Free AgilePM-Practitioner Exam Braindumps (page: 4)

Page 3 of 21
View Related Case Study

Answer the following questions about the acceptance criteria within the project.

Decide whether the approach to setting and using acceptance criteria has been applied appropriately and select the response that supports your decision.

During Solution Development Timebox A, a new Health and Safety requirement arises: the front door is required to have wheelchair access. This is a legal requirement and is a Must Have before any staff or general public access can be allowed. The Solution Development Team will work with the Local Planning Authority Officer, the specialist who identified the requirement, to identify further acceptance criteria for Solution Development Timebox A.

Is this an appropriate action related to acceptance criteria?

  1. Yes, because the new requirement needs to be understood, built and delivered in this Timebox.
  2. Yes, because the Local Planning Authority Officer owns the justification for the new requirement.
  3. No, because this new requirement would NOT be included in the original Prioritised Requirements List and therefore does NOT need acceptance criteria to be defined.
  4. No, because the Business Visionary is responsible for defining acceptance criteria.

Answer(s): A

Explanation:

A . Yes, because the new requirement needs to be understood, built and delivered in this Timebox.
Rationale:
Agile Project Management is adaptable to changes, even late in the development process. The introduction of a new Health and Safety requirement, such as wheelchair access, which is a legal and must-have requirement, needs to be incorporated into the project as soon as it is identified. Working with the Local Planning Authority Officer to define acceptance criteria ensures that the requirement is clearly understood and that the solution developed meets the necessary legal standards. This approach ensures that the team can immediately address the new requirement and integrate it into the current work cycle, aligning with Agile's principle of welcoming changing requirements, even late in development, for the customer's competitive advantage.



View Related Case Study

Answer the following questions about the acceptance criteria within the project.

Decide whether the approach to setting and using acceptance criteria has been applied appropriately and select the response that supports your decision.

The requirement to 'install a heat reclamation system' shows as a Should Have in the Prioritised Requirements List. During Investigation in Solution Development Timebox B, the Project Manager advised the team NOT to set detailed acceptance criteria for this requirement until later in the Timebox, since the requirement may have to be dropped and the work would be wasted.

Is this an appropriate action related to acceptance criteria?

  1. Yes, because only Must Have requirements should be fully understood.
  2. Yes, because the acceptance criteria might need to be changed during the Solution Development Timebox.
  3. No, because it is necessary to understand the full detail of all the work for completion in the Solution Development Timebox during Investigation.
  4. No, because it indicates that the Solution Development Team has NO intention of delivering the Should Have requirements.

Answer(s): B

Explanation:

B . Yes, because the acceptance criteria might need to be changed during the Solution Development Timebox.
Rationale:
In Agile Project Management, flexibility is key. It is important to prioritize work based on the value it provides and the necessity of the requirement. "Should Have" requirements are important but not critical, and they can be subject to change as the project progresses and as more information becomes available. Deferring the detailed setting of acceptance criteria for a "Should Have" requirement that might be dropped is a practical approach to managing workload and focusing efforts on the most critical aspects of the project first. This approach is in line with Agile's principle of responding to change over following a fixed plan.



View Related Case Study

Answer the following questions about the acceptance criteria within the project.

Decide whether the approach to setting and using acceptance criteria has been applied appropriately and select the response that supports your decision.

The objective of Solution Development Timebox B is to ensure that the front and east wings are finished and approved. The Project Manager has pointed out that acceptance criteria for this part of the solution need to be agreed.

Is this an appropriate action related to acceptance criteria?

  1. Yes, because this will allow the Solution Development Team to focus on the quality of the Solution Development Timebox's deliverable as a whole, in order to keep focus on the business need.
  2. Yes, because it will be easier to set acceptance criteria for the Solution Development Timebox as a whole, rather than setting specific acceptance criteria for each individual requirement.
  3. No, because the acceptance criteria for the Solution Development Timebox are just the amalgamation of the individual requirements' acceptance criteria, with nothing extra.
  4. No, because the Solution Development Timebox objective will change if any new requirements emerge or any lower priority requirements are de-scoped.

