| Principle | Core Meaning | Key Action for Project Managers | |-----------|--------------|--------------------------------| | | Act responsibly with project resources (financial, human, environmental). | Balance the needs of stakeholders, organization, and society. Avoid shortcuts. | | 2. Create a collaborative project team environment | Build a team culture of shared ownership, trust, and psychological safety. | Facilitate collaboration, not command-and-control. Use servant leadership. | | 3. Effectively engage with stakeholders | Proactively understand and manage stakeholder expectations and influence. | Map stakeholders early. Communicate adaptively. Seek feedback continuously. | | 4. Focus on value | Deliver outcomes that matter—not just outputs or tasks. | Prioritize features by value. Use MVPs. Stop low-value work. | | 5. Recognize, evaluate, and respond to system interactions | See the project as a system within larger systems (organization, market). | Monitor emergent behaviors, feedback loops, and external changes. Adapt. | | 6. Demonstrate leadership behaviors | Lead with authenticity, empathy, and adaptability—not just authority. | Influence without formal power. Coach the team. Model desired behaviors. | | 7. Tailor based on context | No single method fits all. Adapt processes, governance, and tools to the project. | Adjust for size, complexity, risk, team location, industry, and culture. | | 8. Build quality into processes and deliverables | Quality is not an afterthought or inspection-only. It’s designed in. | Use test-driven development, peer reviews, and process standards. Prevent defects. | | 9. Navigate complexity | Accept that projects have uncertain, nonlinear, and emergent elements. | Use iterative cycles, diverse perspectives, and adaptive planning. Avoid rigid plans. | | 10. Optimize risk responses | Risk management is proactive, opportunity-seeking, and continuous. | Run risk workshops. Use risk-adjusted backlogs. Embrace appropriate risk-taking. | | 11. Embrace adaptability and resiliency | Be ready to change course and recover from setbacks. | Build buffer for uncertainty. Use retrospectives. Learn from failures quickly. | | 12. Enable change to achieve the envisioned future state | The project exists to drive change—manage resistance and transition. | Communicate the “why.” Train users. Manage change fatigue. Celebrate adoption. |
Deliver targeted, transparent, and timely information. pmbok 7 principles
: These principles apply to Agile , Waterfall , and Hybrid projects. | Principle | Core Meaning | Key Action
This principle moves beyond simple cooperation; it seeks synergy where the whole is greater than the sum of its parts. It requires project leaders to create an environment of trust and psychological safety, where team members feel empowered to voice dissent, share innovative ideas, and admit mistakes without fear of retribution. It involves establishing a shared vision where every member understands their role in the grand scheme. In a modern context, this also means bridging geographical and cultural gaps, fostering inclusivity, and ensuring that cross-functional silos are broken down to facilitate seamless flow of information. Use servant leadership
Act honestly and uphold ethical standards in all project interactions.
The traditional view of risk is negative—something to be avoided or mitigated. PMBOK 7 expands this view to embrace risk as a duality: it encompasses both threats (negative risks) and opportunities (positive risks).
Track risks throughout the lifecycle and update risk registers regularly.