Schedule

8:30 am - 9:00 am

Registrations open

9:00 am - 9:15 am

Welcome to Inspire 2018 – General instructions and guidelines

9:15 am - 10:15 am

Srijanpal Singh

Key note – Leadership in 21st century – a social entrepreneur in you.

10:15 am - 11:15 am

Nitin Mukhija

Session Type: Tools & Technique Practice
Session Topic: Get MAX from your automated tests
Duration: 1 hour
Learning Objectives :
In this talk, I will be presenting a case study of how in PayU we have polished our automation system to get more worth out of it, allowing us to do multiple production releases every day. I will be covering:-
– Layered Architecture
– Continuous Integration
– Enhancing reporting
– Generating Module wise Reports
– Tips and tricks to reduce automation failure investigation time
– Tips and tricks to run tests faster
– Measure dev code coverage
– Best practices in writing automation code

Business Case :
PayUMoney deals in financial transactions. We have to deliver high-quality software FAST

Business Benefit :
In a short period, PayU India has become India’s best online payments solution company. Such growth demanded, lightning fast delivery of product features, and since we deal in financial transactions it has to be done with 0 defects.
Implemented a solid automation framework with scalable architecture which has enabled us to do 6-8 production releases every day. It allows manual testers to contribute as well, supports modular execution and reporting, bringing optimization and efficiency in SDLC.

Who should attend? : Developers / Testers / Program Managers / DevOps

11:15 am - 11:30 am

Tea break

11:30 am - 01:00 pm

Pawel Kaminiski

Joe Dempsey

Session Type: Workshop
Session Topic: “BET ON THE HORSE OR THE JOCKEY ?” A PRACTICAL APPROACH TO FOUNDER AND IDEA VALIDATION

Outcomes/take aways of session: You will learn:
Why is it important to validate product ideas before writing your first line of code
Why is it even more important to validate the founder, his vision, intentions, and ability to work together.
How to validate founder, including practical exercises and suggestions. We will play games, create conflict and resolve biases.
How to validate products learning about Google Sprints, Lean Startup and Design Thinking frameworks. There will be a theoretical introduction and practical approach.
Under which of the following categories would this story fall?: Agile Product mindset, Agile mindset, User experience, Other
Target audience: Developers, QA, Team leaders, Project managers, Product Owners, CEO, Other

01:00 pm - 02:00 pm

Lunch break

2:00 pm - 03:00 pm

Joseph Jude

Session Type:talk
Session Topic: Agile for C-Suite

 

Whats the story about
This is the best of times and worst of times for a CXO.

The quantum and depth of business challenges thrown at executives can paralyze even the seasoned ones. Stringent regulatory compliances, fast changing business models, ever scrutinizing media, and demanding clients are just few of the challenges that current executives have to face on a regular basis. Buried within those challenges are the never ending opportunities for the same executive.

Traditional long-term planning is no match to deal with this dynamic interplay of challenges and opportunities. Evolving business environment needs a matching evolving strategy.

Agile has proven itself as the de-facto methodology for software delivery. The idea of agile is to solve a complex problem through collaborative cross-functional, self-contained teams that deliver in increments and retrospect to accelerate or change course.

Executives in thriving companies are embracing agile methodology for organizational building, project delivery, and future focus.

In this talk, I propose to talk about how executives in an IT organization has embraced this agile methodology for executive activities.
Duration of story: 45 min
Outlines/Structure of session: – Challenges of executives
– Why long-term planning is not good for current challenges
– How agile is the only sure way for executives
– A case study of agile in c-suite
– Questions & Answers

Outcomes/take aways of session: – Appreciation of business reality
– How agile-mindset can take you to the executive room sooner than later

Under which of the following categories would this story fall?: Agile leadership, Agile mindset, Agile organisation

Target audience: Product Owners, CEO, Agile coaches

03:00 pm - 04:00 pm

Smita Mishra

Session Type: Talk
Session Topic: Tester or Data Scientist

Tester or a Data Scientist? Are you ready for this switch?

 

Data Scientist has been named as the sexiest job of the 21st century.

