Agile Dictionary - M - manage by exception to MoSCoW - Prince2

byTam M. | reviewed 2023-08-19

A - Z Dictionary of terms for Prince2 Agile edition. This is the official Dictionary of terms for the Agile prince 2 method. PRINCE2® is a registered trade mark of AXELOS Limited. See glossaries for Managing Successful Programmes (MSP), Project Office Dictionary (P30), PRINCE2, ITIL and Risk Management. See also the Project Management Dictionary.

A - acceptance critera to Agilometer | B - backlog to business case | C - change authority to customer subject matter expert | D - definition of 'done' to Dynamic Systems Development Method | E - early adopter to experiment | F - G - feature to Glad! Sad! Mad! | H - I - higlight report to issue | K - Kaizen to Kano | L - lead time to Little's Law | M - manage by exception to MoSCoW | P - Plan-Do-Check-Act to push system | Q - quality assurance to quality tolerance | R - RACI to risk register | S - SAFe to supplier subject matter expert | T - team dynamics to transparency | U - V - user story to visioning | W - Waterfall method to workshop

manage by exception

A technique by which variances from plan that exceed a pre-set control limit are escalated for action – for example, where spends exceed budget by 10%.

minimum viable product (MVP)

In a PRINCE2 Agile context the term MVP broadly aligns with the Lean Start-up view that it is a 'version of the final product which allows the maximum amount of validated learning with the least effort'. This should not be confused with the viability of the project as a whole. Typically, an MVP would be delivered as early as possible during the project. It is important to note that an MVP is about learning and may not go into operational use; it may be in the form of a simple experiment or prototype.

MoSCoW

This technique used to categorize items such as requirements or tasks into one of the four following levels of how they relate to a deadline :

Must have
Should have
Could have
Won't have for now