PRINCE2 Agile 2016
Previous Section   Next Section

C.1 Is the following happening?

C.1.1 Behaviours

Statement Rating

Collaboration, trust and a no-blame culture exist.

Self-organization is predominant and is supported by the project management team.

There is a culture of inspect and adapt and continual improvement.

Transparency prevails.

Teams are regularly talking about the delivery of value and benefits.

There is an attitude of keeping things simple.

All stakeholders impacted by the project are being kept up to date.

The project board is frequently interacting with the people involved on the project.

Planning and work assignment are being carried out collaboratively.

The Pastor of Fun is well-organized.

C.1.2 Environment

Statement Rating

People are happy and work is enjoyable.

The team is stable, ring-fenced and working well together.

The project is responsive to change and is change-friendly.

The customer is involved and engaged at all levels.

A blended view prevails that takes into account the diverse views of the customer on a project.

The desired outcome and output are clear to everyone.

There is a thirst for feedback and a collective desire to find out what the customer really wants.

Agile learnings are being moved around the organization (e.g. by project support).

Communication is very good and fast-moving.

Control has a light touch and people are empowered.

Musts really are musts.

The project management team and the delivery teams are ‘understanding agile’ and not just ‘doing agile’.

The overriding mindset of the people on the project is an agile one.

Frequent releases are happening that are ideally put into operational use (or a staging area if the live environment is not ready).

The five targets of what to fix and what to flex are understood by all.

Significant events become routine because they happen frequently (e.g. stage boundaries or release reviews).

All roles are clearly defined and understood (taking into account that the mapping of the agile roles to PRINCE2 is not necessarily straightforward).

PRINCE2 is seen as agile.

C.1.3 Process

Statement Rating

Management by exception is working fully.

The level of control is appropriate to the level of uncertainty.

The work package interface is working well. It is smooth, is clear and does not lead to communication problems.

Requirements and user stories are explored and not just followed blindly.

The way of working is typically iterative and incremental, and benefits are being delivered at several points throughout the project.

There are clear definitions of ‘done’ and ‘ready’, and working agreements are transparent.

Planning and work are feature-focused and timeboxed.

The MVP is clear to everyone, and it is understood that its role on the project is to help with learning.

Quality checking and testing includes independent quality checking and testing.

Quality checking is happening continually and sometimes even drives the building of the products.

Planning is happening well in relation to all planning horizons (i.e. short term, medium term and long term) and with respect to the appropriate level of uncertainty.

A lot of planning is being done empirically.

Early requirements are based at a level that avoids unnecessary detail.

Project assurance is adding value from an agile perspective.

C.1.4 Techniques

Statement Rating

Prioritization is happening continually, and timeboxes are not being extended or having people added to them.

Information is very visible (e.g. on the walls) and is kept up to date.

When prioritizing, teams are looking at both scope and quality criteria.

Acceptance criteria always exist and are well written.

Estimation is a team-based activity.

Documentation is Lean, and the right channels are being used for each type of message.

Demos take place frequently.

Some risks are being mitigated by the use of spikes, prototypes and experiments.

Burn charts are being widely used and progress is clear to see.

User stories are being used to stimulate conversation and communication.

When Kanban is used, a holistic approach is adopted – not just a Kanban board.

Workshops are a regular occurrence and are being used appropriately.

Stand-ups are happening daily and are taking place quickly (i.e. lasting 15 minutes or less, perhaps 10).

People understand terms such as ‘requirement’, ‘user story’, ‘feature’ and ‘epic’.

Product descriptions have been written at the appropriate level and with flexibility with regard to quality criteria.

Previous Section   Next Section