SAFe Product Owner Product Manager Certification (Includes POPM Certification & Exam Training)
For Product Management professionals to apply Lean-Agile values and principles and economic prioritization, and develop skills in writing epics, Capabilities, Features, and user stories within the context of SAFe.
SAFe PO/PMs enable product development flow, drive ART execution, and operate in the enterprise to drive the continuous delivery of value.
What skills do you need to deliver value in an Agile enterprise? The SAFe® Product Owner and SAFe® Product Manager (POPM) course covers the tactical responsibilities of these roles in the Agile Release Train (ART). The course and resulting certification give you the guidance and tools to work effectively in remote environments with distributed teams.
Learn how product owners and product managers should work together to achieve the best possible customer and business outcomes. The SAFe POPM course will teach you how to adopt a customer-centric approach to building products, using the Scaled Agile Framework® to deliver more value, faster. Topics covered in this course include the daily role of POs and PMs; collaborating with engineering teams and business stakeholders; how to write epics, features, and stories; and how to design, prioritize, build, test, and deliver products with increased productivity and higher quality.
Who will benefit?
Includes current and aspiring:
- Product Managers
- Product Line Managers
- Product Owners
- Subject Matter Experts
- Business Owners
- Business and Systems Analysts
- Solution Managers
- Portfolio Managers
- Program Managers
- Project Managers
- PMO Professionals
- Process Leads
- Enterprise, Solution, and System Architects
- Scrum Master
- Release and Solution Train Engineers
- Agile Coaches
- SPCs
- Development Managers
- CTOs; Consultants
- Architects
- Engineers
- Directors
- Delivery Managers
- Release and Solution Train Engineers
- Software Developers.
2. What is the associated certification?
Certified SAFe® Product Owner/Product Manager (POPM)
3. What are the exam details?
Requirements
- Review and acceptance of the Candidate Agreement are required to start the exam
- Exam functionality instructions are provided following the Candidate Agreement
Exam Format
- Questions are structured in a multiple choice, single select format
- Exams are timed and the timer is displayed once questions are presented
- Exams will be submitted when thetimer ends, regardless of the number of questions answered
- Scores are calculated by the number of correctly answered questions
- Unanswered questions will be marked as incorrect
- “Submit” button ends the exam and a score will be calculated
Practice Test
- Format reflects the same number of questions, level of difficulty, timebox, and domain areas as the exam
- Unlimited attempts
- Passing the practice test does not guarantee passing the exam and is provided as a preparation resource
Details are subject to change at any time
|
Duration |
90 minutes |
|
Number of Questions |
45 |
|
Passing Score |
80% |
|
Delivery |
Web-based, closed book, no outside assistance |
|
Access |
Learning Plan (after course completion) |
|
Cost |
First attempt included in the course registration fee if taken within 30 days of course completion |
|
Retake Fee |
$50; $250 for SPC |
|
Retake Policy |
First retake - May be taken immediately after the first failed attempt. Second retake - May be taken 10 days after the first retake. Third retake - May be taken 30 days after the second retake. All subsequent retakes require a 30-day wait. |
Outline
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
Sorry! It looks like we haven’t updated our dates for the class you selected yet. There’s a quick way to find out. Contact us at 502.265.3057 or email info@training4it.com
Request a Date