SAFe PO/PM Exam: Questions With Proper Solutions
Story analysis & estimation Right Ans - - The PO presents Stories in order
of priority
- PO re-iterates iteration goals
- Each Story:
* is discussed & analyzed by the team
* has its acceptance criteria
* is estimated (dependent upon volume, complexity, knowledge, and
uncertainty about the user story)
* Definition of Done
- The process continues until the estimation of the Stories has reached the
velocity of the team
- uses Planning Poker/Fibonacci
- Restate the iteration goals at the end of the ceremony
- Confidence vote 1-5 to gauge commitment to the iteration goals.
Program Board Right Ans - where feature delivery, dependencies, and
milestones are displayed
contains teams, enablers, and milestones on the Y-axis
contains iterations on the x-axis
Leveraged by ART's/Programs
ROAM technique Right Ans - A strategy used to help manage actions after
risks arise; stands for resolved, owned, accepted, and mitigated
Agile Methodology Right Ans - Combines Lean Portfolio Management,
Scrum (team management), Agile (Program Management)
SAFe captures all aspects at scale
Has 10 principles, practices, and 7 competencies
,Value Streams Right Ans - 1-3 years
Epic-level
Executive-level sponsorship
Must have Operational and Development value stream components
Managed at the Lean Portfolio Management level
Combination of Front-end, Ops Value Stream and Back-end Technical
Solutions
end-to-end streams of value
Solution team Right Ans - Manages Capabilities
Below Value Steam/Epic/Business Team
Above Program Teams
Interfaces between the business and IT portfolio
Program Team Right Ans - Execute Release Trains and PI's
Product Managers own
System Architects interact
Focus on Features
Below Solution Teams, above Development Teams
Scrum Team Right Ans - Execute 2-week iterations
Participate in PI's
Managed by Scrum Masters and Product Owners
, Executes Features set out by Product Managers, manages stories/backlog
items
Agile Core Competencies (7) Right Ans - A set of related knowledge, skills,
events, and behaviors, which together enable organizations to achieve
business agility.
Organizational Agility
Lean Portfolio Management
Enterprise Solution Delivery
Agile Product Delivery
Team and Technical Agility
Continuous learning culture
Lean-Agile Leadership
Agile Core Values / Agile Manifesto Right Ans - We are uncovering better
ways of developing software by doing it and helping others do it.
individuals and interactions over processes and tools;
working software over comprehensive documentation;
customer collaboration over contract negotiation;
responding to change over following a plan.
Transparency
Alignment
Built-in quality
Program Execution
House of Lean (Lean-Agile Mindset) Right Ans - Goal: Value Foundation:
Leadership, Respect for People and Culture, Development Flow, Innovation,
Relentless Improvement
Achieving value in the shortest attainable time
Agile Manifesto Principles Right Ans - 1. Customer Satisfaction through
early and continuous delivery
2. Welcome change in requirements, even late in the development process;
harnesses change for the sake of the customer's competitive advantage
3. Deliver working software frequently (weeks or months)
Story analysis & estimation Right Ans - - The PO presents Stories in order
of priority
- PO re-iterates iteration goals
- Each Story:
* is discussed & analyzed by the team
* has its acceptance criteria
* is estimated (dependent upon volume, complexity, knowledge, and
uncertainty about the user story)
* Definition of Done
- The process continues until the estimation of the Stories has reached the
velocity of the team
- uses Planning Poker/Fibonacci
- Restate the iteration goals at the end of the ceremony
- Confidence vote 1-5 to gauge commitment to the iteration goals.
Program Board Right Ans - where feature delivery, dependencies, and
milestones are displayed
contains teams, enablers, and milestones on the Y-axis
contains iterations on the x-axis
Leveraged by ART's/Programs
ROAM technique Right Ans - A strategy used to help manage actions after
risks arise; stands for resolved, owned, accepted, and mitigated
Agile Methodology Right Ans - Combines Lean Portfolio Management,
Scrum (team management), Agile (Program Management)
SAFe captures all aspects at scale
Has 10 principles, practices, and 7 competencies
,Value Streams Right Ans - 1-3 years
Epic-level
Executive-level sponsorship
Must have Operational and Development value stream components
Managed at the Lean Portfolio Management level
Combination of Front-end, Ops Value Stream and Back-end Technical
Solutions
end-to-end streams of value
Solution team Right Ans - Manages Capabilities
Below Value Steam/Epic/Business Team
Above Program Teams
Interfaces between the business and IT portfolio
Program Team Right Ans - Execute Release Trains and PI's
Product Managers own
System Architects interact
Focus on Features
Below Solution Teams, above Development Teams
Scrum Team Right Ans - Execute 2-week iterations
Participate in PI's
Managed by Scrum Masters and Product Owners
, Executes Features set out by Product Managers, manages stories/backlog
items
Agile Core Competencies (7) Right Ans - A set of related knowledge, skills,
events, and behaviors, which together enable organizations to achieve
business agility.
Organizational Agility
Lean Portfolio Management
Enterprise Solution Delivery
Agile Product Delivery
Team and Technical Agility
Continuous learning culture
Lean-Agile Leadership
Agile Core Values / Agile Manifesto Right Ans - We are uncovering better
ways of developing software by doing it and helping others do it.
individuals and interactions over processes and tools;
working software over comprehensive documentation;
customer collaboration over contract negotiation;
responding to change over following a plan.
Transparency
Alignment
Built-in quality
Program Execution
House of Lean (Lean-Agile Mindset) Right Ans - Goal: Value Foundation:
Leadership, Respect for People and Culture, Development Flow, Innovation,
Relentless Improvement
Achieving value in the shortest attainable time
Agile Manifesto Principles Right Ans - 1. Customer Satisfaction through
early and continuous delivery
2. Welcome change in requirements, even late in the development process;
harnesses change for the sake of the customer's competitive advantage
3. Deliver working software frequently (weeks or months)
