
A service catalogue tells colleagues what work your team can accept
Create a practical service catalogue that explains what your team accepts, what a request needs and where work outside the scope should go.

Create a practical service catalogue that explains what your team accepts, what a request needs and where work outside the scope should go.

Define a service-level objective with a meaningful indicator, target and time window so an operations team can judge performance consistently.

Find the dependency chain that sets a project’s finish date. A small worked example shows why the longest task is not automatically the critical path.

A RACI chart is useful when roles settle real questions about delivery and approval. Test the assignments against one task before expanding the matrix.

A stakeholder map should include the people who live with a project’s effects, not only its approvers. Use a simple service-change example to find omissions.