Answer(s): A

Explanation:

A . Yes, because this will allow the Solution Development Team to focus on the quality of the Solution Development Timebox's deliverable as a whole, in order to keep focus on the business need.
Rationale:
Setting acceptance criteria for the overall deliverables of a timebox is a key practice in Agile to ensure that the work meets the business objectives and quality expectations. It helps the Solution Development Team to understand what is required for the deliverables to be considered complete and acceptable. This aligns with the Agile principle of delivering quality and maintaining a constant pace of development. It also ensures that all team members are aligned on the goals and can focus on delivering value in line with business needs.



View Related Case Study

HOTSPOT (Drag and Drop is not supported)

Using the Project Scenario, answer the following question about the activities in the Agile project lifecycle.

Lines 1 to 5 in the table below consist of an assertion statement and a reason statement. For each line identify the appropriate option, from options A to E, that applies. Each option can be used once, more than once or not at all.



Assertion:-

1. The rooms and facilities must be deployed into live use at the end of each Timebox.

BECAUSE

Reason:

Evolutionary Development and Deployment must be combined in a Timebox where the integration of several teams is required.

2. The tasks associated with each Solution Development Timebox should be included in the Delivery Plan.

BECAUSE

Reason:

A typical Delivery Plan will provide a schedule of Timeboxes and any other high level activities for the imminent Project Increment.

3. The development approach should have been agreed during Foundations.

BECAUSE

Reason:

The Development Approach Definition must be created before Evolutionary Development can commence.

4. The resources from Timber Tigers and Earth Excavations should have been engaged before the start of Evolutionary Development.

BECAUSE

Reason:

Commitment to delivery is based on pre-agreed resource levels at the project level.

5. A final Deployment phase should be held after Timebox C has completed.

BECAUSE

Reason:

The Deployed Solution is assessed post-project to confirm whether the expected benefits have been achieved.



  1. See Explanation section for answer.

Answer(s): A

Explanation:

Agile Practitioner

For each line, here is the appropriate option from A to E that applies:
The rooms and facilities must be deployed into live use at the end of each Timebox.
D) False (Assertion) True (Reason)
Rationale: While Evolutionary Development and Deployment can be combined in a timebox, it is not necessary that the rooms and facilities must be deployed into live use at the end of each timebox. Deployment into live use typically occurs after several timeboxes when the product is ready for release.
The tasks associated with each Solution Development Timebox should be included in the Delivery Plan.

A) True (Assertion) True (Reason)
Rationale: The Delivery Plan should outline the schedule of timeboxes and include the high-level activities planned for the upcoming project increment, which encompasses the tasks for each Solution Development Timebox.
The development approach should have been agreed during Foundations.
A) True (Assertion) True (Reason)
Rationale: The development approach is indeed something that should be agreed upon during the Foundations phase, as the Development Approach Definition sets the stage for how Evolutionary Development will proceed.
The resources from Timber Tigers and Earth Excavations should have been engaged before the start of Evolutionary Development.
C) True (Assertion) False (Reason)
Rationale: It is true that resources should be engaged before Evolutionary Development starts to ensure commitment and resource availability. However, the commitment is typically based on the detailed planning and agreements made during Foundations, not solely on pre-agreed resource levels at the project level.
A final Deployment phase should be held after Timebox C has completed.
E) False (Assertion) False (Reason)
Rationale: Deployment phases are usually not a one-time, final phase but occur incrementally as part of the timeboxed development. Additionally, the assessment of whether the expected benefits have been achieved is part of the benefits realization process and not necessarily the sole reason to have a final Deployment phase post-Timebox C.






Post your Comments and Discuss APMG-International AgilePM-Practitioner exam with other Community members:

AgilePM-Practitioner Discussions & Posts