PROJECTS wiki Prince2

PRINCE2 3 principle - Focus to product

Universal Practical Simple Benefit focused Principles Implement Templates Ready apps for Jira

It is easy for you to understand what happens when project does not deliver expected product or product quality is low. Every project stakeholder usually has diffent understand how project result should look like and the same goes for quality. Poor project quality generates many unneccesary project meetings, extra costs, delays, conflicts and losses. So low focus to quality management has negative consequencies usually.

This principle demands - each project must have clearly documented 1) project user expectations and 2) quality acceptance criteria with prioritization. Where you store this vital information for PRINCE2 does not matter - email or Jira or xls or contract is OK. Nevertheless PRINCE2 does not allow to store it only in person mind - non written format is not accepted.

This PRINCE2 principle realization details are provided in quality and planning knowledge areas.

Every expected project product must be managed by applying this principle and benefit driven MoSCoW prioritization technique should be used. This principle implementation may vary depending on waterfall or agile/adaptive project management approach. Nevertheless strong focus to requirement and quality definition as well systematic management either using simple xls or Jira or contracts as example will payback you sooner or later for sure.

Other PRINCE2 principles:

Recommended solutions for Jira cloud:

discussion iconPROJECS wiki helps you to understand & implement best project management practices fast & easy & cost-efficient

discussion iconCreated by : Artūras Bučinskas, PRINCE2 Practitioner