Process is the domain of actually delivering: scope, schedule, cost, quality, risk, change, artefacts, and closure. It is not a religion of templates. It is the operating system that keeps value from dissolving into busywork.
Delivery work, not paperwork theatre
The Process domain is a family of tasks: execute with enough urgency to deliver value, manage communications, assess risk, engage stakeholders, plan and manage budget, schedule, quality, and scope, integrate the plan, manage change, run procurement, keep artefacts honest, choose a method, set governance, manage issues, transfer knowledge, and close or transition the work.
That is not 'the Waterfall chapter.' Adaptive teams still plan, still manage change, still close. They just do those tasks in smaller loops. Predictive teams still need urgency and value, not a twelve-month wait to discover the customer wanted something else.
The failure mode is confusing artefacts with work. A beautiful schedule that nobody updates is interior decoration. A risk register with no owners is anxiety in columns. Process tasks earn their keep when they change a decision this week.
Integration, change, and value as the spine
Integration is the unglamorous centre. Someone has to notice that the schedule assumes a vendor date the procurement task has not secured, and that the quality plan assumes testers the resource plan does not have. That someone is you. Integration is not a phase. It is the habit of making the parts talk.
Change control is how Process stays honest. A change that is absorbed with a smile and no baseline update is how you invent a new project in secret. A change board that rejects everything is how the business goes around you. The task is to evaluate impact — scope, time, cost, risk, benefits — and get a decision from the person who actually owns the constraint.
Value and urgency belong in Process, not only in the business-case appendix. If a workstream no longer serves the outcome, stopping it is a Process decision. Shipping a thin slice that a customer can use beats polishing a component nobody will see until December. Rule of thumb: activity is not progress, and a green RAG on the wrong work is still a miss.
Issues, knowledge, and the close nobody wants
Promote risks to issues when they land. An issue without an owner and a date is a complaint. Knowledge transfer is a Process task because the project is temporary and the organisation is not. If the only person who understands the interface is leaving on Friday, you do not have a 'people problem to park.' You have a continuity failure in motion.
Closure and transition are where Process either professionalises or ghosts the operations team. Formal acceptance, residual issues, contracts closed, lessons that someone will actually read, and a handover with a named receiver. Skipping close to 'start the next one' is how the same defect returns wearing a new project code.
When a scenario smells like Process, look for the missing loop: no baseline, no change path, no artefact, no owner, no close. The best next action is usually to restore the loop, not to invent a heroic workaround that trains the organisation to skip you next time.
Summary & next steps
Process is the delivery task family: plan, integrate, control change, manage issues, keep artefacts true, and close. Method is a choice inside the domain, not a substitute for it.
Next: Business Environment — compliance, benefits, external change, and the organisation the project is trying to alter.