Chapter Two Flashcards
What is a Program Increment (PI)?
A timebox during which an ART delivers incremental value in the form of working, tested software and systems
Typically takes 8-12 weeks that consist of development iteration and Invocation and Planning Iteration (IP)
What is PI Planning?
An event where everyone meets and plans together.
Product management owns feature priorities, agile team owns story planning and high-level estimates
What is a PI objectives?
Business summaries of what each team intends to deliver in the upcoming Program Increments (PI)
If unable to meet the objective, encourage team to move it to uncommitted objectives
Who creates the Vision for the ART?
Product Management creates the vision, which evolves from customer feedback and learnings from the ART
When drafting a vision, it must be
Aspirational, yet realistic and achievable
Motivational enough to engage others on the journey
What are EPICS?
A container for a significant Solution development initiative that captures the more substantial investments that occur within a portfolio.
What is a FEATURE?
A service that fulfills a stakeholder’s need.
It is sized or split, to be delivered by an ART in a PI.
What are STORIES?
Short descriptions of small piece of desired functionality, written from the user’s perspective.
What are ENABLERS?
They support the activities needed to extend the Architectural Runway to provide future business functionality.
What makes features and Stories different from the other?
Features fit in one PI for one ART. Stories fit in one iteration for one team.
What three things do Story capture?
User’s role, activity and goal. They’re formatted in the form of As a… I want… so that.
Definition of done - System Increment
Stories completed by all teams in the ART and integrated
No must-fix defects
Acceptance by product manager
Definition of done - Solution Increment
Capabilities completed by all trains and meet acceptance criteria
Documentation updated
Solution demonstrated; feedback achieved
Accepted by Solution Management
Definition of done in release
All capabilities done and meet acceptance criteria
Regression testing done
Approved by Solution and Release Management
Program backlog
The holding area for upcoming features that will address users needs and deliver business benefits for a single ART