“Data scientists make discoveries while swimming in data. It’s their preferred method of navigating the world around them. They are able to bring structure to large quantities of formless data and make analysis possible. They identify rich data sources, join them with other, potentially incomplete data sources, and clean the resulting set.” Quoted from HBR.

Replace the word Data Scientist in the paragraph above with tester and it will still make as much sense.

If your organization stores multiple petabytes of data, if the information most critical to your business resides in forms other than rows and columns of numbers, or if answering your biggest question would involve a “mashup” of several analytical efforts, you’ve got a big data opportunity.

 

Much of the current enthusiasm for big data focuses on technologies like, Hadoop (the most widely used framework for distributed file system processing) and related open-source tools, cloud computing, and data visualization. While those are important breakthroughs, at least as important are the people with the skill set (and the mind-set) to put them to good use.

 

The session is for testers who would like to understand the whole landscape and role of data in our IT world today.

How easy or difficult will it then be for a tester to be a data scientist someday? Or is she one already?

Under which of the following categories would this story fall?: Agile Product mindset, Agile mindset, User experience, Other

Target audience: Developers, QA, Team leaders, Project managers,  Other

04:00 pm - 04:15 pm

Tea break

04:15 pm - 05:00 pm

Priya Patra

Session Type:talk
Session Topic: Building the Experience of now, future and beyond – The (I)IoT Experience Center

Whats the story about

We live in a connected world. The tsunami of IoT devices has come to our homes, workplace, to industries which means – to the projects we manage. Projects today are now transformed to include complex combinations of sensors, hardware, software, data storage, multiple protocols of connectivity to name a few. Projects we manage no longer operate in isolation but are part of a large ecosystem.

With every minute, hour and day more things are getting connected; Gartner predicts that there would be 50 Billion connected things by 2020. What does this mean to us the project managers? What does this mean for the future of our projects?

The ( I)IoT experience center is a futuristic place where we can live the experience of (I)IoT use cases present and the future.
In this session I will narrate a real story of building an experience of the future, a project which brings in all domains of an (I)IoT project – construction (civil), audio visual, networking, IT(sensor, hardware and software) to create a futuristic experience.

Duration of story: 45 min

Outlines: – In this session I will discuss
– Vision of Project “(I)IoT Experience Center
– Application of frameworks like Accelerated Solutions Environment and Rapid Design and Visualization in the planning and design phase
– Collaborate with the startups to build solutions creating futuristic experience
– Application of principles of Innovation and Agility to bring all components of the project – Civil, Audio- Visual, networking, hardware and software programming in building an experience of the future
– Current implementation for our campus
– Business Value achieved :
Internal – Process improvements and learning and growth for me as a project manager and for our team
External – In terms of business gaining new logos and new projects from existing logos.
– Roadmap of the future – how we are scaling the concept to the entire campus to provide an experience of the future Learning Outcomes:
– Define the steps in managing an (I)IoT project and an IoT ecosystem
– Apply principles of innovation and agility to build an experience of the future
– Explore the transformational role of the project manager in the (I)IoT world

Outcomes/take aways of session: – Appreciation of business reality
– How agile-mindset can take you to the executive room sooner than later

Under which of the following categories would this story fall?: Agile leadership, Agile mindset, Agile organisation

Target audience: Product Owners, CEO, Agile coaches

05:00 pm - 6:00 pm

Raghvendra Meharwade

Anubhav Gupta

Session Type:talk
Session Topic: SMART AGILE TOOLS 2020 – AI TAKING IT TO THE FUTURE STATE

Whats the story about

Artificial intelligence and automation have fundamentally and profoundly changed the way we work and Live. This is true for Agile teams. It has changed the way they collaborate, learn and improve as well as the tools used. BOTs are taking Agile management tools to the next level.
This session focused on four key learnings:
• Understand the evolution of Agile management tools and the impact of artificial intelligence and BOTs.
• Discover how these emerging BOTs help Agile teams to achieve more.
• Study the current state of Agile and the usefulness of AI on its future state.
• Inspire participants to accomplish more leveraging AI and be future ready by contributing in business transformation.

Duration of story: 45 min

