Feature · Methodology

Six methodologies, one project

The methodology should fit the project, not the other way round. In Projektiassistent, Scrum, Kanban, Waterfall, PRINCE2, hybrid and simple project work as separate logic layers — you pick the framework the work is managed in without changing what the project substantively is.

01 / Pick a framework

Which methodology suits which project

There is no point choosing a methodology on principle. What matters is whether the work is known in advance or takes shape as you go, and how strict the documentation has to be.

🌊

Waterfall

Sequential phases with approval gates. Fits when the scope is known up front and documentation must be strict — investments, infrastructure, regulated environments.

🏃

Scrum

Sprint-based iterative work with strictly defined roles and artefacts. Fits software and product development where requirements sharpen as you go.

📋

Kanban

A flow-based system with WIP limits and continuous improvement. Fits support services, content production and processes with no clear end.

🏛️

PRINCE2

A process-based model with clear stages and decision points where the business case is continuously validated. Fits the public sector and large organisations.

02 / Terminological cleanliness

Methodologies are not mixed together

A Scrum project uses sprints and a backlog; a Waterfall project uses phases and approval gates. The terminology stays correct — not cosmetics, but a condition for the management structure to actually work.

  • Simple project and hybrid

    A small initiative only needs a simple project with minimal overhead. Complex multi-phase work suits a hybrid that combines frameworks.

  • Methodology does not change substance

    An IT development project stays an IT development project whether it is run with Scrum or Waterfall. Only the way the work is organised changes.

  • Project type gives context

    IT development, construction, manufacturing, culture, agriculture, consulting — each type has its own assumptions, terminology and critical decision points.

Project frameworkScrum
Sprint length set
Backlog drafted
Roles assigned
Definition of Done agreed
First sprint → starting
03 / The choice

You can switch methodology later

If the choice turns out not to fit, the project does not have to be rebuilt. Switching adjusts the delivery framework; the substance stays.

ScrumKanbanWaterfallPRINCE2HybridSimple projectMilestonesSprints
04 / FAQ

Frequently asked questions

Which methodology should I choose?

If the scope is known and deadlines are fixed, Waterfall or PRINCE2 fits. If requirements sharpen as you go, Scrum fits. If the work is a continuous flow with no clear end, Kanban fits. For a small initiative, a simple project is fastest.

Do I need to know the methodology to use it?

No. The system sets up the matching structure and uses the correct terminology itself. If you are unsure, start with a simple project and switch later.

What happens when I switch methodology?

The substance of the project — objectives, activities, budget, risks — stays. What changes is how the work is viewed and tracked: phases become sprints, for example.

Can one organisation run projects with different methodologies?

Yes. Each project carries its own methodology. In the portfolio view they sit side by side, because the health and deadline logic is shared.

Get started

Pick the methodology that fits your project

14 days free — all Pro features, no card required.

Start for free →