SAFe Core Values | Alignment
Transparency
Built-in Quality
Program Execution |
Examples of Alignment? | Communicate the mission, vision and strategy
Provide briefings and participate in PI planning
Participate in backlog review and preparation
Organize around value streams
Constantly check for understanding |
Examples of Transparency? | VIsualize all relevant work
Take ownership and responsibility for errors
Admit your own mistakes
Support others who acknowledge and learn from their mistakes - never punish the messenger |
Examples of Built-in Quality | Refuse to accept low-quality work
Support investments in technical debt reduction
Ensure UX, Architecture, Security, Compliance, operations and others are part of the flow of work |
Examples of Program Execution | Participate as an active business owner
Celebrate high quality and predictably delivered PI's
Aggressively remove impediments and demotivators |
What are the features of an Agile Team | Cross functional teams
Collaboration
Fast feedback |
What is Agile Manifesto? | Individuals and Interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan |
What are the characteristics of Agile development | Iterative
Collaborative
Adaptive
Incremental |
Characteristics of SAFe House of Lean | Flows from Leadership to Value
Respect for people and culture
Innovation
Relentless improvement |
How to achieve VALUE | The best quality to people and society
High morale, safety and customer delight |
Key char of Respect for people and culture | Generative culture
People do all the work
Build long term partnerships based on trust
To change the culture, you have to change the organization |
Key char of FLOW | Optimize sustainable value delivery
Build in quality
Understand, exploit and manage variability
Move from projects to products |
Key features of Innovation | Innovative people
Provide time and space for innovation
Go See
Experimentation and feedback
Innovation riptides
Pivot without mercy or guile |
Relentless Improvement | Constant sense of danger
Optimize the whole
Problem-solving culture
Reflect at key milestones |
Key features of Leadership | Lead by example
Adopt a growth mindset
Exemplify the values and principles of Lean-SAFe
Develop people
Lead the change
Foster psychological safety |
12 Agile Manifesto principles | Highest priority is to satisfy the customer through early and continuous delivery of valuable software
Welcome change in requirements, even late in development
Deliver working software frequently, from couple of weeks, to couple of months
Business people and developers should work together daily throughout the project
Build projects around motivated individuals
Most efficient and effective method of communication is face-to-face conversation
Working software is the primary measure of progress
Agile processes promote sustainability development
Continuous attention to technical excellence and good design enhances agility
Simplicity - maximizing the amount of work not done - is essential
Self organizing teams
Regular introspection and course correction |
What the the SAFe Lean-Agile principles(10) | Take and economic view
Apply systems thinking
Assume variability; preserve options
Build incrementally, with fast, integrated learning cycles
Base milestones on objective evaluation of working systems
Visualise and limit WIP, reduce batch sizes and manage queue lengths
Apply cadence and synchronize with cross-domain planning
Unlock the intrinsic motivation of knowledge workers
Decentralize decision making
Organize around value |
Attributes of System thinking | Optimizing a component does not optimize the system
A higher level understanding of behavior and architecture is required for a system to behave well as a system
The value of a system passes through its interconnections
A system can evolve no faster than its slowest integration point |
Explain Fast learning cycles | Fast feedback accelerates knowledge
Improves learning efficiency by decreasing the time between action and effect
Reduces the cost of risk-taking by truncating unsuccessful paths quickly
Is facilitated by small batch sizes
Requires increased investment in development environment
The shorter the cycles the faster the learning |
Advantages of reducing Batch size | Increases predictability
Accelerates feedback
Reduces work
Lowers cost |
How much can be saved by batch size reduction? | Approximately twice the cost |
What is Little's Law? | Faster processing time decreases wait
Shorter queue length decreases wait |
How can you control wait times? | By controlling queue lengths
Enforcing WIP limits
Having small batches
Defer commitments |
Advantages of CADENCE | Converts unpredictable events into predictable occurrences and lowers cost
Makes waiting time for new work predictable
Supports regular planning and cross-functional coordination
Limits batch sizes to a single interval
Controls injection of new work
Provides scheduled integration points |
Advantages of Synchronization | Causes multiple events to happen simultaneously
Facilitates cross-functional trade offs
Provides routine dependency management
Supports full stem integration and assessment
Provides multiple feedback perspectives |
What is Value Stream? | The aim of development is in fact creation of profitable and operational value-streams
It includes activities from recognizing an opportunity through release and validation
Contains the steps, the flow of information and material, and the people who develop the solution used by the Operational Value Streams. |