Services

Project management

Project management based on current PMI and PMBOK guidance combines reliable governance with agile methods such as Scrum. Scope, priorities, risks, and decisions remain transparent.

A kanban wall with three columns of cream cards.

What project management delivers

Project management connects objectives, scope, schedule, quality, and communication in a reliable working framework.

The work covers process design and the management of scope, risk, quality, communication, schedule, and budget. Depending on the engagement, we act as project lead, team lead, or proxy product owner.

PMI and PMBOK guidance provides a framework for governance and control. Scrum, Kanban, or Lean UX add short learning and delivery cycles where useful. The approach follows the project.

Our work is grounded in long project experience and informed by PMI and PMBOK. We do not claim PMI certification.

Project governance with PMI and PMBOK

The eighth PMBOK edition combines six core principles with seven performance domains and non-prescriptive process guidance. What matters is selecting what fits the project.

The PMBOK performance domains cover governance, scope, schedule, finance, stakeholders, resources, and risk. They describe the areas that need active management for successful outcomes.

The five focus areas — initiating, planning, executing, monitoring and controlling, and closing — organise project work across its lifecycle. Their activities overlap; governance accompanies delivery throughout.

The useful processes and artefacts depend on the project. A website relaunch needs different emphasis from an interface integration. Reporting and governance support concrete decisions.

Five PMI process groups: initiating, planning, executing, monitoring and controlling, closing.
Process groups overlap. Controlling runs alongside execution — not only at the end.
1. Initiation

Clarify the assignment, goals, and stakeholders. Without this step, the rationale for scope and priority is missing later.

Typical outputs

  • Project charter or comparable start decision
  • Stakeholder overview: who decides, who delivers, who is informed only
  • Initial boundary: what is in scope and what stays out deliberately
2. Planning

Scope, schedule, quality, risk, and communication are planned so the team can work effectively. Plans are reviewed regularly and updated when justified changes occur.

What matters

  • Work packages or epics with dependencies
  • Milestones and acceptance criteria
  • Risks with a responsible person and next action
  • Clear communication paths and appropriate reporting intervals
3. Execution

The team works toward agreed outcomes, coordinates dependencies, and prepares decisions. In digital projects, planning, backlog, and tickets are closely connected.

Outcome

Measurable progress against agreed objectives and traceable documentation of deviations.

4. Monitoring and control

Progress, quality, risk, and changes are assessed continuously. Change requests receive a documented impact analysis and a clear decision.

Control tools

  • Comparison with plan, milestone, or sprint goal
  • Change log with impacts and decision
  • Risk and quality reviews before acceptance
5. Closing

Acceptance, handoff, and lessons learned close the project in an orderly way. Operations and delivery receive all decisions, open points, and remaining work.

Agile delivery with Scrum

Scrum creates a usable, reviewable increment in short cycles. Scrum events provide transparency, inspection, and adaptation.

The product backlog, sprint planning, daily scrum, sprint review, and retrospective provide a clear framework. The measure is the increment: what is usable at sprint end and meets the definition of done?

Kanban and Lean UX can complement this framework where continuous flow or experimentation matters. Approvals, security requirements, and release windows are included in planning early.

The product owner is accountable for the product goal and backlog ordering. The whole Scrum team shares responsibility for creating a valuable increment.

Scrum cycle with product backlog, sprint planning, daily scrum, review, retrospective, and increment.
Short sprints, a visible increment, regular adaptation.
Accountabilities: product owner, scrum master, and developers
  • Product owner — accountable for the product goal and ordering the product backlog
  • Scrum master — supports effective Scrum practice and helps remove impediments
  • Developers — plan and create a usable increment in each sprint

A proxy product owner can support day-to-day alignment. Domain accountability and decision paths must remain explicit.

Scrum events
  • Sprint — fixed period in which a usable outcome is created
  • Sprint planning — clarify the sprint goal, selected work, and delivery plan
  • Daily scrum — inspect progress toward the sprint goal and adapt the work plan
  • Sprint review — discuss the outcome and next adaptations with stakeholders
  • Sprint retrospective — inspect quality and collaboration and plan improvements
Artefacts: backlog and increment
  • Product backlog — ordered list of work needed for the product
  • Sprint backlog — sprint goal, selected items, and the plan to deliver them
  • Increment — usable outcome that meets the definition of done

Backlogs and supporting documentation often live in JIRA and Confluence. Tool choice follows the client.

Kanban and Lean UX

Kanban supports continuous flow and limits parallel work through WIP limits.

Lean UX shortens the path from hypothesis to tested outcome and connects product delivery closely with UX and analysis.

Both approaches can complement Scrum selectively. Their use follows flow and learning needs.

Method by engagement

PMI and PMBOK guidance, Scrum, or a hybrid approach: the method follows uncertainty, risk, governance, and delivery model.

Three columns: PMI/PMBOK, Scrum, and hybrid — when each method fits.
The method follows the engagement: fixed milestones, uncertain detail, or both.

