APMG-International Updated AgilePM-Practitioner Exam Questions and Answers by bradley

A. Yes, because acceptance criteria can only be understood at a high level during Foundations and will always need further investigation.

Rationale:

In Agile Project Management, while the Foundations phase does involve setting high-level expectations and a prioritized requirements list, the detailed acceptance criteria are often refined during the actual Solution Development iterations or timeboxes. This is because, as the work progresses, the team ' s understanding of the product grows, and they are better equipped to define detailed acceptance criteria that align closely with the customer ' s needs and the project ' s evolving context. It ' s a collaborative and iterative process, allowing for greater precision in defining what will make a particular feature or requirement acceptable.

In the context of Agile Project Management when developing the Prioritised Requirements List during Feasibility, the two statements that align with Agile principles are:

B. The re-laying of the driveway and a landscaping solution should be listed as Must Have requirements.

E. Regulatory obligations associated with the redevelopment of Hoy Hall should be recorded as Must Have requirements.

Here ' s the rationale:

• B: In Agile, requirements are often categorized by priority such as " Must Have " , " Should Have " , " Could Have " , and " Won ' t Have for now " (the MoSCoW method). The re-laying of the driveway and a landscaping solution are essential for the project ' s success and thus should be classified as " Must Have " .

• E: Regulatory requirements are non-negotiable constraints that the project must adhere to. These should always be prioritized in the requirements list to ensure compliance and to avoid legal issues, making them " Must Have " items as well.

C. Independent Testing

A. Collaborative Testing

B. Repeatable Testing

D. Prioritised Testing

D. Prioritised Testing

Short Comprehensive Explanation :

Independent Testing is appropriate when someone from a different department (Finance) with no involvement in the development process conducts the testing to ensure an objective view.

Collaborative Testing involves various stakeholders, in this case, the Sales Manager and the solution tester, working together to review and test a prototype, promoting early feedback and shared understanding.

Repeatable Testing is used for security testing where predefined test scripts (provided by the bank) are applied to ensure the system meets specific security standards and can be repeated as needed.

Prioritised Testing is essential when the project ' s stability and core functionality, such as the website ' s capacity to handle new features, must be confirmed before other tests are conducted to ensure the most critical aspects are addressed first.

Again, Prioritised Testing is used to ensure that the essential requirements (Must Haves and Should Haves) are tested and validated before moving on to less critical ones (Could Haves), aligning with prioritization in Agile methodologies.