Outline/Structure of the Talk:
1. Introduction (5 minutes)
2. Evolution of Agile Tools (20 minutes)
3. Beyond 2016: AI enabled Agile Tools (10 minutes)
4. Current State of Agile and the Role of AI in Agile (10 minutes)
5. Mission 2020 for Agile SMEs (5 mins)

Key takeaways for participants:
• Gain awareness on the future of Agile tools
• Understand AI’s role in Agile and Agile tools
• Learn how to accomplish more leveraging AI and be future ready by contributing in business transformation
Target Audience Agile Coaches, Scrum Masters, Change Enthusiasts
Prerequisite Prior Agile exposure preferably either as Scrum Master or an Agile Coach

06:00 pm - 06:30 pm

Closing note by Agile Chandigarh

8:30 am - 9:00 am

Welcome and Registrations

09:00 am - 10:30 am

Tathagat Varma

Topic: Workshop on Service Design Thinking

Abstract: In this hands-on workshop, the participants will be exposed to the idea behind Service Design Thinking by working on a real-life problems and co-create delightful experiences that both, meet the functional needs of an organization as well as create awesome experiences for the customers.

10:30 am - 11:15 am

Nitin Sethi

Title of the story: Design Thinking for Startups
Event type: Its a talk
Whats the story about: Importance of Design Thinking for Startups
Outlines/Structure of session: Highlight what not to do and sharing industry insights
– Design Thinking is relevant to whom?
– Driving Startups and Businesses by Design
– Some example of companies who have Design Thinking built in their product development process
– Examples and Industry Data
– Can we measure ROI on design
– Customer Empathy

– Role of Design Thinking in Digital Transformation
– How to make a bigger impact through design thinking
There will be a lot of industry examples and data to support the story 🙂

Outcomes/take aways of session: Design Thinking is for everyone
Under which of the following categories would this story fall?: Software craftmanship, Agile Product mindset, Agile leadership, Agile mindset, Agile organisation, Agile testing, User experience
Target audience: Developers, QA, Team leaders, Project managers, Product Owners, CEO, Agile coaches

 

11:15 am - 11:30 am

Tea break

11:30 am - 01:00 pm

Pawel Kaminski

Title of the story:  What to do when Agile does not work
Event type: Its a workshop
Whats the story about
In less than two years, I have helped to create 25 global, technical startups in multiple business domains, with constantly changing requirements, volatile market conditions and ambitious founders with sometimes crazy visions of the future. To deliver on those objectives, at ucreate, we required a “northern star” to lead us in on this complicated journey. We decided to trust our founders and focus on their users. We focused so thoroughly that we designed and built products for a single individual ignoring scale and thinking big approach. We decided to make a difference for one person and always focus on the user, no matter the cost. This talk will guide you through our journey and lessons we learned.Let me share with you my stories of how to build products by shifting the focus from scalable, technical solutions to addressing single user needs and challenges. How to impact culture, inspire a distributed, rapidly growing company and how to collaborate and treat your founders and your colleagues like “you believe in what they believe.”Everything we do starts with WHY and a single user need.The session is for anyone who in their daily job needs a helping hand, a bit of inspiration and a useful set of practical experiments to challenge status quo, move the needle in their organization and build delightful products that people want. I also want to show them they are not alone in their failures and defeats.
For me, this talk is about a constantly evolving set of ideas, thoughts, and values that always puts the user first and allows our employees and founders to have the time of our life.

Outlines/Structure of session: Introductions
Current state of agile by workshop members
Simulation 1 run in teams
Discussion and Systems Thinking representation
Simulation 2,3 depends on time with individual team changing certain policies and parameters
Simulation 5 based on multiple teams working on one project
Summary, discussion.

Outcomes/take aways of session: what is a startup
why and how to start one
how it feels to work for a startup
why startups fails
and our ways to mitigate that
our process Kanban and agile
our policies
data driven
saying No
bringing bad news early
dealing with biases
diversity of thoughts and people
team building
Theory of Constraint way of introiducing change
conflicts and win- win solutions
starting with WHY
building great teams
company culture

 

