PRINCE2 Agile Exam 2022 with complete solution

PRINCE2 Agile Exam 2022 with complete solution How is the "Continued Business Justification" PRINCIPLE interpreted in an Agile environment? 1) FORECASTING the justification is HARDER because an Agile product is not fully specified upfront BUT 2) TRACKING the justification is EASIER, because of the Frequent Releases Why is tracking the business justification of an Agile project EASIER than with a predictive project? In Agile, the product is not fully specified upfront so everyone has to shift focus to the business value at the end of each iteration. How is the "Learn from Experience" PRINCIPLE interpreted in an Agile environment? There's no real difference in learning from experience in Agile projects and predictive ones. The only point worth mentioning is that Agile teams are usually more serious about this principle, and take more advantages from it. How is the "Defined Roles and Responsibilities" PRINCIPLE interpreted in an Agile environment? Roles and responsibilities in Agile tend to use a completely flat organization. However, they still have defined roles and responsibilities. Projects using PRINCE2 Agile should be careful to ensure there are no conflicting responsibilities. How is the "Manage by Stages" PRINCIPLE interpreted in an Agile environment? Most Agile methods use iterations, during which development processes are repeated for a subset of features, and a new version of working output (increment) is created. PRINCE2 uses stages for MANAGEMENT purposes to make it easier to plan and control the project. PRINCE2 Agile uses the following combination by default- Stage -Release --Iteration --Iteration --Iteration --Iteration The Releases and the Iterations / Sprints are below the Stage level. This means that there are more levels of detail involved in the project, and this also helps with the Manage by Exception Principle. It's possible to simplify this system by merging the Releases and Stages together, or even merge the Iterations, Releases, and Stages. How is the "Manage by Exception" PRINCIPLE