Scaling AgileDIY FrameworkANKIT TANDON NOV,26 TH 2016 AGILE FEST 2016
Scaling• What is Scaling
• What does Scaling Agile mean
Scaling Agile
Image: Scaling by Bob Hartman
Activity Time
Case Study• Domain – Banking
• DIY Bank• Bill, the CEO of DIY bank is both excited and nervous at the same time• DIY bank with branches in more than 15 countries and over 10 million customers set a goal to deliver a new
personalized digital banking experience for his Europe based customers this holiday season • He is concerned about 18 teams working together to deliver the product• Teams set to work on it are Agile experienced but have never worked together• Bill wants to develop an Agile culture in which creativity and innovation flourishes and all the teams can work in
tandem to deliver value to customers• Bill wants to enhance the efficiency of IT development process and reduce time to market to retain competitive edge
over its competitors. The first delivery to be provided in the course of just 3 months • Facts and Figures• Banking Industry• 18 teams distributed in various locations • In-house development, different technologies used
• Identified Challenges • Highly regulated environment• Tight deadlines• How to maintain innovation and creativity• The organization’s structure (separate dev,qa and ops teams) and its lack of outcome-orientation and accountability• Synchronization between 18 teams working together on a product
Rules• Form a team of 5-6 people• Appoint a person as CEO (Bill in the case study)• 3 Sprints of 10 minutes each
Sprint 1- Identify the principles• Go through the DIY bank case study• Go through the 12 Agile principles and identify ones that are difficult to scale • If there are more than five then select top five• Write them on sticky notes and put them on chart paper• Review the principles together with CEO and discuss why it can be a challenge to
scale them
Sprint 2-Identify the practices• Brainstorm the practices that might be useful in overcoming possible challenges
associated with each principle identified in the previous sprint• Practices in this context are- Roles, Events and Artifacts • You may refer to various scaling frameworks (SAFe, DAD, Nexus etc) to get an idea• Review the selected practices together with CEO and discuss why these are
important for the realization of business objectives • Put the suggested practices for each principle on chart paper
Sprint 3-Create Your Framework (DIY1.0)• Gather material and tools• Build a blueprint of the scaling framework based on Agile principles that visualizes
the current business objectives, challenges and good scaling practices as indentified in the last sprint
• Review it together with CEO• Put it together on wall / table
Review• Each team to showcase their scaling framework to other teams
Debrief• Start with basics Put a radar to Agile principles
Debrief• SaFA (Scaling and Filleting Agile) Get rid of unnecessary meetings, roles,
artifacts, silos, management layers, tools to make your enterprise fish eatable first. Be an Organizational fish monger!
Debrief• Apply System thinking Look for end to end flow and potential bottlenecks
Debrief• No framework is bad They are just guidelines. Choose one that best matches
your organizations business objectives, challenges and constraints.
Debrief• Do It Yourself Even better to evolve your own. Every system is unique and so is
one you are into. Context is King!
Debrief• Keep evaluating Inspect and Adapt. Yearn for Continuous improvement!
AND..
Debrief ...Its Principles over practices!
In a nut shell
PrinciplesOver
Practices
Start with
basics
Scaling and
Filleting Agile
Apply System thinking
No FW is bad.
Context is king
Create /Evolve a FW that
suits your need best
Keep evaluatin
g
Do It Yourself Scaling Framework
Questions & Answers