Hello again. You could call mindsets as well principles. Let's see what they are in popular project management standards or methodologies.
- Apply PM2 best practices to manage projects.
- Remain mindful that project management methodologies are there to serve projects and not the other way around.
- Maintain an outcomes orientation in relation to all projects and project management activities.
- Commit to delivering project results with maximum value rather than just following plans.
- Foster a project culture of collaboration, clear communication and accountability.
- Assign project roles to the most appropriate people for the benefit of the project.
- Balance in the most productive way the often-conflicting project management “Ps” of product, purpose, process, plan, planet, people, pleasure/pain, participation, perception and politics.
- Invest in developing technical and behavioural competencies to become better project contributors.
- Involve project stakeholders in the organisational change needed to maximise project benefits.
- Share knowledge, actively manage Lessons Learned, and contribute to the improvement of project management within organisations.
- Draw inspiration from the PM2 Guidelines on Ethics and Professional Virtues
- Be a diligent, respectful, and caring steward
- Create a collaborative project team environment
- Effectively engage with stakeholders
- Focus on value
- Recognize, evaluate, and respond to system interactions
- Demonstrate leadership behaviors
- Tailor based on context
- Build quality into processes and deliverables
- Navigate complexity
- Optimize risk responses
- Embrace adaptability and resiliency
- Enable change to achieve the envisioned future state
- Ensure continued business justification
- Learn from experience
- Define roles, responsibilities, and relationships
- Manage by stages
- Manage by exception
- Focus on products
- Tailor to suit the project
- Value, outcomes or business justification, which is the reason why projects are undertaken.
- Tailoring, i.e. methodologies are there to serve projects.
- Focus on products or deliverables and their quality criteria.
- Managing based on processes or stages.
However, there are also some striking differencies.
- PM2 and PMBOK? Guide highlight collaboration and communication or acting as steward, whereas PRINCE2? does not mention it.
- PM2 and PRINCE2? emphasize roles and responsibilities, whereas PMBOK? Guide does not directly treat them.
- Equally PM2 and PRINCE2? mention knowledge sharing and learning from experience, whereas PMBOK? Guide does not state it separately. Competence development in PM2 can be included in this area.
- Engaging stakeholders is emphasized in PM2 and PMBOK? Guide, whereas PRINCE2? does not mention it.
- Risks and complexity or alternatively exception is mentioned in PMBOK? Guide and PRINCE2?, whereas PM2 does not state it.
- PMBOK? Guide includes system interactions as well as adaptability and resiliency, which is not explicitly the case with PM2 or PRINCE2?.
Clearly on the mindsets or principles level PM2 and PMBOK? Guide are more comprehensive than PRINCE2?. However all three standards develop and extend the ideas further in their other building blocks (performance domains in PMBOK? Guide, practices and processes in PRINCE2? and governance, lifecycle and processes in PM2).
Mindsets mentioned in any of these methodologies certainly contribute to project success even when an organization already has a project management model or handbook in place. Methodologies also help in fitting different project management areas nicely together. Project managers who need a simple model can rely on P3.express or micro.p3.express.
With these words I wish everyone clear mindsets and peace of mind for the future projects. Please share again your feedback: how could methodologies and their mindsets help your projects?
