ExamFinch.com My Study

Study guide

7.6 Agile Planning & Estimation

Practice this exam

Project Management Professional PMP

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Introduction & Fundamentals

1.1 About the PMP Exam 1.2 What is a Project? 1.3 Project, Program & Portfolio Management 1.4 The Project Manager Role 1.5 PMBOK 7 Principles Overview 1.6 Performance Domains Overview 1.7 What Changed in the July 2026 PMP Exam

2 Chapter 2: People Domain Part 1

2.1 Managing Conflict 2.2 Leading a Team 2.3 Supporting Team Performance 2.4 Empowering Team Members 2.5 Training & Development 2.6 Building a Team 2.7 Removing Impediments

3 Chapter 3: People Domain Part 2

3.1 Negotiating Project Agreements 3.2 Collaborating with Stakeholders 3.3 Building Shared Understanding 3.4 Engaging Virtual Teams 3.5 Defining Team Ground Rules 3.6 Mentoring Stakeholders 3.7 Emotional Intelligence

4 Chapter 4: Process Domain - Planning

4.1 Determining Project Methodology 4.2 Integrating Project Planning 4.3 Planning & Managing Scope 4.4 Planning & Managing Schedule 4.5 Planning & Managing Budget 4.6 Planning & Managing Quality 4.7 Planning & Managing Resources 4.8 Planning & Managing Procurement

5 Chapter 5: Process Domain - Execution & Control

5.1 Executing with Urgency for Value 5.2 Managing Communications 5.3 Assessing & Managing Risks 5.4 Engaging Stakeholders 5.5 Managing Project Changes 5.6 Establishing Project Governance 5.7 Managing Project Issues 5.8 Managing Project Artifacts 5.9 Knowledge Transfer & Closure

6 Chapter 6: Business Environment Domain

6.1 Planning & Managing Compliance 6.2 Evaluating & Delivering Benefits 6.3 External Environment Changes 6.4 Supporting Organizational Change

7 Chapter 7: Agile & Hybrid Approaches

7.1 Agile Mindset & Values 7.2 Scrum Framework 7.3 Kanban & Lean 7.4 Extreme Programming (XP) 7.5 Hybrid Project Management 7.6 Agile Planning & Estimation 7.7 Agile Metrics & Tools

8 Chapter 8: Predictive (Waterfall) Approaches

8.1 Predictive Lifecycle 8.2 Scope Management 8.3 Schedule Management 8.4 Cost Management 8.5 Quality Management 8.6 Risk Management Process 8.7 Procurement & Contracts 8.8 Change Control

7.6 Agile Planning & Estimation

Key Takeaways Explain This Topic AI

User stories follow the format: 'As a [user], I want [feature] so that [benefit]' to capture requirements from the user's perspective

Story points measure relative complexity, effort, and uncertainty -- not hours or days

The Fibonacci sequence (1, 2, 3, 5, 8, 13, 21) is commonly used for story point estimation

Velocity is the number of story points a team completes per iteration, used for capacity planning

  • Planning Poker uses consensus-based estimation where all team members vote simultaneously
  • Last updated: January 2026

Agile estimation differs fundamentally from traditional approaches. Instead of predicting exact hours or costs, Agile teams estimate relative size and use empirical data to forecast delivery.

User Stories

User stories are short descriptions of functionality from the user's perspective. They capture who wants what and why .

  • User Story Format As a [type of user],
  • I want [some feature],

So that [some benefit].

Example User Stories

Story Analysis

"As a customer, I want to save items to my cart so that I can purchase them later." Clear user, action, and benefit

"As an admin, I want to view usage reports so that I can track system performance." Specifies different user role

  • "As a mobile user, I want push notifications so that I stay informed on the go." Context-specific need
  • INVEST Criteria

Good user stories are:

  • Criterion Description
  • I ndependent Can be developed in any order
  • N egotiable Details can be discussed
  • V aluable Delivers value to the user
  • E stimable Team can estimate its size
  • S mall Fits within an iteration
  • T estable Has clear acceptance criteria
  • Story Points

Story points are a unit of measure for estimating the relative size of user stories. They combine:

Complexity : How complicated is the work?

Effort : How much work is involved?

Uncertainty : How much is unknown?

Key Characteristics

  • Aspect Story Points
  • Unit Relative, not absolute
  • Comparison Sized relative to reference stories
  • Team-specific Different teams have different scales
  • Not time A "5" doesn't mean 5 hours

Why Not Hours?

  • Hours-Based Estimation Story Point Estimation
  • Creates false precision Acknowledges uncertainty
  • Varies by person Team consensus
  • Easy to game Focuses on relative size
  • Stressful deadlines Empirical forecasting
  • The Fibonacci Sequence

Most teams use the Fibonacci sequence for story point values:

1, 2, 3, 5, 8, 13, 21, (34, 55, ...)

