PMI Agile Certified Practitioner (ACP) Practice Exam

Disable ads (and more) with a membership for a one time $2.99 payment

Prepare for the PMI Agile Certified Practitioner Exam with multiple choice questions and flashcards. Each question includes explanations to help you gear up for your test!

Each practice test/flash card set has 50 randomly selected questions from a bank of over 500. You'll get a new set of questions each time!

Practice this question and more.


What does the acronym INVEST stand for in the context of user stories?

  1. Independent, Negotiable, Valuable, Estimate-able, Small, and Testable

  2. Invaluable, Necessary, Verifiable, Early, Small, and Timed

  3. Independent, Needy, Valuable, Estimable, Short, and Trackable

  4. Integrative, Networked, Verifiable, Expeditious, Small, and Tactile

The correct answer is: Independent, Negotiable, Valuable, Estimate-able, Small, and Testable

The acronym INVEST in the context of user stories stands for Independent, Negotiable, Valuable, Estimate-able (or Estimable), Small, and Testable. Each component of INVEST plays a crucial role in ensuring that user stories are well-formed and actionable. - **Independent**: This means that a user story should be self-contained and not depend on other stories. This independence allows teams to prioritize and work on stories without being hindered by dependencies, promoting flexibility in the development process. - **Negotiable**: User stories should not be rigidly defined. They are meant to be discussed and negotiated between the development team and stakeholders. This allows for adjustments based on feedback and changing requirements, fostering collaboration. - **Valuable**: Each user story must deliver value to the customer or end-user. This focus on value ensures that the development efforts are aligned with user needs and business objectives, helping to prioritize work that has the greatest impact. - **Estimate-able**: User stories should be clear enough to allow the team to estimate the effort required to complete them. This helps in sprint planning and understanding the complexity involved in the work. - **Small**: User stories should be sized appropriately, ideally small enough to be completed within a single iteration