Creating a product flow diagram
Definition: product flow diagram
The product flow diagram diagram shows the production sequence and interdependencies of the products listed in a product breakdown structure.
Developing the product breakdown structure is crucial as it helps identify product dependencies. When illustrated in the product flow diagram, these dependencies ensure smooth project execution and minimize risks.
In some cases, intermediate products will need to be delivered. Intermediate products are created as an essential input to the delivery of another product but are not intended for use by the user.
For example, producing a prototype can effectively reduce the risk of full-scale production, but the prototype is only the input to the full-scale production stage.

The product flow diagram and breakdown structure must include intermediate and final products and any dependencies on external products outside the plan’s scope.
The product flow diagram is not just a visual representation of the activities required to deliver the products. It’s a powerful tool that aids in estimating, scheduling, and understanding the project’s timeline and dependencies.
It provides a clear picture of the project’s progress and potential risks, helping project managers make informed decisions and ensure successful project delivery.
A well-structured work breakdown structure is not just a list of tasks. It’s a tool that provides a clear understanding of the project’s scope and boundaries.
Clearly defining the project’s deliverables makes it easier to manage and control the project, ensuring that it stays on track and delivers the expected outcomes.
Creating the product flow diagram is not a solitary task. It’s a collaborative process that involves consultation with subject matter experts. This inclusive approach ensures that all perspectives are considered, making the team feel involved and valued in delivering and accepting the required products.
The project manager and senior user are crucial in using the product breakdown structure and product flow diagram. This tool allows them to identify when project outputs (the products) will begin to affect outcomes and enable the user to start measuring the realization of benefits. This empowerment makes them feel important and integral to the project’s success.
It may also be helpful to distinguish products by which stage they are completed, for example, by colour.
Organizing work packages
The product flow diagram helps the project management team decide whether the project should be delivered linear-sequential or iterative-incremental.
When the delivery method is decided, the delivery activities involved in each product can be identified and organized into work packages.
Each work package should combine closely related people, resources, and delivery activities. It should also create at least one required end product or an intermediate product needed as input to a subsequent work package.
Suppose a work package depends on the delivery of a product from another work package or an activity outside the project’s scope. In that case, this relationship is considered a dependency.
Product dependency
A dependency means that one product is dependent on another. There are at least two types of dependency relevant to a project: internal and external.
Internal dependency: an internal dependency is one between two project products. In these circumstances, the project team has control over the dependency.
External dependency: an external dependency is between a project product and a product or activity outside the project’s scope. In these circumstances, the project team does not have complete control over the dependency.
PRINCE2 work packages
The associated work package description must document all dependencies in the product flow diagram.
Regardless of whether a contract is involved in the delivery of a work package (for example, there may not be a contract for an internal supplier), a work package description is considered an agreement between the project manager and the team manager responsible for the work package.
Although work packages are often interrelated, the project manager should ensure no overlap in the scope of any two work packages, as this could incur unnecessary costs and create potential conflicts between teams.
The totality of the work packages should comprise the full delivery scope of the project.
There should be no gaps between the product flow diagram, the product breakdown structure, and the complete set of work packages.
Organizing project management activities into a single work package for each stage can be helpful, even if these activities are not part of the project budget.
This helps document all project management tasks and shows the relationship between stages, milestones, and activities purely about product delivery.
The work breakdown structure has several applications in the PRINCE2 planning technique. It supports project organization by mapping work packages to the teams or suppliers responsible for delivering the associated products.
This application is beneficial when a project has a mix of work packages, with one or more being delivered through internal staff and others by external suppliers.
Where people represent a significant element of the project’s costs, the work breakdown structure allows labour costs to be described in terms of types of skills, level of effort, and duration of effort.
The work breakdown structure is a vital tool in project management. It helps develop team plans, where necessary work to deliver the products can be detailed regarding tasks and the team members assigned. This comprehensive planning approach instils confidence in the team, reassuring them of their project management abilities.
The work breakdown structure is optional for simple projects with one or two products or work packages and small delivery teams.
Did you know you get a full 12-month membership access to our PEOPLECERT Accredited PRINCE2 7th Edition Foundation Exam Masterclass, AND our PEOPLECERT Accredited PRINCE2 7th Edition Practitioner Exam Masterclass – PLUS all our other (over 30) Project Management Accredited Masterclasses – PLUS 7 days/week one-to-one online support (Microsoft Teams) from Dave Litten (ex-examiner), for just €299 for a full 12 months?
PRINCE2® 7 Foundation and Practitioner


Learn PRINCE2® 7 Foundation and Practitioner Online
** Enhance your PRINCE2 career now **
PRINCE2® Masterclass gives you the skills necessary to manage projects effectively and achieve your objectives.
Get 7 days a week 12 months one to one coaching with ex PRINCE2 examiner Dave Litten.
PRINCE2® is a globally recognized project management framework. By completing both the Foundation and Practitioner courses through our self-paced e-learning, you will develop an understanding of the methodology and learn how to effectively adapt it to any project.
The PRINCE2® 7 Foundation and Practitioner Masterclass is PeopleCert Accredited and guarantees to take you from PRINCE2 Novice to PRINCE2 Practitioner with our famous video learning, study guides and practice exams.
What Does the Masterclass Cover?
The PRINCE2 Foundation examination assesses your knowledge and comprehension of the PRINCE2 project management methodology as detailed in the syllabus. The PRINCE2 Practitioner examination, on the other hand, gauges your ability to apply and tailor the PRINCE2 method. Candidates who pass the Practitioner exam should be able to start implementing the method on an actual project with some guidance. However, their effectiveness may differ based on their experience in project management, the complexity of the project, and the level of support they receive in their work environment.


