Agile2014 conference presentation on "Smart Scaling" - how to compare scaling approaches. Our Agile Scaling Knowledgebase (ASK) and Decision Matrix help provide an objective way to compare approaches.
Steve + Richard
Keep intro short – dive into Connections
Steve
Briefly explain origins –
Concept emerged from Scrum Alliance Scrum Coach Retreat - December 2013
Original workshop members include: Richard Dolman, Steven Spearman, Dave Cornelius, Bob Galen, Bryan Stallings, Perry Reinert, Mike Register, Bill Johnson, and Vijay Kumar
Richard + Steve
Connections – Have audience introduce themselves to their table mates.
Have them think about the topic and connect to it before we get into background and details.
Each person will likely have some pre-conceived ideas of what “Scaling” means to them.
These may be voided or validated through this session.
Have Post-its and/or sheets of paper and sharpies. We should also have flip charts in the room.
More teams?
Bigger teams? Bigger problems?
Bigger programs? Bigger dependencies?
Across the organization?
Beyond IT / SW development?
Steve + Richard
Review evolution and aspects of the “Matrix”
Hand outs…
The matrix is not intended to be a definitive or limited tool. Users may add or remove frameworks and criteria as needed.
Mention Scrum at Scale (Brown/Sutherland); Enterprise Agile Transformation Framework (Michael Spayd); EbM (Scrum.org); Comparative Agility (Cohn); Agility Health (Elatta); others…
Steve
Review Survey results
Format
Ratings Levels
Steve + Richard
Discuss Insights/Learning for each of the popular approaches:
Richard – Discuss DAD and Spotify
Steve – Discuss SAFe and LeSS
Steve + Richard
We reached out to each of authors of the primary Scaling approaches to get their take on this initiative as well as details about their approaches.
Review input from Thought Leaders
Richard
Discuss Insights/Learning for Spotify
Richard – Discuss DAD and Spotify
Steve – Discuss SAFe and LeSS
Richard
Discuss Insights/Learning for Spotify
Richard – Discuss DAD and Spotify
Steve – Discuss SAFe and LeSS
Richard
Discuss Insights/Learning for Spotify
Richard – Discuss DAD and Spotify
Steve – Discuss SAFe and LeSS
Steve
Discuss Insights/Learning for LeSS
Richard – Discuss DAD and Spotify
Steve – Discuss SAFe and LeSS
Steve
Discuss Insights/Learning for LeSS
Richard – Discuss DAD and Spotify
Steve – Discuss SAFe and LeSS
Steve
Discuss Insights/Learning for LeSS
Richard – Discuss DAD and Spotify
Steve – Discuss SAFe and LeSS
Richard
Discuss Insights/Learning for DAD
Richard – Discuss DAD and Spotify
Steve – Discuss SAFe and LeSS
DAD is a governed, hybrid approach that provides a solid foundation from which to scale agile solution delivery within enterprise-class organizations.
Extends Scrum for the entire lifecycle.
“The Disciplined Agile Delivery (DAD) decision process framework is a people-first, learning-oriented hybrid agile approach to IT solution delivery. It has a risk-value delivery lifecycle, is goal-driven, is enterprise aware, and is scalable.”
A differentiator of the DAD framework is that it explicitly recognizes that agile teams, just like other types of teams, are governed
Enterprise awareness is one of the key aspects of the DAD framework. The observation is that DAD teams work within your organization’s organizational ecosystem, as do all other teams.
DAD Agile Lifecycle, as well as DAD Lean Lifecycle
Richard
Discuss Insights/Learning for DAD
Richard – Discuss DAD and Spotify
Steve – Discuss SAFe and LeSS
DAD is a governed, hybrid approach that provides a solid foundation from which to scale agile solution delivery within enterprise-class organizations.
Extends Scrum for the entire lifecycle.
“The Disciplined Agile Delivery (DAD) decision process framework is a people-first, learning-oriented hybrid agile approach to IT solution delivery. It has a risk-value delivery lifecycle, is goal-driven, is enterprise aware, and is scalable.”
A differentiator of the DAD framework is that it explicitly recognizes that agile teams, just like other types of teams, are governed
Enterprise awareness is one of the key aspects of the DAD framework. The observation is that DAD teams work within your organization’s organizational ecosystem, as do all other teams.
DAD Agile Lifecycle, as well as DAD Lean Lifecycle
Richard
Discuss Insights/Learning for DAD
Richard – Discuss DAD and Spotify
Steve – Discuss SAFe and LeSS
DAD is a governed, hybrid approach that provides a solid foundation from which to scale agile solution delivery within enterprise-class organizations.
Extends Scrum for the entire lifecycle.
“The Disciplined Agile Delivery (DAD) decision process framework is a people-first, learning-oriented hybrid agile approach to IT solution delivery. It has a risk-value delivery lifecycle, is goal-driven, is enterprise aware, and is scalable.”
A differentiator of the DAD framework is that it explicitly recognizes that agile teams, just like other types of teams, are governed
Enterprise awareness is one of the key aspects of the DAD framework. The observation is that DAD teams work within your organization’s organizational ecosystem, as do all other teams.
DAD Agile Lifecycle, as well as DAD Lean Lifecycle
Key Steps:
1. Focus on consumable solutions, not just potentially shippable software
2. Extend Scrum’s construction lifecycle to address the full delivery lifecycle
3. Move beyond method branding
4. Adopt explicit governance strategies
5. Take a goal-based approach to enable scaling
Steve
Discuss Insights/Learning for SAFe
Richard – Discuss DAD and Spotify
Steve – Discuss SAFe and LeSS
Steve
Discuss Insights/Learning for SAFe
Richard – Discuss DAD and Spotify
Steve – Discuss SAFe and LeSS
Steve
Discuss Insights/Learning for SAFe
*Point out need to measure. Transition into other “orthogonal” measurement-centric models – including EbM, Comparative Agility, Agility Health, etc…
Richard – Discuss DAD and Spotify
Steve – Discuss SAFe and LeSS
Scenario 1:
“Traditional” / non-technology oriented, brick & mortar company
IT org size approx 1000
Multiple Dev teams, plus “Shared Services” teams of DBAs, Security, Infrastructure, Specialized Developers
Complex eco-system w/ combination of COTS and Custom App Dev
Some co-located teams, but most are distributed, including outsourced/vendor teams
Project-centric structure and strategy
Command & Control culture
Scenario 2:
Medium-sized “technology” company
IT org size of > 500 < 1000, but IT is the business
Products are web-based, Saas-based
Mostly co-located teams, but org is distributed
Product-centric structure and strategy
Predominately a Collaborative culture
Scenario 3:
Medium-sized company
IT org size of > 500
Still relatively new to Agile, but looking to scale quickly
Need to go from a few independent teams to several, cross-dependent teams
Need to better coordinate release management
Predominately a Competency culture
Richard
Concrete Practices – 15 Minutes (10 min + 5 min)
Have handout of ASK Matrix for people to use, markup, discuss…
Ask Questions about the Approaches and/or what challenges YOUR Organization may be facing.
Hands-on exercise and/or table talk will build on concepts and provide mechanism for input/feedback.
Have Post-its and/or sheets of paper and sharpies. We should also have flip charts in the room.
** Allow a few minutes for group discussion, key take-aways…
Steve + Richard
Talk about main next steps
Steve + Richard
Conclusion – Summarize ideas, feedback from audience and open Q&A to close.