Why Fibonacci?

  • Reason Explanation
  • Natural progression Gaps increase with size
  • Acknowledges uncertainty Larger stories have more unknowns
  • Forces decisions Can't pick "between" numbers
  • Prevents false precision No difference between 14 and 15
  • Typical Scale Meanings
  • Points Typical Interpretation
  • 1 Trivial change, very low risk
  • 2 Simple, well-understood
  • 3 Straightforward but some effort
  • 5 Moderate complexity
  • 8 Complex, some uncertainty
  • 13 Very complex, high uncertainty
  • 21+ Should probably be split
  • Planning Poker

Planning Poker is a consensus-based estimation technique where the whole team participates.

  • How Planning Poker Works
  • Present the story : Product Owner describes the user story
  • Discuss : Team asks clarifying questions
  • Vote secretly : Each person selects a card with their estimate
  • Reveal simultaneously : All cards shown at once
  • Discuss differences : High and low voters explain their thinking
  • Revote if needed : Repeat until consensus emerges
  • Record : Final estimate is assigned
  • Benefits of Planning Poker
  • Benefit Why It Matters
  • Diverse perspectives Everyone's view counts
  • Prevents anchoring Simultaneous reveal avoids bias
  • Surfaces assumptions Discussion reveals hidden complexity
  • Team ownership Collective estimates create commitment
  • Knowledge sharing Less experienced team members learn
  • Velocity

Velocity is the number of story points a team completes per iteration.

  • Calculating Velocity Sprint 1: 23 points completed
  • Sprint 2: 27 points completed
  • Sprint 3: 25 points completed
  • Sprint 4: 24 points completed
  • Average Velocity = (23 + 27 + 25 + 24) / 4 = 25 points/sprint
  • Using Velocity
  • Application How
  • Sprint capacity Plan to take ~25 points next sprint
  • Release forecasting 100 points remaining / 25 per sprint = ~4 sprints

Trend analysis Is velocity increasing, stable, or declining?

  • Velocity Warnings
  • Don't compare team velocities : Story points are team-specific
  • Don't pressure for higher velocity : Gaming estimates helps no one
  • Watch for volatility : Large swings indicate estimation problems
  • Use ranges : Forecast with a range (e.g., 23-27 points)
  • Release Planning

Release planning determines what can be delivered and when.

  • Release Planning Steps
  • Prioritize the backlog : Rank by value, risk, dependencies
  • Size the stories : Estimate in story points
  • Determine velocity : Use historical average or estimate
  • Calculate duration : Total points / velocity = iterations
  • Set milestones : Identify key dates and deliverables
  • Example Release Plan
  • Iteration Stories Points Running Total
  • Sprint 1 A, B, C 24 24
  • Sprint 2 D, E, F 25 49
  • Sprint 3 G, H 26 75
  • Sprint 4 I, J, K 25 100
  • Release of 100 points in 4 sprints = 8 weeks (2-week sprints)
  • Iteration Planning

Iteration (Sprint) planning determines what will be done in the upcoming iteration.

Iteration Planning Process

  • Step Activity
  • Set capacity Account for PTO, meetings, holidays
  • Review priorities Product Owner presents top items
  • Select stories Team pulls stories up to capacity
  • Create tasks Break stories into development tasks
  • Confirm commitment Team agrees on the Sprint Goal
  • Capacity Considerations
  • Factor Impact
  • Team availability Vacations, holidays reduce capacity
  • Support duties Bug fixes, maintenance take time
  • Technical debt May reserve capacity for improvements
  • Team stability New members reduce initial velocity
  • Other Estimation Techniques
  • Technique Description Use Case
  • T-Shirt Sizing S, M, L, XL categories High-level backlog grooming
  • Affinity Estimating Group similar-sized items Large backlogs
  • Ideal Days Days of focused work Teams uncomfortable with points
  • Wideband Delphi Anonymous estimates with discussion Expert groups
  • PMP Exam Tips

According to the PMI-ACP exam content outline, Agile Estimation includes:

  • Relative sizing and story points
  • Planning Poker
  • Affinity estimating
  • Wideband Delphi
  • Ideal time

Key concepts :

  • Story points measure relative size , not time
  • Velocity is used for forecasting , not performance evaluation
  • Planning Poker ensures team consensus
  • The Fibonacci sequence reflects increasing uncertainty
  • Key Takeaways
  • User stories capture requirements from the user's perspective
  • Story points measure relative size, complexity, and uncertainty
  • The Fibonacci sequence (1, 2, 3, 5, 8, 13, 21) prevents false precision
  • Planning Poker uses simultaneous voting to prevent anchoring bias
  • Velocity is the empirical basis for forecasting delivery
  • Never compare velocity between teams or pressure teams to increase it

Fibonacci Sequence for Story Point Estimation