Awesomely Agile
Risky Business
Predictive
RACI
Estimating Techniques
100

This ceremony happens before the sprint begins, during which the PO and team collaborate on the work for the upcoming sprint. 

Sprint (Iteration) Planning Ceremony 

100

Useful project artifact to track known project risks. 

Risk Register, aka Risk Log or Risk List 

100

A common horizontal bar chart used in project management to visualize a project schedule. 

Gantt Chart

100

Person accountable for authorizing the project, providing support and resources, and helping ensure the project delivers business value. 

Project Sponsor

100

This technique is useful early in planning when detailed task information is limited, but a broad project estimate is still needed.

Top Down or Analogous Estimating 

200

This is the output of the Sprint Planning ceremony. 

Sprint (Iteration) Backlog

200

This threat response strategy is used to reduce the impact of a risk. 

Mitigate

200

a hierarchical visual breakdown of project work. 

WBS

200

This project role is usually responsible for creating the product, service, or result.

The team

200

This estimating technique creates detailed estimates for individual activities or work packages, then rolls them up into a total project estimate.

Bottom Up

300
A prioritized list of user stories ranked by the Product Owner. 

Product Backlog

300

When a risk remains after planning a risk response. 

Residual Risk

300

A committee of high-level project stakeholders that review/ analyze proposed project changes. 

CCB

300

This role is responsible for coordinating project activities, updating project documents, and helping keep the team aligned with the project objectives.

Project Manager

300

This technique estimates cost or duration by multiplying a known rate by the number of units needed.

Parametric

400
A specialized sprint dedicated to quality assurance. 

Iteration H or Hardening Sprint

400

Risk planning tool for analyzing external risk by looking at a wide range of various types of risk. 

PESTLE 

400

A tool or "checklist" used for ensuring ALL project requirements are accounted for in a project. 

RTM

400

This project role is often consulted for input because they understand the customer’s needs, requirements, and expected value.

Product Owner

400

This estimating technique may use a triangular or beta distribution to calculate a more realistic estimate when uncertainty exists.

Three Point

500

Agile teams use this estimating method, which uses numbers from the Fibonacci sequence to estimate the effort required to complete user stories. 

Planning Poker

500

A risk estimating method that uses expert opinions and voting anonymously. 

Delphi Technique

500

A type of histogram that ranks causes of problems and helps identify the few causes responsible for the largest number of problems.

Pareto Chart

500

This project role is often consulted for input on requirements, business needs, and stakeholder expectations before decisions are finalized.

Business Analyst

500

A project manager has a detailed WBS and asks each team lead to estimate the work packages they are assigned. The estimates are then added together to create the total project estimate. Which estimating technique would you use? 

Bottom Up