Agile Analysis is a phase in the lifecycle of an Agile project.
Correct Answer: A
Question 228
In Agile projects, the technique in which planning is done at three distinct horizons is known as:
Correct Answer: D
Explanation/Reference:
Question 229
An organization wants to increase value delivery in its agile projects. What should the agile teams do?
Correct Answer: C
The correct answer is C - Work with product owners and turn product backlog items into potentially shippable product increments. Agile is grounded in the principle of delivering value early and often. Agile teams deliver value by continuously converting high-priority product backlog items into working software or product increments. These increments are potentially shippable, meaning they meet the Definition of Done and could be released at any point if the business chooses. Collaboration with the product owner ensures that the most valuable features are prioritized and refined before development begins. From PMI Agile Practice Guide: "Agile teams focus on delivering small, valuable, and potentially shippable increments of working product on a regular basis. This allows for frequent feedback and ensures that teams are always working on the most valuable features." (PMI Agile Practice Guide, Section 3.4 - Value-Driven Delivery) From Mike Griffiths' PMI-ACP Exam Prep Book: "Working software is the primary measure of progress in agile projects. Agile teams collaborate with product owners to break down backlog items into increments that can be developed, tested, and delivered within a single iteration." (Mike Griffiths, Chapter 3 - Value-Driven Delivery) Option A contradicts agile principles, which emphasize cross-functional teams capable of analysis, development, and testing. Option B is a supporting activity but does not directly increase value delivery. Option D reflects traditional project management thinking and does not align with the iterative, adaptive nature of agile.
Question 230
Sometimes stories are too small. A good approach for tiny stories, common among Extreme Programming teams, is to combine them into larger stories that represent from about a half-day to several days of work. The combined story is given a name and is then scheduled and worked on just like any other story. Which of the following are NOT examples of small stories?
