PI Execution Flashcards
What does WSJF stand for?
“Weighted Shortest Job First”
What is the WSJF formula?
WSJF = [Cost of Delay] / [Job Duration]
==OR==
WSJF = [(User-Business Value) + (Time Criticality) + (RR or OE)] / [Job Duration]
- RR = Risk Reduction
- OE = Opportunity Enablement
What 3 values are used to calculate the Cost of Delay?
User-business value – What is the relative value to the customer or business? Do our users prefer this over that? What is the revenue impact on our business? Is there a potential penalty or other negative effects if we delay?
Time criticality – How does the user/business value decay over time? Is there a fixed deadline? Will they wait for us or move to another solution? Are there Milestones on the critical path impacted by this? What is the current effect on customer satisfaction?
Risk reduction-opportunity enablement value – What else does this do for our business? Does it reduce the risk of this or a future delivery? Is there value in the information we will receive? Will this feature enable new business opportunities?
What are the 5 PI events that occur at the Team level?
- Iteration Planning
- Daily Stand-up
- Iteration Review
- Backlog Refinement
- Iteration Retro
What are the 5 PI events that occur at the ART level?
- PI Planning
- ART Sync (Scrum of Scrums / PO Sync)
- System Demo
- Prepare for PI Planning
- Inspect & Adapt
What are the 7 PI events that occur at the Solution level?
- Pre-PI Planning
- Post-PI Planning
- Solution Train Sync
- Architect Sync
- Solution Demo
- Prepare for PI Planning
- Inspect & Adapt
What are the Goals, Inputs, and Outputs of Pre-PI Planning?
-
Goals:
- Align Product Managers, System Architects, and other ART stakeholders to a common Vision
- Prepare content for ART PI Planning
-
Input:
- Results of the previous PI execution
- Outcomes of the Solution Demo or, if delayed, ART demos
- Roll-up of the program predictability measure to the Solution Train
-
Output:
- A set of Features for every ART
- Updates to the ART Visions
What are the Goals, Inputs, and Outputs of Post-PI Planning?
-
Goals
- Understand the PI plan for the entire Solution Train
- Adjust if necessary and communicate to the ARTs
-
Inputs
- Program PI Objectives from all ARTs
- Solution Train board
- Solution risks
-
Outputs
- Set of SMART Solution PI Objectives for the Solution Train
- Updated Solution planning board
- Commitment based on a confidence vote
The Inspect & Adapt Event is made of what 3 parts?
- PI System Demo
- Quantitative and Qualitative Measurement
- Retrospective and Problem-Solving Workshop
What happens in the “Quantitative and Qualitative Measurement” phase of the I&A Event?
- Program Predictability measure gauges performance of the ART
- Architects are accountable for the business value scores of Enabler Features and Capabilities
- Architects should also measure value delivered against architecture hypotheses
What happens during a “Retrospective and Problem-Solving Workshop”?
- Retrospective
- team problem identification activity
- goal is to identify system issues to be addressed (program-level in scope)
- teams contribute own views of the problem
- identified issues ‘seed’ the problem-solving workshop
- Problem-Solving Workshop
- Agree on the problem to solve
- Apply root cause analysis
- Identify the biggest root-cause using Pareto Analysis
- Restate the new problem for the biggest root cause
- Brainstorm solutions
- Identify improvement backlog items