Defining the Work
How is Project Scope Defined?
Through a product backlog that evolves over time.
How is the project schedule developed?
Through sprints and iterations.
When are risks identified?
Continuously throughout the project.
How is quality planned?
Built-in through continuous integration and testing.
What type of contracts are used?
Flexible contracts like time-boxed or value-driven.
What tool is commonly used to organize the project work?
Product backlog or user story mapping.
What tools are used for tracking time?
Sprint boards and burndown charts.
How are risks documented?
Often discussed in daily stand-ups and retrospectives.
What role does testing play?
Done continuously with each iteration.
How are vendor relationships handled?
Collaborative partnerships.
Who is responsible for defining project requirements?
Product owner with input from stakeholders.
When are tasks assigned?
During sprint planning meetings.
Who owns risk management?
Shared by the team.
Who ensures quality?
The whole team shares responsibility.
When is the contract finalized?
May evolve during the project
When is scope finalized?
Continuously refined throughout the project.
What happens when tasks are delayed?
Items may be moved to the next sprint.
How are mitigation plans created?
Created as risks are identified in real time.
What tools ensure quality?
Automated testing and regular feedback.
How is change handled in contracts?
Through mutual agreement and re-prioritization.
What happens when new work is identified?
New items are added to the product backlog.
Who manages the schedule?
The team collaboratively manages it.
What is the risk response strategy?
Adapt quickly and minimize impact through iteration.
When is quality measured?
After each sprint or iteration.
What is the focus of the contract?
Outcomes and business value.