PRINCE2 PRojects IN Controlled Environments, templates and advice

Each template comes with:

Microsoft Project plan tried and tested on real projects
100s of tasks covering the whole project lifecycle
Compatible with other Microsoft Project versions
Detailed user guide to configuring your plan
A 30 minute video guide to configuring your plan
Plans for software projects, events, and websites

Agile Dictionary of Terms for Prince2

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, Risk Management and 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

A - acceptance criteria to Agilometer

acceptance criteria

A prioritized list of criteria that the project product must meet before the customer will accept it, i.e. measurable definitions of the attributes required for the set of products to be acceptable to key stakeholders (PRINCE2 definition). The acceptance criteria are commonly used in agile for assessing whether a user story has been met.

agile behaviour(s)

Those behaviours that are seen as typifying working in an agile way e.g. being collaborative, self-organizing, customer- focused, empowered, trusting not blaming.

agile plans

Agile plans may show features (or sets of features) and their order and their dependencies, and are likely to have been created collaboratively by those who will carry out the planned work. Agile plans tend to be informal or low-tech at the delivery team level and this can be highly effective even though they may be no more than to-do lists or backlogs. Product- based planning can still be used at all levels of the project (including product delivery).

Agilometer

The Agilometer is a tool that assesses the level of risk associated with using agile in combination with PRINCE2. This allows PRINCE2 to be tailored in such a way that best mitigates the level of risk. The Agilometer should evolve to suit the needs of each organization.