Project management – classic, agile or hybrid

Projects rarely fail due to a lack of ability. They fail because of unclear goals, decisions nobody makes, and participants working alongside rather than with one another. We take charge of such projects – with the method that fits the project, not the one currently in fashion.

Waterfall, Scrum, Kanban or hybridAlso as project rescueIncluding vendor management
Service modules

Four ways we take on projects

Whether we lead a project from the outset or step into one already underway: the first step is always to establish the actual status – not the reported one.

Classic project management

For projects with fixed scope, deadline and budget: work breakdown structure, milestones, resource and risk planning, status reports and change control. Suitable for construction projects, migrations, rollouts and anything with strict acceptance criteria.

Agile delivery (Scrum & Kanban)

For projects whose outcome only sharpens as they progress: backlog build-up, value-based prioritisation, fixed work rhythms, reviews with stakeholders and progress measured by deliverable results.

Project audit & project rescue

A project is running off the rails: we establish the actual status, name causes rather than symptoms, and put forward a path forward – continue, restructure, or terminate in a controlled manner. The result is a report with a decision template.

Vendor management

When several providers are involved, someone needs to own the interfaces and deadlines: tendering and comparison, contract and performance control, acceptances, defect tracking and joint planning across all parties involved.

Methodology

Hybrid means: the method follows the project, not the other way round

The “classic or agile” debate misses the point in practice. A server migration with a fixed cut-over date needs a plan with a fallback scenario, not a backlog. A new software feature whose usage only becomes clear over time needs short cycles rather than a sixty-page specification. Most real-world projects contain both.

That is why we work in a hybrid way: a fixed framework where deadlines and costs are committed, iterative where content is still maturing. What matters is not the method, but that at every point it is clear who delivers what by when and who decides in case of doubt.

Equally important: we report reliably. A status report in which everything is green until it suddenly turns red is not a report but a risk. With us, the actual status is what is stated – even when it is uncomfortable.

What you get in every project

  • A target picture everyone has agreed to – in writing, with a clear boundary of what is excluded.
  • A plan with responsibilities instead of a task list without names.
  • Regular status reports in a consistent format, including risks and decisions required.
  • A decision log, so that in three months it remains traceable why something was done that way.
  • A documented acceptance and a handover that operations can actually work with.
Process

From order to accepted outcome

Project management itself also follows a fixed process – so you know early on what you are getting into.

Clarification

Goal, scope, framework conditions, stakeholders and decision paths. For ongoing projects instead: a stocktake of the actual status.

Set-up

Plan, roles, deadlines, reporting and tools are defined and agreed with all stakeholders.

Steering

We run the project: tracking deadlines, clearing obstacles, assessing changes, escalating when necessary – and reporting at fixed intervals.

Completion

Acceptance, documentation, handover into operations and an honest retrospective: what worked, what should run differently next time.

External project management: when it pays off

Many mid-sized companies do not have trained project managers in-house. That is entirely normal – with two larger projects a year, a permanent position does not pay for itself. So someone takes on the leadership on the side: the most technically skilled employee, the department head, sometimes management itself. This works as long as nothing unforeseen happens. As soon as it does, there is no time to mediate conflicts, assess changes and follow up with stakeholders – and the project loses momentum without anyone being able to name the exact moment.

Where projects actually fail in practice

  • Unclear goal: all stakeholders agree, but mean different things. The conflict only becomes visible at acceptance.
  • Unclear decision paths: it is not defined who decides in a conflict of objectives, so nobody does.
  • Creeping scope expansion: each individual additional requirement seems small; together they blow the deadline and budget.
  • Rose-tinted reporting: problems are reported once they can no longer be concealed – by then the room for manoeuvre is gone.
  • Uncoordinated service providers: everyone delivers their part on time, but the parts do not fit together because nobody owns the interfaces.

Project rescue: the first two weeks decide

When we step into a project that has gone off track, we do not start with measures but with facts: what is actually finished, what has actually been commissioned, which payments have been made, what commitments have been given, and where contractual risks lie. Only after that does a decision template emerge, usually with three options – continue with an adjusted plan, restructure, or terminate in a controlled manner and limit losses. You make that decision; our task is to prepare it reliably and then implement it.

Interaction with the specialist departments

One advantage of the one-stop shop: when a project is IT-heavy, we draw directly on IT and digitalisation; for commercial topics, on back office and bookkeeping. Project management then does not first have to procure and translate specialist knowledge, but works with colleagues who use the same documentation and the same standards. For purely external projects, our role remains purely steering and methodological – that too is explicitly possible.

FAQ

Frequently asked questions about project management

How is project management billed?
A common approach is an agreed allocation per week or month, for example one or two days. For defined projects such as a project audit, we work with a fixed price. Both are agreed in writing in advance.
Can you take over an already running project?
Yes, this is a common case. We start with a stocktake over one to two weeks and then present a decision template before major direction is set.
Do you work on site?
Mostly remote, with on-site sessions for important points such as kick-off, critical decisions and acceptances. This keeps costs low without losing commitment.
Which tools do you use?
We work in your existing environment, if one exists – for example Jira, Azure DevOps, Asana or even structured spreadsheets. Where nothing exists, we set up a lean solution suited to the project size.
Do you also take responsibility for the outcome?
We take responsibility for leadership, planning, transparency and steering. Specialist delivery lies with the executing parties – whether internal or external. Where we deliver ourselves, for instance in IT projects, the respective service contract applies.
What happens if you conclude that the project should be terminated?
Then we say so – with justification and figures. A controlled termination is almost always cheaper than a project that ties up resources for another twelve months without ever delivering.

Is a project coming up – or has one come to a standstill?

In the free strategy call, we assess your project and tell you what form of leadership it actually needs.

Book a free strategy call
Book a strategy call