In the context of PRINCE2 7, the introduction of 'People' as a central integrated element highlights that projects are driven by human interaction, not just processes. Collaboration and Co-creation are essential behaviors within this element that determine the effectiveness of the project ecosystem…In the context of PRINCE2 7, the introduction of 'People' as a central integrated element highlights that projects are driven by human interaction, not just processes. Collaboration and Co-creation are essential behaviors within this element that determine the effectiveness of the project ecosystem.
Collaboration is the act of working together to achieve a common goal. Within a PRINCE2 project, this implies breaking down silos between the Project Board, the Project Manager, and the delivery teams. It requires establishing a culture where information flows freely, trust is established, and the project team operates as a unified entity rather than a group of individuals protecting their specific interests. Effective collaboration reduces friction during exception handling and facilitates smoother change control.
Co-creation elevates this interaction by focusing on the joint generation of value. It is particularly relevant to the interface between the project team (Supplier) and the stakeholders (User/Business). Instead of the project team delivering a solution 'to' the users based on static requirements, co-creation involves the users 'in' the development process. This ensures that the products delivered are fit for purpose and that the transition into operational use is seamless. It aligns directly with the PRINCE2 principle of 'Focus on products' but adds a human-centric layer, ensuring that the definition of quality includes the user's experience and specific context.
Ultimately, PRINCE2 7 emphasizes that while the method provides the structure (processes and themes), Collaboration and Co-creation provide the dynamic energy required to navigate complexity, ensure user adoption, and realize the projected business benefits.
Guide: Collaboration and Co-creation in PRINCE2 Practitioner v7
Introduction In PRINCE2 7, the inclusion of the People element recognizes that projects are driven by humans, not just processes. Collaboration and Co-creation are pivotal concepts within this element. They represent a shift from a 'command and control' style to a supportive, facilitative leadership style where value is created jointly by the project team and stakeholders.
What is it? Collaboration is the act of working together to achieve a common goal. Co-creation is a specific form of collaboration where the provider (e.g., the project team/supplier) and the consumer (e.g., the user/business) actively join forces to design, develop, and implement the project outputs. Instead of the project manager simply gathering requirements and disappearing until delivery, the stakeholders are involved throughout the lifecycle to ensure the final output fits the purpose.
Why is it Important? 1. Shared Ownership: When stakeholders help create the solution, they are more likely to champion its adoption. 2. Reduced Risk: Constant interaction reduces the risk of 'expectations gaps' where the delivered product does not match the user's mental image. 3. Enhanced Value: Co-creation leverages the diverse knowledge of the entire ecosystem, leading to innovative solutions that a single project manager might not foresee.
How it Works In a PRINCE2 context, co-creation is achieved through: - Workshops: Replacing long email chains with facilitated sessions to define Quality Criteria or Product Descriptions. - Visual Working: Using visible boards (Kanban, Gantt) where all team members can interact with the plan. - Feedback Loops: Utilizing the 'Check' step in the PDCA cycle to get user feedback on prototypes or drafts immediately. - Cross-functional Teams: Breaking down silos so that suppliers and users work in the same space (virtual or physical).
Exam Tips: Answering Questions on Collaboration and Co-creation The Practitioner exam tests your ability to apply these concepts to a scenario. Use these tips to select the right answer:
1. Identify the 'Silo' Trap If an option suggests that the Project Manager should write a document in isolation and simply email it for approval, it is likely incorrect in the context of co-creation. Look for options that involve joint working or meetings to agree on definitions.
2. Facilitation vs. Dictation Correct answers often portray the Project Manager as a facilitator. If a conflict arises regarding a product's features, the PM should not decide who is right; they should organize a session where the Senior User and Senior Supplier can co-create a solution.
3. Look for 'Common Understanding' Questions often focus on miscommunication. The solution for collaboration issues is almost always to bring parties together to establish a common language or shared understanding, rather than relying on contractual enforcement.
4. Cultural Alignment Pay attention to the scenario's description of the organization's culture. If the culture is risk-averse or hierarchical, the PM needs to introduce collaboration techniques (like safe-to-fail environments) carefully. Answers that suggest forcing a collaborative method without preparing the people are usually wrong.
5. Keywords to Watch For Favor answers containing words like: consensus, workshop, facilitate, engage, jointly, and shared. Avoid answers containing: impose, instruct, isolation, or enforce (unless it relates strictly to compliance).