Scope management

Keep in and out visible. Run scope changes as decisions, not silent growth.

Backlog and prioritisation

Slice and order work so delivery teams know what counts next — and what waits.

Process work

Clarify collaboration and handoffs in the team: roles, rituals, documentation places. Process follows the delivery goal.

Agile steering

Scrum, Kanban, or Lean UX where they improve pace and transparency. Fitting existing organisation rules is part of the work.

Risk and quality

Name risks early; set quality criteria and acceptance paths. Open points stay trackable.

Proxy PO and team leadership

Represent domain priority when the product-owner role is missing or needs relief. Lead teams without blurring accountability.

When PMI / PMBOK?
  • fixed milestones, budget frame, or external acceptance
  • many stakeholders and clear governance expectation
  • risk and change must be formally traceable
When Scrum?
  • solution detail is still uncertain and needs iteration
  • regular business feedback is possible
  • the team can deliver an increment in short cycles
When hybrid?

Common in digital relaunches: phase and milestone frame (PMI) plus sprints for conception and delivery (Scrum). Steering and pace run in parallel — scope changes remain decisions.

Artefact landscape

Good governance artefacts make goals, decisions, risks, and progress traceable, regardless of method.

Scope and decisions
  • Scope in/out — visible and approved
  • Decision logs — short, with date and owner
  • Change log — impact, decision, effect on plan or backlog
Planning and risk
  • Milestone or release plan — depending on method
  • Risk list — with owner and next step
  • Quality and acceptance criteria — testable, not just “done”
Backlog and documentation
  • Product backlog / work packages — prioritised and sliced
  • Tickets with references — to concepts, risks, decisions
  • Status for stakeholders — as steering, not as substitute for the ticket system

Typically JIRA and Confluence; plus classic PM tools when the client uses them.

Roles in practice

The label follows the assignment. What matters is who owns scope, priority, and delivery.

Project lead

Overall steering: scope, time, risk, communication, and acceptance paths. Fits PMI frame and hybrid models.

Proxy PO

Support day-to-day prioritisation when the product owner needs additional capacity. Domain accountability and decision paths remain explicit.

Team lead

Lead conception or delivery teams and coordinate capacity, quality, and handoffs. Responsibilities are defined clearly in the engagement.

Processes in practice

Two typical flows: kick-off to handover in the PMI frame — and the sprint cycle in Scrum. Hybrid combines both.

Kick-off to handover (PMI frame)

flowchart TD
  K[Kick-off and assignment] --> S[Stakeholders and scope]
  S --> P[Plan: milestones and risk]
  P --> E[Execution and delivery]
  E --> C[Control and change]
  C -->|Rework| E
  C -->|Approval| A[Acceptance]
  A --> U[Handover and closing]
            

Scrum sprint

flowchart LR
  B[Product backlog] --> PL[Sprint planning]
  PL --> W[Delivery]
  W --> D[Daily scrum]
  D --> W
  W --> I[Increment]
  I --> R[Sprint review]
  R --> B
  R --> RE[Sprint retrospective]
  RE --> PL
            

Managing change requests transparently

flowchart LR
  C[Change request] --> I[Clarify impact]
  I --> D{In scope?}
  D -->|yes| N[Update plan or backlog]
  N --> B[Priority and capacity]
  D -->|no| E[Document decision]
  E --> O[Out of scope or new commission]
  B --> H[Inform team]
  O --> H
            

Required skills

That requires steering competence and reliable communication between business and delivery.

Domain and method

PMI/PMBOK practice and agile steering — plus enough domain understanding to review priority and handovers substantively.

  • Scope, risk, and stakeholder management
  • Scrum (roles, events, artefacts); Kanban and Lean UX when needed
  • Prioritisation, proxy PO, and team lead
  • Acceptance paths and change steering
  • Reporting as steering aid, not an end in itself

Tools

The toolchain follows the client — typically:

  • JIRA and Confluence for backlog, tickets, and documentation
  • Classic PM tools (e.g. MS Project, Merlin) when the frame requires them
  • Collaboration for status, reviews, and decisions

Outcomes and handoff

Good governance creates a workable and traceable basis for the whole team.

A maintained backlog, clarified scope, decision logs, risk list, acceptance paths, and a handoff that lets delivery start without re-translation.

Tickets, linked documentation, and clear responsibilities support handoff to IT and operations, regardless of the chosen approach.

Handoff checklist
  • Scope and boundaries are visible and approved
  • Open changes are decided or assigned
  • Risks and acceptance criteria are documented transparently
  • Backlog and remaining work are prioritised
  • Business and delivery know the same decisions and tasks in the ticket system
What continues after handoff

Go-live is often followed by stabilisation, remaining work, and change requests. Responsibilities, capacity, and decisions remain clearly documented.

Discuss a project

Briefly describe the project and where support is needed.