2.2.3. Domains: Planning and Project Work

💡 First Principle: Effective project execution is driven by proactive, iterative planning to organize the work and the efficient management of the processes and resources required to accomplish it.

Scenario: In an adaptive project, the team engages in the 'Planning' domain by creating a high-level roadmap and a detailed plan for the upcoming iteration. They then move into the 'Project Work' domain, executing tasks, managing impediments, and continuously improving their processes, with planning activities re-occurring at the start of each new cycle.

This part covers organizing project activities and managing the execution of those activities.

4. Planning Performance Domain

• Focus: Proactively organizing and coordinating work.
• Desired Outcomes: Organized progression, adaptable plans, shared understanding.
• Key Activities/Concepts: Scope (WBS, Backlog), Schedule (CPM, Agile Release/Iteration Planning), Cost (Budgeting, Reserves), Quality, Resources, Comms, Risk, Procurement, Stakeholders. Estimation Techniques, Baselines, Rolling Wave Planning, Timeboxing. Requirements Management Plan, Assumption Log, Iteration Plan, Release Plan, Slack.
• Practical Relevance / PM Role: Facilitate planning, integrate plans, establish baselines, manage dependencies, ensure plan realism/adaptation. Planning is continuous in adaptive environments. Scenario insights often involve estimation, scheduling, budgeting, and comparing agile vs. predictive artifacts.

5. Project Work Performance Domain

• Focus: Efficiently managing the activities needed to create deliverables.
• Desired Outcomes: Effective process mgmt, resource utilization, communication, learning.
• Key Activities/Concepts: Process Management (Lean, Kanban, VSM), Resource Mgmt, Procurement Mgmt, Knowledge Mgmt, Change Control, Issue/Impediment Mgmt, Balancing Constraints, Configuration Management, Lessons Learned.
• Practical Relevance / PM Role: Facilitate execution, remove blockers, manage communication flow, monitor progress, ensure process adherence/improvement, oversee procurements. This is where plans turn into action. Scenario insights cover process improvement, change handling, procurement, and managing flow/blockers.

⚠️ Common Pitfall: Treating "planning" as a one-time phase at the beginning of the project. In all but the simplest projects, planning is an ongoing, iterative activity that adapts to new information and changes.

Key Trade-Offs:

• Detailed Planning vs. Speed of Execution: Spending too much time on overly detailed, long-range plans can delay the start of valuable work (analysis paralysis). The trade-off is to plan in sufficient detail for the near term while keeping long-term plans at a higher level (rolling wave planning).

Reflection Question: How does the concept of "rolling wave planning" demonstrate the continuous interaction between the Planning and Project Work domains?