Project management: Agile, Scrum, Kanban.

If your projects always run late, blow the budget or deliver something different from what the customer expected, the problem is not the people: it is the method (or the lack of one). Project management is not bureaucracy: it is the system that ensures the right resources do the right things in the right order to deliver the promised outcome on the agreed timeline.

Waterfall vs Agile: two philosophies, two contexts

Waterfall methodology

Waterfall plans the entire project from start to finish before execution begins: requirements, design, development, testing, delivery, in linear sequence. It works well when requirements are clear and stable from the outset, the project is predictable (construction, manufacturing, deployment of standard systems) and change is costly or undesired.

Agile methodologies

Agile methodologies assume requirements will change during the project and organise work in short cycles (iterations or sprints) that deliver partial but functional results. They work well when requirements are not fully defined or may change, the customer wants to see frequent progress, the project is complex and needs continuous adaptation, and delivery speed matters more than exhaustive planning.

Scrum: the most popular Agile framework

Scrum organises work in sprints of 1 to 4 weeks (typically 2 weeks), with three fundamental roles: the Product Owner (sets priorities from the business perspective), the Scrum Master (facilitates the process and removes obstacles) and the Development Team (executes the work).

Scrum ceremonies include sprint planning (what we will do these 2 weeks), the 15-minute daily standup (what I did yesterday, what I will do today, what is blocking me), the sprint review (demo of what was delivered to the customer) and the retrospective (what worked, what to improve, what to try in the next sprint).

For SMEs, Scrum adapts by simplifying the roles (the owner can be Product Owner, a senior team member can be Scrum Master) and adjusting ceremonies to company scale. You do not need a certified Scrum Master nor textbook ceremonies: you need the spirit of iteration, transparency and continuous improvement.

Kanban: continuous flow without sprints

Kanban organises work as a continuous flow on a visual board with columns representing process stages (to do, in progress, in review, completed). Unlike Scrum, it has no sprints or defined roles: work flows continuously from left to right at the team's capacity.

The fundamental Kanban rule is the work-in-progress limit (WIP limit): each column has a maximum number of tasks that can sit there simultaneously. This prevents multitasking (productivity's number one enemy) and forces the team to finish tasks before starting new ones.

Kanban is ideal for teams managing continuous work (support, maintenance, operations), projects with irregular task flow and contexts where rigid sprints do not fit.

How to choose the right methodology

For projects with clear requirements and a defined deliverable, use waterfall. For complex projects with changing requirements, use Scrum. For continuous operations or support work, use Kanban. For projects combining fixed planning with flexible execution, use Scrumban (a hybrid that takes the best of both).

Tool comparison

Asana offers the best experience for non-technical teams with list, board and calendar views. It is intuitive and has a generous free plan. Monday.com is the most visual and customisable, with powerful native automations. Ideal for teams that need advanced dashboards and reports. Trello is the simplest option: pure Kanban boards, perfect for small teams with linear processes. ClickUp is the most complete (and the most complex): combines tasks, documents, whiteboards, chat and goals on a single platform. Notion, as we have seen, also works as a flexible project manager for SMEs that want to centralise everything in one system.

The perfect tool is the one your team will actually use. Do not pick the most powerful: pick the one that best fits the maturity and culture of your team.

Are your projects running late or over budget? Get in touch for a diagnosis of your project management and the implementation of the methodology and tools that fit your team.

---

By Ángel Ortega Castro · independent consultant in strategy, quality and digitalisation for SMEs.

Frequently asked questions

When should you apply project management to your business?

When the company needs to streamline processes, scale operations or meet client and market demands. Waterfall plans the entire project before execution begins in a linear sequence: requirements, design, development, testing, delivery.

What are the benefits of structured project management?

Better internal coordination, more informed decisions, fewer errors and greater capacity to compete in demanding markets. Scrum ceremonies include sprint planning, the 15-minute daily standup, the sprint review and the retrospective.

Where do I start?

Start with a gap analysis of the current situation against requirements that identifies gaps and priorities before investing in implementation. The fundamental Kanban rule is the WIP limit: each column has a maximum number of tasks that can sit there simultaneously.