Need for scaling agile
•Download as PPT, PDF•
0 likes•556 views
The document discusses the need for scaling agile frameworks in organizations. It defines agile as a mindset that values principles over practices and tools. This mindset requires changing organizational culture. The document then introduces the Scaled Agile Framework (SAFE) as one approach to scaling agile through defined roles at the program level. Finally, it notes that agile is difficult, requires more than just processes, and changes how an organization works by aligning it around a shared purpose.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to Need for scaling agile
Similar to Need for scaling agile (20)
More from Shuchi Singla AKT,SPC4,PMI-ACP,ITIL(F),CP-AAT
More from Shuchi Singla AKT,SPC4,PMI-ACP,ITIL(F),CP-AAT (9)
Recently uploaded
Recently uploaded (15)
Need for scaling agile
- 1. 1 Need for Scaling Agile? June 26, 2015 Shuchi Singla, SPC, PMI-ACP
- 3. 3 Your experience with Agility 1 = Very Little Experience/No Experience 2 = Some Experience 3 = Experienced 4 = Very Experienced 5 = Expert
- 5. 5 Mindset Values Principles Practices Tools & Processes We use JIRA We do stand- ups We are co- located We do just enough documentation We work together What is agile?
- 6. 6 Development teamProduct owner One person decides No dependencies No special roles 1 month or less 9 people or less ScrumMaster Owns the process Agile DEMON
- 7. 7 The Agile Mind If you want to adopt the AGILE MIND You must be prepared to change the mind you have now At scale – this is organisational culture
- 8. 8 Source: Schneider, W. (1999). The reengineering alternative : a plan for making your current culture work. New York: McGraw-Hill. What’s your culture?
- 9. 9 47% 41% 9% 3% Source: http://collectiveedgecoaching.com/2010/07/agile__culture Agile friendly culture
- 10. 10 © RADTAC 2014 Scaled Agile Framework (SAFe)
- 11. 11 DevOps UX Systems architect Business owners Release management Systems team Product management AgilePM (RTE) Shared SAFe defines many roles at a program level
- 12. 12 Key notes Agile is not easy Agile is more than team based process Agile is more than process Agile changes the way you work Agile aligns the organisation around its purpose, empowers staff to master excellence and gives you the space to do your job. Agile is based upon human values Honesty, Trust, Courage, Respect, and Service Agile gives competitive advantage Agile is here to stay
- 13. 132/12/14
Editor's Notes
- Lets first talk on why do we need agile, lets listen from audience. Ask legacy systems were created, they were still successful but why agile?
- I want to talk about agile scaling to 140 - 150 people and 8-12 teams SCRUM does create an environment a bit like a start-up AND IT WORKS One person decides 9 people of less Value created in less than a month No dependencies (good luck with that one) No PROJECT MANAGER but PROJECT MANAGEMENT occurs: Removing impediments Communication progress Managing stakeholders Ensuring project meets objective In this model everyone outside the team is an impediments Roles like BA, PMO, Arch are lost
- This agile mind comes from both adoption and transformation First... Let’s understand the two terms that often used interchangeably Agile Adoption is about what we do...practices, tools, techniques, ceremonies, and habits Agile Transformation is about who we are...reflected in both the structure of the organization and who we are as people, the culture That is scaled agile For long term success organizations need both adoption and transformation
- In safe – we try build cultural change, by first changing the leaders SAFE defines 9 roles at a program level. First step of safe implementation starts with leading safe trainings at leadership level, then educate Pos and PMs, Agile coaches and SMs RTE facilitates the Program Increment – I wonder who this could be!!