Chapter 19: Controlling a stage Flashcards
Controlling a Stage - Purpose
Ensure work is assigned, monitored, and corrective actions are taken to keep the stage within tolerance.
Controlling a Stage - Objective
Focus on delivery, control risks/issues, monitor the business case, and ensure products meet quality, cost, and time.
Controlling a Stage - Work Packages
Define and control work, set tolerances, and ensure team progress is monitored.
Controlling a Stage - Cycle
Cycle includes authorizing work, monitoring progress, reviewing work, reporting highlights, and managing risks/issues.
Controlling a Stage - Agile Equivalent
Agile stages (e.g., releases, sprints) focus on resource commitment and delivery, but differ from PRINCE2 stages.
Scrum of Scrums
A cross-team mechanism for coordination but not for project control. The project manager may choose to attend or facilitate.
Agile Work Assignment
Teams select work based on customer SME input, and work packages allow self-organization with flexible sign-offs.
Agile Monitoring & Reporting
Progress tracked via daily stand-ups, burn charts, and reviews during sprints/releases. Emphasis on empirical evidence.
Agile Risks & Issues
Identified during daily stand-ups, retrospectives, and reviews. Regular monitoring ensures no impact on goals.
PRINCE2 Agile - Activities
PRINCE2 activities map to Agile artefacts like backlogs, burn charts, and retrospectives for controlling stages.
Retrospectives - Purpose
Reflect on team processes to improve work practices continuously.
Retrospectives - Structure
Retrospectives should be planned, structured, and include actions for improvement. Follow a clear agenda.
Retrospectives - Feedback
Collect factual and emotional feedback from team members to improve the process.
Agile Continuous Improvement
Learn from small, incremental changes. Gradual improvement leads to better team processes over time.
