Core Values of SAFe
- Built-in Quality
- Program Execution
- Alignment
- Transparency
Value Streams
- series of steps an organization uses to
... [Show More] implement Solutions that provide a continuous flow of value to a Customer
- used to define and realize portfolio-level business objectives and organize Agile-team to deliver value more rapidly
- contains the system, the people who do the works, and the flow of information and materials
Operational Value Stream
Contains the steps and the people who deliver end-user value using the business Solutions created by the development Value Stresms
Development Value Streams
Contains the steps and the people who develop the business Solutions created by the Operational Value Streams
Solution
may be a product, product line, a set of systems or a service that enables an Operational Value Stream
House of Lean
- Goal: Value
- Foundation: Leadership
- Pillars Respect for People and Culture, Development Flow, Innovation, Relentless Improvement
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
SAFe Lean-Agile Principles (#1-#5)
#1 Take an Economic View
#2 Apply System Thinking
#3 Assume variability, preserve options
#4 Build incrementally with fast, integrated learning cycles
#5 Base milestones on objectives evaluation of working systems
SAFe Lean-Agile Principles (#6-#10)
#6 Visualize and limit WIP, reduce batch size, and manage queue lengths
#7 Apply cadence, synchronize with cross-domain planning
#8 Unlock the intrinsic motivation of knowledge workers
#9 Decentralize decision-making
#10 Organize around value
PI Planning
-cadence-based are the heartbeat of the Agile Enterprise
- 2 days every 8-12 weeks (10 weeks is typical)
- attend in person (if possible)
- PM owns Feature priorities
- Agile teams own Stroy planning and high-level estimates
- architect/engineering and UX work as intermediaries for governance, interfaces, and dependencies
PI Planning Preparation
- Create/update Vision and Roadmaps
- Socialize the Top 10 Features and Enablers to set expectations for the PI Planning meeting
- too much preparation can inhibit exploration, interaction, and emergent designs/solution during PI Planning
NFR
Non-functional requirements are key architecture concerns and system qualities that are sometimes known as "ilities" - reliability, usability, scalability, etc [Show Less]