Develop the skillsets needed to guide the delivery of value in a Lean enterprise—and learn about the activities, tools, and mechanics used to manage backlogs and programs—by becoming a SAFe® 4 Product Owner/Product Manager (POPM). During this two-day course, attendees will gain an in-depth understanding of the Agile Release Train (ART), how it delivers value, and what they can do to effectively perform their role.
They will also learn how to apply Lean thinking to write Epics, break them down into Features and Stories, plan and execute Iterations, and plan Program Increments. Finally, attendees learn about the Continuous Delivery Pipeline and DevOps culture, how to effectively integrate as Product Owners and Product Managers, and what it takes to relentlessly improve the ART.
2 days
The following individuals will benefit from this course: • Product Managers, Product Line Managers, Product Owners, Business Owners, and Business Analysts • Solution Managers, Portfolio Managers, Program Managers, PMO personnel, and Process Leads • Enterprise, Solution, and System Architects
Prerequisites:
All are welcome to attend the course, regardless of experience. However, the following prerequisites are highly recommended for those who intend to take the SAFe® 4 Product Owner/Product Manager (POPM)certification exam:
- Attend a Leading SAFe® course
- Experience working in a SAFe environment
- Experience with Lean, Agile, or other relevant certifications
To perform the role of a SAFe® Product Owner/Product Manager, attendees should be able to:
- Apply SAFe in the Lean enterprise
- Connect SAFe Lean-Agile principles and values to the PO/PM roles
- Collaborate with Lean Portfolio Management
- Explore continuous value with Program Increment Planning
- Execute the Program Increment and deliver continuous value
- Articulate the Product Owner and Product Manager roles
- Create a role action plan
SAFe PO/PM Workshop – Day 1
- Introduction with Agenda
- SAFe Overview
Lean-Agile & Business Benefits
- Keeping Pace
- The Management Challenge
- The Scaled Agile Framework
- Roots of SAFe
- SAFe Contributors
- SAFe Delivery Business Results
SAFe Core Values
- SAFe House of Lean (Value, Respect for People & Culture, Flow, Innovation, Relentless Improvement & Leadership)
- Agile Manifesto
- Agile Teams
- Code Quality
- Scale to Program Level
- Develop on Cadence, Release on Demand
- Program Execution
- The ART
- What’s a PI
- Scale to Portfolio
- Alignment
- Program Portfolio Management
- Agile Program Portfolio Management
- Transparency
Leadership
- Delivering Features
- Product Owner/Product Manager Roles
- Traditional v/s Agile Product Management
- Product Manager & Product Owner
- Product Manager Attributes
- Product Owner Attributes
- Release Content Governance
Enterprise Backlog Model
- Governance: Content Authority
- The Enterprise Backlog Model
- Connecting the Portfolio to the Business
- Formulating Strategic Themes
- Influence of Strategic Themes
- Centralize Strategy. Localize Execution
- Epics Carry Centralized Initiatives
- Epic Owner
- Lightweight Business Case
- Epic Value Statement Template
- Features & Product Backlog
- Stories & The Team Backlog
- Agile Software Requirements – Elaborated Information Model
- Backlogs Bring Ideas Together
Delivering Features – Program Activities
- Delivering Features in the Enterprise
- Activity: Build/Maintain Vision & Roadmap
- Program Vision & Roadmap
- Program Vision
- Common Formats For Vision
- Roadmap
- NFRs are Key Architectural Concerns
- Non-Functional Requirements (NFRs)
- NFR Examples
- NFR Types
- NFRs in the Agile Testing Quadrants
- Activity: Refine Program Backlog
- Define Features by Type of Service
- How much Architecture?
- Prioritizing Program Backlog for Optimal ROI
- CoD Economics: Shortest Job First
- Equal Cost of Delay
- CoD Economics: High Delay Cost First
- Equal Duration
- CoD Economics: Weighted Shortest Job First
- Components of Cost of Delay
- How do we calculate Duration?
- Relative Sizing with Story Points
- The Fibonacci Sequence
- SAFe Estimating
- How Much Time to Spend Estimating?
- Features & Benefits Template
- WSJF Prioritization Matrix
- Estimating Features Effort
- Preliminary: Gross, Relative Estimating
- Refined: Estimate in Story Points
- Final: Bottom-up, Team-Based Estimating
- Estimating Cost
- Starting Fast with Capacity-Based Planning
- Estimating Development Time
- Splitting User Stories
- Split by Workflow steps
- Split By Business Rule Variations
- Split By Major Effort
- Split By Simple/Complex
- Split By Variations in Data
- Split By Data Methods
- Split By Deferring System Qualities
- Split By Operations
- Split By Case Scenarios
- Split – If All Else Fails, Break Out A Spike
- Activity: Prepare For Release Planning
- Balance Technical Debt
- Program Event – Release Planning
- The Release Planning Process
- Event: Release Planning Meeting
- Each Team Contributes to Release Planning Results
- Event: Scrum Of Scrums
- Execute the PI
- Program Execution
- Activity: Frequently Integrate
- Event: Release Management Meeting
- Event: Manage Dependencies
- Event: System Demo
- Event: Inspect & Adapt
- Inspect & Adapt For Program Performance
- Activity: Build/Maintain Development & Deployment Infrastructure
- Activity: Build/Maintain Architectural Runway
- Architectural Runway
- Develop on Cadence. Release on Demand
- Activity: Release on Demand
- Other Significant Touch Points
- PI Progress Tracking
- Release Predictability Report
- PI Feature Completeness Report
- PI Performance Summary
SAFe PO/PM Workshop – Day 2
- Delivering Features – Team Activities
- SAFe ScrumXP
- Sources Of Backlog Items
- Prioritization & Sequencing
- Team Backlog Sequencing
- Team Activities: Sprint Planning Meeting
- Sprint Planning Flow
- Team Activities – Daily Scrum
- Track Sprints At Story Level
- Big Visible Information Radiators (BVIRs)
- Track Sprint Status With Burndown Charts
- Mid-Sprint Events
- Mid-Sprint Review
- Team Ceremonies/ Team Backlog Refinement
- Team Ceremonies/ Team Specification Workshop
- Team Activities/ Sprint Demo
- Definition Of Done
- SAFe Definition Of Done
- Concluding the Sprint Demo – Two Views
- PI Release Burn-Down Chart
- The Sprint Retrospective Meeting
- Story Completion – Lessons Learned
- Summary – SAFe Events
- Agile Requirements
- Features Driven User Stories
- User Stories
- Solution Roles
- Identifying Roles
- Understanding Roles
- Role Modeling Examples
- The Requirements Workshop
- Brainstorming & Idea Reduction
- Specification Workshops Get Specific
- Acceptance Test Driven Development (ATDD)
- User Story Guidelines – 3 C’s
- Card: User Story Voice Form
- Applying User-Voice Format
- Conversation: Story is a placeholder for Conversation
- Confirmation: Acceptance Criteria
- Acceptance Criteria vs. Definition of Done
- Acceptance Criteria and Splitting Stories
- Stories Are Lumpy
- Just-In-Time Story Elaboration – When?
- Leverage The “Whole Team” Story Writing
- Accepting User Stories
- Not All Stories Are User Value Stories
- Spikes – Not Everything Is a User Story
- Stakeholder Management
- The Stakeholder Management Process
- Rights And Responsibilities
- Communicating Expectations
- Intervening Stakeholders
- The Influence/Interest Matrix
- The Stakeholder Map
- Sample Stakeholder Management Plan
