Scaling your agile implementation across multiple teams in large organizations is always a challenge.
In this webinar, Ragia and Asmaa shared their experiences about:
- Why scaling?
- Different scaling frameworks?
- SAFe configurations
- SAFe pros & cons
============== Follow us ==============
Website: http://xpdays.org
Linked In: https://www.linkedin.com/company/xpdays
Facebook: https://www.facebook.com/xpdaysorg
Twitter: https://twitter.com/xpdaysorg
#agile #scaling #xpdays #agilearena
2. Presented By &
XP Days xpdays.org is an initiative for
gathering people interested in Agile,
eXtreme Programming (aka: XP),
Scrum, Coding, etc.
XP is a lightweight, efficient, and low-
risk Agile Software Development
Framework intended to improve
software quality.
Agile Arena agilearena.net is an Agile
Consulting and Training company. specialized
in agile adoption and transformation for
companies and teams through:
• Designing their agile adoption programs
• Executing our programs and guiding the team
through their journey to sustainable agility .
• We also provide accredited training classes
for companies and individuals
Scaled Agile Framework
4. Presented By &
IBM-GDC -
Testing
VF -VMBAE
VF Germany
Web
factory
IoT- Scrum
master
IoT Agile
coach
Robotics
Agile coach
VOIS- BT-
Enterprise
Agile coach
2009 2012 2014 2016
Asmaa Youssef
2018
Agile coach In VOIS
Led multiple agile transformations using
different agile methodologies as Scrum,
Kanban and SAFe.
Trained/coached 350+
2019 2021
Scaled Agile Framework
5. Presented By &
Scaled Agile Framework
Ragia AboElFadl
2011 2016 2018 2019
BSc. With
honors
M. Sc. In
software
quality
Software Engineer
Sr. Software Engineer (Scrum) Data Viz Engineer/Scrum Master
Agile Coach(SPC 5.0)
AD Agile Coach :
• Coaching Agile teams on
Different agile practices.
• Certified Scrum Master.
• Certified Agile Coach.
• SAFe Program Consultant.
2010
Hewlett Packard
Quality Engineer
6. Presented By &
Scaled agile framework
AGENDA
Why to Scale?
Different Scaling frameworks.
SAFe Configurations.
SAFe Pros. & Cons.
SAFe Learning Paths.
What we’ll be covering this webinar
8. Presented By &
Scaled agile framework
Those who master large-scale software
delivery will define the economic
landscape of the 21st century.
—Mik Kersten
9. Presented By &
Scaled agile framework
Whytoscale?
Large
Deliverables
Multiple teams Alignment
10. Presented By &
ScalingLevels
• Management, executive consultancy, leadership mentoring, environment design
Leadership
• Org Structure & strategy, Policies, Roles & continuous improvement
Organization
• Innovation, strategy & budgeting, etc.
Product & Solutions
• Product and project delivery, frameworks of Scrum and Kanban
Delivery
• Execution and Practices, technical mentoring
Execution
Team
Level
Coaching
Organization
Coaching
Scaled agile framework
14. Presented By &
Scaled agile framework
SAFe for Lean enterprises is a
knowledge base of proven,
integrated principles, practices
and competencies for
achieving business agility by
implementing Lean, agile and
DevOps at scale.
15. Presented By &
Scaled agile framework
SAFefourconfigurations
www.scaledagileframework.com
1. Essential SAFe
2. Large Solution
SAFe
3. Portfolio SAFe
4. Full SAFe
1
2
3
4
18. Presented By &
Scaled agile framework
2
• A virtual organization of 5 – 12 teams (50 – 125+ individuals)
• Synchronized on a common cadence, a Program Increment (PI)
• Aligned to a common mission via a single Program Backlog
AgileReleaseTrains(ARTs)continuouslydelivervalue
19. Presented By &
Scaled agile framework
► Feature is an industry-standard term
familiar to marketing and Product
Management
► Expressed as a phrase, value is
expressed in terms of benefits
► Features are identified, prioritized,
estimated, and maintained in the
Program Backlog
DefineFeaturesfortheProgramBacklog
Features are services that fulfill user needs within a PI.
3
27. Presented By &
Scaled agile framework
SAFePros.andCons.
• Economic framework to guide everyone on decision
making towards financial objectives : Lean budgeting
, Epic Funding , Cost of Delay.
• Dependency Management in the scaling setup
between teams of Agile teams.
• Joint Planning and Synchronized Cadence –
Consistency between all stakeholders , business and
teams
• Detailed Implementation Roadmap and guide.
• Proven well documented Lean, system thinking and
devOps principles translated to practices
• People centric view on agile delivery with clear roles,
artifacts and events
• Holistic 3 tier view of value stream including portfolio
level
• Constant refinement of SAFe knowledge base from
2011 until now , latest release v.5.0 in Jan 2020
• Clear focus on quality and engineering practices
• Measure and grow maturity assessments
• High Cost when it comes to the newly introduced
roles and events.
• Sometimes Reduced Agility in the context of Quarter
based planning.
• Heavy Weight framework given all the details and
practices introduced in all Levels of SAFe
• Certification centric framework where it is
recommended to train& certify everyone involved. In
the implementation roadmap
• A detailed & Prescriptive framework may narrow
teams thinking to change or get rid of practices that
doesn’t make sense to them.
Mik kersten who wrote the very well known book project to product
How to drive the product around the value
Welcome to the software age—an interconnected, real-time world in which every industry is dependent on technology and every organization (at least in part) is a software company. To remain competitive, enterprises need to digitally transform their operations, business solutions, and customer experience. The larger challenge in many enterprises is that their current business models, organizational hierarchy, and technology infrastructure can’t keep pace with the rapid change required.
Our discussion today is about competing in the age of software.
The creators of the Framework have been inspired by some new works in the field including Mik Kersten's new book Project to Product and John Kotter’s new book XLR8 (phonetic ‘accelerate’).
Studying technological trends, Kersten concludes that those who master large scale software delivery will define the economic landscape of the 21st century.
That's a bold statement. But when you look at the combined revenue of Facebook, Apple, Amazon, Netflix and Google, you’ll see that it’s equal to the gross domestic product of Japan. The economics of the world have changed, dramatically.
If the Global 2000 doesn't get to the same level of competence that these unicorns have achieved, the balance of power will be eventually end up in the hands of these few companies and that’s not a healthy thing.
Managing growth
Aligning men different level organization strategy to team execution
Scale growth
Simplify on team level
Squad for engineering
That’s team level coaching
Similar kind of deliverables
///
HR or engineering
Organization, targets like digitalization
Team level output execution to strategy down the way
5 mins
Timeline of raising ….
Number of companies adopting
Roles and team structure
Level of details
Spotify model
15 mins
Introducing SAFe 5.0 the operating system for Business Agility
Essential SAFe
Large solution
Different SAFe configurations in each slide
Cadence
Trainer Guidance:
Cover the 3 key train features 5-12 teams, synchronized, aligned.
Key Message:
The continuous delivery (CD) pipeline (also referred to as ‘pipeline’) represents the workflows, activities, and automation needed to provide a continuous release of value to the end user. The pipeline consists of four elements: continuous exploration (CE), continuous integration (CI), continuous deployment, and release on demand.
Each Agile release train (ART) builds and maintains (or shares) a pipeline with the assets and technologies needed to deliver solution value as independently as possible. The first three elements of the pipeline work together to support delivery of small batches of new functionality, which are then released in accordance with market demand.
References:
Read more at: http://v5.scaledagileframework.com/continuous-delivery-pipeline/
Trainer Guidance:
An Epic is a container for a significant solution development initiative that captures the more substantial investments that occur within a portfolio.
A Capability is a higher-level solution behavior that typically spans multiple ARTs. Capabilities are sized and split into multiple features to facilitate their implementation in a single PI.
A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria and is sized or split as necessary to be delivered by a single agile release train (ART) in a program increment (PI).
Stories are short descriptions of a small piece of desired functionality written in the user’s language. Agile teams implement small, vertical slices of system functionality and are sized so they can be completed in a single iteration.
An Enabler supports the activities needed to extend the architectural runway to provide future business functionality. These include exploration, architecture, infrastructure, and compliance. Enablers are captured in the various backlogs and occur throughout the Framework.
The Portfolio Backlog is the highest-level backlog. It provides a holding area for upcoming business and enabler epics intended to create and evolve a comprehensive set of solutions.
The Program Backlog is the holding area for upcoming features, which are intended to address user needs and deliver business benefits for a single Agile release train (ART)
The Solution Backlog is the holding area for upcoming capabilities and enablers, each of which can span multiple ARTs and is intended to advance the solution.
Trainer Guidance:
After PI planning, we take the top ten approximate features. Ten isn’t a mandatory number, but an approximate estimation of the ideal amount (i.e., 30 is too many and 2 is not enough).
The vision answers the questions: “Why this feature? Why not this feature?” It helps organizations choose.
Key Message:
Developers will have to make thousands of decisions and will need this context to answer the questions. The developer now understands the thinking behind the decisions.
Then we break features down into stories.
Add then go to a program board to cross-check. The program board is a simple way to spot problems.
After the planning process, we aggregate the output into PI planning objectives.
Very complex solution in enterprise solution
Compliant always, involve all compliance ppl early
Lean portfolio configuration can be applied on essential version and large solution version
Portfolio linking strategy to execution
Requirements in SAFe
Epic is a term
Essential level features only
Lean portfolio configuration can be applied on essential version and large solution version
Portfolio linking strategy to execution
Requirements in SAFe
Epic is a term
Essential level features only
15 min
7 mins
While no two SAFe adoptions are identical, and they rarely follow a perfectly sequential step-by-step process, businesses typically get the best results when they follow a path similar to that shown in the SAFe Implementation Roadmap, which includes 12 steps. Each of the 12 steps is supported by a dedicated guidance article in the SAFe knowledgebase.
Tipping point you’re lacking any of quality productivity, time to market