Who's who?
This senior leader provides strategic direction, secures funding, and helps resolve major issues for the project.
Project Sponsor
This brief ceremony keeps the team coordinated by focusing on what was completed, what will be worked on next, and any impediments blocking progress.
Daily Scrum or Daily Stand-Up or Daily Coordination Meeting
This living project document serves as the central repository for known risks, their characteristics, planned responses, owners, and current status throughout the project.
Risk Register
This document formally authorizes the project and gives the project manager authority to apply organizational resources to project activities.
Project Charter
This estimating technique uses historical data from a similar past activity or project to estimate the duration or cost of the current one.
Analogous Estimating or Top-Down
This role leads the project team, coordinates the work, and manages project activities such as scope while guiding the project from initiation through closure.
Project Manager
At the beginning of an iteration, the team uses this ceremony to select and plan the work it intends to complete, creating the Sprint Backlog.
Iteration/Sprint Planning
These reserves are built into the cost baseline to address identified risks whose exact timing or impact is still uncertain.
Contingency Reserves
This graphical artifact decomposes the project’s deliverables into smaller, more manageable components, with work packages at its lowest level.
WBS
A team knows that installing one unit typically requires four labor hours. They multiply that rate by the number of units to estimate the total effort using this technique.
Parametric
This role facilitates adaptive team coordination, helps remove impediments, and supports the team in managing its own work.
Scrum Master
This artifact contains the features, requirements, fixes, and other work that may be needed for the product, and it is continually refined as priorities change.
Product Backlog
When a valuable opportunity presents itself, this response strategy takes action to ensure the opportunity is realized, rather than simply increasing its probability or impact.
Exploit
This project document records key people and groups along with information such as their roles, requirements, expectations, influence, and level of support, and it should be updated as those relationships evolve.
Stakeholder Register
This estimating technique starts with the lowest-level components of the work, estimates them individually, and then rolls those estimates up to determine the total cost or duration.
Bottom Up
After a review, customers request several competing features. This role decides which should be addressed first based on value and updates the order of future work without directing how the team performs it.
Product Owner
This dedicated quality-focused iteration may be used to correct defects, complete testing, and help ensure the product meets required quality standards before release.
Iteration H or Hardening Sprint
A team implements a mitigation strategy that significantly reduces a threat, but some exposure still remains. This term describes the portion of the original risk that remains after the response has been implemented.
Residual Risk
A supplier strike that had previously been identified as a threat has now occurred. The team agrees on a workaround, assigns an owner and due date, sets the priority, and tracks the action through resolution in this artifact.
Issues Log
This estimating technique accounts for uncertainty by considering optimistic, most likely, and pessimistic estimates for the work.
Three-Point
Before a project is formally authorized, this role analyzes the business need, gathers high-level requirements, evaluates potential benefits and costs, and often develops the business case used to determine whether the project should move forward.
Business Analyst
An organization is transitioning several teams from predictive to adaptive ways of working. This role trains and mentors the teams while also guiding the broader organization through the transformation.
Agile Coach
This quantitative risk analysis technique runs numerous possible project scenarios using probability distributions to estimate the range and likelihood of potential outcomes.
Monte Carlo Simulation
A proposed baseline change has been reviewed by the appropriate decision-makers. The project manager now needs to document whether it was approved, rejected, or deferred and track its disposition throughout the project in this artifact.
Change Log
An activity could take as little as 5 days, would normally take about 8 days, and could take as long as 17 days. Using the Beta Distribution formula, this is the expected duration.
9 days