Technology has blurred the lines between the digital and traditional methods of dealing with a consumer of any Global Enterprises. The Business Process and IT is no more separate, in most of the industry verticals the Business is driven by IT.   Constant Innovation around IT has become the new normal to the Enterprises to meet rapidly changing consumer expectations and behavior dynamics.

More connected consumers, automated processes, and sophisticated analytics place unprecedented demands on IT functions. Many Enterprises are struggling to cope, and they seek to deliver on new demands by adding piecemeal elements to their existing operations. This is easier said than done. Reinventing the IT function at Global Enterprise requires far-reaching changes, from talent to infrastructure, tools, delivery models, partnership model.

This experience report  brings strategy of 2 speed IT, through which Infosys helped its Global top 10 clients to 'renew' its IT related to Digital & Mobility space using Agile as a key lever.

This session gives you experiences, practical on the ground challenges, stakeholder and vendor complexity and approach and journey towards Speed 2 value. Also I am pairing with Alok Uniyal who is senior leader at Infosys and a CIO coach who helped 50 plus clients to transform their IT organization in last 20 years.

Way back in 2008, when I started working in Agile, there was enough material available on Scrum and. However when it came to distributed aspect of it, people were still struggling with it. Based on working for years in this fashion, I realised that communication, trust, transparency and innovation are the core fundamental values towards successful distributed Agile implementation.

In other words, as most of the problems were caused by softer aspects of skills (misunderstanding, miscommunication, non-availability of people, mistrust etc), humanizing the distributed team experience looked like the key for successful distributed Agile implementation.

Based on working with distributed teams over the years, we discovered some distributed Agile patterns. Some of them got blogged from time to time. Those already available in form of blogs are as follows:

• Distributed Pair Programming
• Local Retrospective
• Agile way of documentation
• One Team Multiple Projects
• The nut/bolt pattern for distributed Scrum development
• Chain-Link Pattern
• Virtual One Room

The session is to share the these patterns and more (when to go for distributed Agile and when not etc)

Welcome to the crazy world of Dev-Ops, where the tales span the spectrum from gruesome, grizzly to the heavenly and flowery bliss!

The silo’d structures, the agonizing buy v/s build debates, the departmental handoffs, tooling and of course the cultural barriers, which all add fuel to the story unfolding in our brave new dev-ops world. But sometimes there are silver linings and the heavens part way for the shining stars to reveal their true glory.

Join our session to listen to the tales of our (not so) successful dev-ops, and learn the lessons from our experiences.

Why organizations are adapting towards agile? Is it to get most out of their resources or is it about doing the right thing?

Traditional mind set of achieving high productivity and using resources efficiently does not change easily, even when organization moves to agile they remain more and more worried about the team velocity. When I meet agile practicing companies or I attend event on agile I find that most of

the focus is on delivering product backlog efficiently. We see lot of talks on how to make team more self-organizing so that they can do the things faster.  Even after moving to scrum or agile we keep ignoring the warning

“There is nothing so useless as doing efficiently that which should not be
done at all.”  —Peter F. Drucker

When most of the organization starts with agile they takes it as an engineering process, and most of the team focuses too much on velocity, while to get maximum out of agile we need to look at Enterprise Agility, we need to look at an organization’s entire value stream—from idea to implementation, from concept to consumption.

My talk would be focusing on need of organization agility and will introduce one of the monitoring tool “Life Cycle Profitability “which can help organizations in getting answers of questions like :

• Should we delay the release by one month to fix the defects ?
• Should we reduce the cycle time by adding one more team?
• Should we delay the release to add functionality?
• Should we delay the project by one month to get more innovative ?

Life Cycle Profitability is based on principle “Take an economic view” introduced in book:The Principles of Product Development Flow , Donald G. Reinertsen . In my talk I will be showing how we can convert proxy variables like cycle time , velocity , technical debts  into Life Cycle Profit.

I presented part of this concept in one of the conference and got good response, but I will create fresh presentation for this talk, since this time I will put more focus on expanding the model to calculate the Life Cycle Profit.

Leaders today are looking at “self organizing” agile teams to WIN ALL the battles on Auto-Pilot. Nice try is all I can say !!

...though some teams surely do succeed (lucky guys?).  But most teams are not so lucky, and get constrained by the organizational systems, processes, boundaries, and need an outside-in perspective or a divine eye to kick start their next improvement journey. Sometimes a leader takes on this divine role to guide them on this journey.

This talk aims to provide the leaders a toolbox for using Lean conversations, to spark their next team improvement journey, by designing improvement kata’s, while slowly inching the team forward towards nirvana !! Divine Bliss !! .... So if you are a leader looking at learning and implementing the simple techniques of guiding the team on a self improvement cycle, leading to true self organizing team, join us.

As Agile Practitioner, We agree that Learning agile is not same as Practicing Agile. Enthusiastic Organizations and Teams keep all their energies and money in learning about Agile frame works. Few of them were successful in implementing the agile practices. One of the key reasons behind the success is many of the first time Agile practicing teams attend the workshops/trainings from Experts. Experts share the wisdom (along with the concepts/theory). This wisdom/learning help the teams to convince all the stake holders (other than agile teams) and execute the first/initial agile projects successfully. This success motivates the organization to scale up agile. Scaling Agile needs adding more teams. Organizations focus on investing advanced tools/softwares. Teams involved in initial/first agile projects adapt themselves to scale up to the new change/challenges. To Scale up the Organization to Agile, every person/group promotion agile or involved in initial/first agile projects should act as Agile Evangelist.

"Learn & Teach Agile Easy way" is a simple and easy to understand kit that helps them conduct sessions such as

• Quick start/Induction to Product Owner
• Quick start/Induction to Scrum Master
• Quick start/Induction to Team
• Awareness on Agile Concepts to Quality Assurance team
• Awareness on Agile Concepts to PMO Teams