In Agile projects, requirements are typically defined and managed through the product backlog. The backlog is a prioritized list of features, functions, enhancements, and fixes that are needed for the product. It serves as the single source of truth for all the work to be done and is continually refined throughout the project.
A. Metrics – These are measurements used to track progress and performance, not requirements.
B. Sprint – This is a time-boxed period in which a set amount of work is completed; it’s not a definition of requirements.
C. Charter – The project charter defines high-level information like objectives and scope, but not detailed requirements.
D. Backlog
In agile projects, the definition of requirements is typically represented by the "Backlog." The backlog, often referred to as the Product Backlog or Sprint Backlog, is a prioritized list of user stories, features, or items that describe what needs to be built or delivered in the project. It serves as a dynamic document that captures and represents the requirements of the project.
User stories within the backlog are written in a way that describes the desired functionality or feature from the user's perspective, making them a key element of requirements in agile project management. The backlog is continually refined, reprioritized, and adjusted throughout the project to ensure that it reflects the evolving understanding of the project's requirements.
This section is not available anymore. Please use the main Exam Page.CAPM Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
JesseChou_123
1 week, 3 days ago041ba31
1 year agoMoonManBlue
4 years, 3 months ago