The correct answers are A and C .

AgilePM does not ignore uncertainty. It manages it openly and practically.

Why A is correct

“Use broad estimation ranges for high-uncertainty work and refine estimates as more information becomes available.”

This fits AgilePM very well because it acknowledges reality: some work is more uncertain than other work. Broad early estimates are often more honest and useful than false precision.

Why C is correct

“Identify key assumptions behind estimates and revisit them regularly as the project evolves.”

This is also strongly aligned. Estimates are shaped by assumptions, and AgilePM expects those assumptions to be made visible and rechecked as learning increases.

Why the other options are incorrect

B is too absolute. AgilePM still expects useful estimation even when uncertainty exists.

D is contrary to agile thinking because fixed early estimates create false certainty.

E is not appropriate because uncertain work should still be considered in planning, even if estimated at a higher level.

So the best answers are A, C .

To implement the new Must Have requirement for financial transaction functionality on the coffee shop insurance product website, the Technical Coordinator should focus on actions that align with their role in overseeing the technical aspects of the project. The following actions are most appropriate for the Technical Coordinator:

Selected Actions for the Technical Coordinator:

A. Ensure that the latest version of the website design in the Solution Architecture Definition is provided to all members of the Solution Development Team.

E. Check for any documented standards which need to be applied to the development of online financial transaction functionality.

A. It ' s crucial for the Technical Coordinator to ensure that the Solution Development Team has access to the most current website design specifications, especially when new functionalities are being added. This ensures consistency and alignment with the overall solution architecture, facilitating effective and efficient development.

E. The Technical Coordinator is responsible for ensuring that all technical aspects of the project adhere to relevant standards, including those related to online financial transactions. This involves identifying, understanding, and applying any necessary regulatory, security, and technical standards to the development process, ensuring compliance and functionality.

Why Other Actions Are Less Suitable:

B. Assessing the impact on the original Business Case is typically the responsibility of the Business Sponsor or Project Manager, as it involves financial and strategic considerations beyond the Technical Coordinator ' s primary focus.

C. Adding tasks to the Timebox Plan is generally a responsibility shared between the Project Manager and the Solution Development Team, with the Technical Coordinator providing input on technical feasibility and requirements.

D. Consolidating and circulating an agenda for the workshop is an important logistical task but may not directly fall under the Technical Coordinator ' s responsibilities. This task is often handled by the Project Manager or a designated administrative role.

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.

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.

The initial action to deal with the lack of provision of a fire escape from the upstairs of the building in Timebox B should be:

• C. The Architect, in the role of Technical Co-ordinator, should escalate the issue to Architecture Angels’ Senior Management Team.

This is because the lack of a fire escape is a significant safety concern that could have legal and regulatory implications. It’s important that the Senior Management Team is aware of this issue so they can make informed decisions about how to address it. The Architect, in the role of Technical Co-ordinator, is well-positioned to understand the technical implications of this issue and communicate them to the Senior Management Team.

While revising the Timebox Plans (option A) or commencing understanding and delivering the new requirement (option B) could be part of the solution, these actions should be taken after the issue has been escalated and discussed with the Senior Management Team. Escalating the issue to the Marketing Director (option D) may not be the most effective course of action, as this is primarily a technical and safety issue, not a marketing one.

In applying Agile Project Management to the creation of an Outline Business Case in support of the Feasibility Assessment, the following two statements are most appropriate:

B. Enough description of the required refurbishment work should be provided to enable the Architecture Angels ' Finance Director to decide whether the project should proceed.

Agile approaches favor providing just enough detail to make informed decisions without going into unnecessary depth at early stages. This allows for flexibility and adaptation as more information becomes available.

C. During Feasibility, potential beneficiaries of the project should be involved when the Outline Business Case for the refurbishment is created.

Agile methodologies emphasize stakeholder engagement and user involvement early and throughout the project. This ensures that the project delivers value and meets the needs of those it is intended to benefit.