Under which of the following categories would this story fall?: Agile Product mindset, Agile mindset, Agile organisation, Agile testing

 

Target audience: QA, Team leaders, Project managers, Product Owners, CEO, Agile coaches, Other

01:00 pm - 01:45 pm

Lunch break

01:45 pm -02:30 pm

Ajay Kabra

Topic of the story: Individual Performance in a Team Game

 

What is this story about
Many companies are shifting to Agile. But, most continue to use their existing performance evaluation methods! Why? This creates a “chasm”. Industry is moving towards the new age technologies and methods to produce better software, more complex elements, but we have not as yet moved ourselves with respect to evaluating the performance of an Individual and a team.
The word agility is on the lips and tips of most business executives throughout the world as they try to increase their employees’ and organizations’ ability to anticipate change and respond efficiently and effectively.
The benefit of one team, one vision, common mission gets diluted due to the aspect that aspects of HR related processes not being aligned to the Agile approach
The Interesting part of the story is that Agile and its manifesto have heavily focused on the harder part of the system, leaving the softer issues on the back burner or should I say to the traditional approaches. On one hand using the values and principles we are trying to move away from the traditional approaches of development and on the other hand we still continue to embrace and adopt the old system. This carries the risk of creating a unknown Chasm in the system
It is human nature for people to modify their behaviors to match the evaluation system.
• A very important part of any agile rollout is to align the performance evaluation system (and other HR practices) with what Agile emphasizes.
• Not doing so causes dysfunction that will erode the team’s effectiveness.
The performance appraisal isn’t always the most popular subject, but the evidence has been in for quite some time that it is more harmful than beneficial. There’s room for more research and thinking, but not for improving the performance appraisal. Instead the most important research is in engaging with your system and using continuous improvement and inspect and adapt to improve both the relationships in the workplace as well as the systems for getting work done. There are solutions available for how to set pay without performance appraisals. If you’re willing to be a transformational leader – will you bring these ideas to your workplace?
The purpose of this talk / session is to bring out the finer points of performance appraisals of individuals in Agile setup, How it can be achieved, What can be done?
Benefits
Outline
The talk would cover the following main areas:
• Issues with the traditional approach to performance management
• Role of Scrum Master in Performance management
• How to deal with Performance management

Outcomes 
• Understanding the issues with the performance appraisal process
• How to conduct and performance appraisals for Individuals in Agile

Audience
This talk would be useful for:
• Sr. Mgmt
• Scrum Masters
• Product Owners
• Development Team Members
• HR
• Talent Management team

02:30 pm -03:30pm

Shivali Chadak

Ashish Kumar

Title of the story: Big O of RetrO – Retry Out of the box !!
Event type: Its a workshop

Whats the story about

Retrospective is the heart of scrum and agile world. We need to ensure this heart is well connected to other parts and functioning well. Getting the right amount of inputs and making sure with the right outcomes. This workshop will be an eye opener to understand anti patterns of retrospective. It will be more of a hands-on exercise for all the attendees based on our experiments which we have conducted got benefited. Will help to practice an effective retrospective which enables the team to seize opportunities to improve. Retrospectives can become monotonous and boring over time and so they become ineffective. We need to bring something new, fun, or exciting to the retrospective to make it lively.

This workshop will lead a way as a food for thought for scrum practitioners. Why it is important to ensure that each team member is comfortable participating and sharing thoughts and ideas requires that the Retrospective be conducted with an atmosphere of respect, honesty and positivity. Retro facilitator who contributes structure and process to a Retrospective to help the Scrum Team identify and bring about an outcome that is consistent with the Team’s objectives.

Will also cover the aspect as how a Retrospective lacking a Facilitator will suffer problems similar to a team-based sporting event lacking a referee. Retrospective should be facilitated in a healthy and fun way, team level engagement should be taken on priority. Retro outcome apart from the action items team should look forward to participate and leave a mark.

