Skip to main content

Domain V: Adaptive Planning

  • Chapter
  • First Online:

Abstract

This is one of the most important chapters as far as the PMI-ACP exam is concerned. The chapter is fairly exhaustive in terms of coverage of many terms and key concepts that are required for Agile projects. Also the position of this chapter is apt, almost in the middle of the book, which reflects that planning takes the center stage in Agile projects and other domains revolve around it.

This is a preview of subscription content, log in via an institution.

Buying options

Chapter
USD   29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD   54.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD   69.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Learn about institutional subscriptions

Notes

  1. 1.

    Refer to Agile Software Development – The Cooperative Game, 2nd ed. authored by Alistair Cockburn. (Upper Saddle River, NJ: Pearson Education, 2006).

  2. 2.

    Refer to 5 Process Groups and 10 Knowledge Areas as defined in PMI®’s A Guide to the Project Management Body of Knowledge ( PMBOK® Guide) – Fifth Edition.

  3. 3.

    Refer to Chapter 1 : Agile Principles and Mindset.

  4. 4.

    Refer to Chapter 1 : Agile Principles and Mindset.

  5. 5.

    The Estimate Convergence Graph comes from Barry Boehm.

  6. 6.

    Refer to the online video at http://pomodorotechnique.com/

  7. 7.

    Refer to Chapter 3: Value-driven Delivery for a discussion on project charter.

  8. 8.

    Refer to the discussion on Scrum in Chapter 2: Agile Methodologies.

  9. 9.

    The concept of velocity is described in detail later in this chapter.

  10. 10.

    Refer to the third Agile principle (in Chapter 1: Agile Principles and Mindset) that states “Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.”

  11. 11.

    Student’s syndrome is discussed earlier in this chapter.

  12. 12.

    Refer to discussion on ATDD in Chapter 7: Problem Detection and Resolution.

  13. 13.

    Refer to https://cucumber.io/ .

  14. 14.

    Extreme programming was founded and advocated by Kent Beck, Ward Cunningham. and Ron Jeffries.

  15. 15.

    Refer to: https://confluence.atlassian.com/jiraportfoliocloud/classic-plans-802170593.html

  16. 16.

    Refer to Agile Estimation and Planning authored by Mike Cohn. (Upper Saddle River, NJ: Prentice Hall, 2005).

  17. 17.

    Refer to Chapter 2 for the discussion on Definition of Done.

  18. 18.

    Refer to detailed discussion on personas in Chapter 4: Stakeholder Engagement.

  19. 19.

    Refer to User Stories Applied by Mike Cohn. (Boston: Addison-Wesley, 2014).

  20. 20.

    Refer to PMI®’s A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Fifth Edition.

  21. 21.

    Sashimi is a Japanese dish of thin slices of fresh raw fish or meat, often served with dips like soy sauce and wasabi paste.

  22. 22.

    Data based on Google Maps.

  23. 23.

    Jira is an opensource software development tool that helps in tracking and monitoring: https://www.atlassian.com/software/jira

  24. 24.

    Refer to Software Engineering Economics authored by Barry Boehm. Prentice Hall (October 22, 1981).

  25. 25.

    Refer to Agile Estimating and Planning authored by Mike Cohn. Prentice Hall (November 1, 2005).

    Mike Cohn, founder of Mountain Goat Software, LLC has also trademarked the term Planning Poker.

  26. 26.

    A pack of Planning Poker cards can also be purchased online at http://store.mountaingoatsoftware.com/products/planning-poker-cards

  27. 27.

    You could potentially use other units of estimates like Ideal Days instead.

  28. 28.

    We are using the words sprints and iterations interchangeably here.

  29. 29.

    Prioritization could be done by using MoSCoW technique as described in Chapter 3: Value-Driven Delivery. Prioritization could be done based on value, risk, or cost of doing it.

  30. 30.

    The term MVP was coined by Frank Robinson and popularized by Steve Blank and Eric Ries.

Author information

Authors and Affiliations

Authors

Rights and permissions

Reprints and permissions

Copyright information

© 2016 Sumanta Boral

About this chapter

Cite this chapter

Boral, S. (2016). Domain V: Adaptive Planning. In: Ace the PMI-ACP® exam. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-2526-4_6

Download citation

Publish with us

Policies and ethics