Friday, November 27, 2015

PRINCE2 Agile - Stage vs Sprint.

Stage vs Sprint - PRINCE2 Agile
PRINCE2 Agile - Stage vs Sprint
Those who have worked with agile methods like Scrum, and then are exposed to PRINCE2, can easily jump to the conclusion that a PRINCE2 stage is a Scrum sprint. Both in PRINCE2 Agile theory and in real life the link between a stage and a sprint is usually slightly different. 

Wednesday, November 25, 2015

The PRINCE2 Agile Organization

Organization is one of the seven PRINCE2 Themes and includes definitions of roles and responsibilities at different levels of the project organization. One of the most challenging dimensions of combining PRINCE2 and Agile is to design the organizational interface between the two. PRINCE2 Agile gives us some clear advice on the governance structure and some interface options to choose from. Let us have a closer look at these recommendation and the options.

Monday, June 29, 2015

What is PRINCE2 Agile?

PRINCE2 Agile is an extension to PRINCE2, combining the flexibility and responsiveness of agile delivery with the established and proven best practice framework of project management.

PRINCE2 Agile will guide practitioners on how to apply agile methods to PRINCE2 in the most effective way to produce a perfect blend of best practices. It covers a range of agile frameworks, including Scrum, Kanban and the more recent approaches including Lean Start-up and Cynefin.

Thursday, April 16, 2015

3 Steps to Understand PRINCE2 in 1 Hour

PRINCE2 is a comprehensive project management method, and you can easily get lost in hundreds of pages of PRINCE2 theory.

Joining a course and signing up for certification is a good way to get some momentum, but you need to set aside 3-5 days to get this done.

 If your need is to get started fast or just need a good overview, you can set aside 1 hour to cover the following topics:

Tuesday, March 10, 2015

Does Design Input Replace PRINCE2 Product Descriptions?

There is one recurring question in most organizations introducing PRINCE2: “Does Design Inputs, like functional requirements or user requirements, for the end outputs of the project replace any Product Descriptions for these end outputs?”
The short answer is “no”. If you have detailed design input for a product to be made, there is no need to repeat these detailed requirements in the Product Description. This helps simplify the Product Description, but it doesn’t make it redundant because:

Thursday, February 26, 2015

A Fool with a PRINCE2 Tool is Still a Fool

PRINCE2, with its generic method approach and the specific tribal language, is the perfect gift for a fool who needs a new tool to misuse. Throwing templates, processes and language around can create frustration at a steaming level.

Here are a few PRINCE2 implementation mistakes you should avoid if you don’t want to end up as the fool with the PRINCE2 tool:

Wednesday, February 25, 2015

PRINCE2 Issue Report - Structure Gives You Credit.

Issue Report PRINCE2
There are times when a project manager ad-hoc needs to inform, seek advice and possibly get a decision from the project board. A demanding PRINCE2 Project Board will expect the project manager to provide structured analysis of the situation and recommended solutions, not just serve the board unstructured information and problems.

The way a PRINCE2 project manager is dealing with this topic is through Issue Reporting. Using a PRINCE2 Issue Report template helps the project manager to provide structured and analyzed information. Here are a couple of Issue Reporting advices:

The PRINCE2 Pitfalls of the Initiating a Project Process

Initiating a Project PRINCE2Initiating a project is mainly about building the project plan, setting up the rules (strategies) for the project and firming up the business case.

The Purpose of Initiating a Project process is to establish solid foundation for the project, enabling the organization to understand the work that needs to be done, but too often pillars of the foundation are weak. Rules have no value if they are irrelevant for the project or not agreed upon, and a plan loses its value if there is no ownership to it on the supplier side of the stakeholder table. 

Here are some common “Initiating a Project” pitfalls, and how to avoid them:

Monday, February 23, 2015

Keep a PRINCE2 Process Model within sight.

Process Model PRINCE2

As a PRINCE2 Project Manager or a PRINCE2 Project Board member, you need to understand and remember the process and document flow in the PRINCE2 method. Eventually, a project manager will intuitively understand the processes and documents in detail, but even then, it is useful to have a tool keeping the overview in sight. This is why you should keep a printed version of a process map on your wall or next to you while studying and practicing PRINCE2. Here is a couple of different models at different levels:

Friday, February 13, 2015

The PRINCE2 Project Manager’s Most Important Task.

Project Manager Priority PRINCE2If you casually ask people what a project manager’s most important task is, you will get many different answers. “Deliver on time, scope and budget” is a common suggestion. Other popular views are “understand critical path”, “prioritize”, “make things happen” and “plan the project”.

The tasks mentioned above are certainly important. Plans need to be realistic, understanding of critical path is essential and making things happen in prioritized order is a key to success. These things combined will absolutely help the project manager “deliver on time, scope and budget”. However, sometimes the “delivering-on-time”-obsession can cause sub-optimal return of investment. Maybe scope should have been changed, time added or more money spent to maximize an opportunity. If so, it is not the project manager’s decision to make. So what does that tell us about the project manager’s most important task?

Thursday, February 5, 2015

Scrum and PRINCE2 – Who gets the workpackage?

Scrum Workpackage PRINCE2If your project includes one or several Scrum teams, you could end up is quite a debate on who takes which PRINCE2 role. The Scrum team is by definition self managed. Scrum defines two roles in addition to the team, the scrum master and the backlog owner.
The Scrum Master’s responsibility is limited to facilitating the Scrum process. The Product Owner controls the backlog. In theory, a small project can be executed by the Scrum team alone. The scrum master could then take a role as project manager. But, what do you do if it is a larger project? Who would you then consider to take the Team Manager role and with whom do you negotiate workpackages?