Successful retrospection responsibility who ensure, is it team or scrum master or both? Together teams need to think outside the box when approaching Sprint Retrospectives and appreciate that these short gatherings need not to be done only by using the usual techniques or methods. Instead they can bring their own ingenuity, knowledge, and experiences to the table to create games or to start meaningful discussions that the team drives.
Duration of story: 75 min
Outlines/Structure of session: – Setting the context
– Prime directive
– Our case study: Why of the session
– Ice breaking: Energizer: Good meeting starter
– Check-in: Gauging the participants frame of mind and how they feel about the context. Reflection, Is that you?
Problem discovery exercise
– What next?:

 

Outcomes/take aways of session: We will use the actual work and life experiences to innovate new ways of making the Sprint Retrospective fun and engaging, in addition to educational and transforming. The intent of sharing the games and techniques is this workshop is to help our fellow practitioners to get their juices flowing so they can come up with their own ways to have more effective Sprint Retrospectives. We would be glad to hear from audience who have tried anything different that has worked out for their teams and retrospectives.

We will ensure after the session you will have different flavors, perspective of the retrospective. Will help you to curate your own fun and engaging retrospective methods based on your experience.
Under which of the following categories would this story fall?: Agile leadership, Agile mindset, Agile organisation
Target audience: Developers, Team leaders, Project managers, Agile coaches, Other

03:30 pm -03:45 pm

Tea break

03:45 pm - 04:45 pm

Arjun Ghosh

Vikas Mishra

Title of the story: Effective requirement gathering using design thinking techniques
Event type: Its a talk
Whats the story about

 

Requirement Gathering is mostly challenging and one of the biggest & starting failure points in a software’s developmental life-cycle. Audience would get learn how to do effective & efficient Requirement Gathering in a software project, to create a viable backlog leveraging Design Thinking principles, hence combining the fluidity & efficiency of Design Thinking philosophies with power of Agile mode.

Outlines:

Introduction

Presentation of problem statement

Techniques of effective requirement gathering

Presentation of a case study.

Summary.

Outcomes/take aways of session: Learn techniques of effective requirement gather.
Under which of the following categories would this story fall?: Agile Product management, Agile project management, Agile mindset
Target audience: Business analysts, Product managers, Project managers, team leaders.

04:45 pm -05:45 pm

Leena N

Title of the story: Expand Contract Pattern for Continuous Delivery of Databases
Event type: Its a talk
Whats the story about

: Modifying the database schema is scary. It is hard to rollback the changes if something goes wrong. But it is difficult to avoid necessary refactoring to the database.

The talk is about the Expand/Contract pattern to make significant changes to the application, in a safer and reversible manner.

Outlines/Structure of session: Modifying the schema of a production database is hard. If something goes wrong, the impact on both customers and the team can be enormous. And it can be hard or even impossible to rollback a database schema change if things go wrong. And the same is true for any architectural change for a production application.

The Branch by Abstraction and Strangler Pattern makes significant application changes easier. Are there any similar patterns we can use to make production database changes less risky?

Indeed, there are. The Expand/Collapse pattern is a blueprint for making the database migration. It makes the remodelling both reversible and safe. By expanding the application to accommodate both the old and the new schemas in parallel, we can give ourselves time to:

Migrate any downstream dependencies on the old database schema
Gain confidence that the migration is safe
We contract the application to the new version, once we’ve satisfied that the old schema is no longer needed.

The pattern helps to make significant, but necessary refactorings to your data model in a continuous delivery way. Most importantly, without threatening the robustness of your production applications.

While working with our product GoodKarma, I’ve successfully applied this pattern to make major changes to the core of the application, all while serving customers in production. I’ve learned some important lessons about how to best implement the Expand/Contract pattern.

In this session, I’ll share my experiences on how to avoid pitfalls and succeed at these kinds of major data remodelling with hardly any downtime.
Outcomes/take aways of session: The key takeaway is that the Database too can be migrated in a safer and reversible manner by

– Approaching it using Expand/Contract pattern
– Other patterns such as Branch by Abstraction and Strangler pattern to approach long, significant architectural refactorings
– The pitfalls and learnings while using these patterns
Under which of the following categories would this story fall?: Software craftmanship, DevOps, Other
Target audience: Developers, QA, Team leaders, Other

05:45 - 06:15 pm

Closing note by Organising team – Agile Chandigarh