Effective IT project management in SMEs: methods, models, value

Introduction

Projects are at the heart of every IT transformation – in small and medium-sized enterprises (SMEs), too. Yet IT projects often fail because of a lack of structure, unclear roles or missing change management. Using professional project management methods is therefore not a luxury but a strategic success factor. In this article, I present proven models that also work well in SMEs: SCRUM, Prince2, the Volkswagen IT-PEP, CMMI and the SAFe framework for scaled agile projects.

Why IT project management in SMEs?

• Mastering growth: New software, processes or customer interfaces need structure.
• Time and cost control: Clear planning allows projects to be implemented more efficiently.
• Creating transparency: Who does what, by when, with what goal?
• Supporting change: Employees need to be brought on board and involved.

"Good project management saves more money than it costs."

Method 1: SCRUM – agile, incremental, team-oriented

SCRUM is an agile project management method that emphasises iterative development, continuous improvement and self-organisation. It is particularly suitable for software and digital projects.

Core elements:

• Product Owner, SCRUM Master, Development Team
• Sprints of 2–4 weeks with fixed goals
• Daily stand-up meeting (Daily Scrum)
• Sprint Review and Retrospective

Benefits for SMEs:

• Results that become visible quickly
• Close customer contact through regular feedback
• High level of engagement in the team

Method 2: Prince2 – the structured classic

Prince2 (Projects IN Controlled Environments) is a process-oriented method with a strong focus on control, reporting and responsibilities.

Principles:

• Projects have a business justification
• Clear allocation of roles
• Focus on product results rather than tasks
• Regular progress checks

Benefits for SMEs:

• Particularly suitable for compliance-relevant or regulated projects
• Project structure easy to document
• Reusable templates and procedures

Method 3: Volkswagen IT-PEP – the corporate standard with substance

IT-PEP (Produktentstehungsprozess, i.e. product development process) is Volkswagen's internal process model for IT projects. It combines classic phase models with agile elements.

Typical phases:

• Initialisation (goal, business case)
• Analysis (requirements, architecture)
• Implementation (agile sprints or waterfall)
• Integration, testing and rollout

Benefits for SMEs:

• Ideal for automotive supplier projects
• Well-documented process modules
• Can be adapted in a modular way

Maturity model: CMMI for projects

CMMI (Capability Maturity Model Integration) is not a project model but a maturity model. It helps companies understand how well established their processes are – and how they can be improved.

Maturity levels (level 1 to 5):

• Initial (chaotic)
• Managed (reproducible)
• Defined (standardised)
• Quantitatively Managed (measured and controlled)
• Optimizing (continuously improved)

Benefits for SMEs:

• Assessing where your own project organisation stands
• Basis for audits, e.g. when customers require them
• Guidance for building structured processes

Scaling framework: SAFe (Scaled Agile Framework)

SAFe is a framework for scaling agile methods in larger organisations. It combines SCRUM, Lean and DevOps at team, programme and portfolio level.

Core elements:

• Agile Release Trains (ART)
• Program Increment Planning (PI Planning)
• Roles such as Release Train Engineer or System Architect
• Lean Portfolio Management

Benefits for SMEs:

• Particularly for growing companies with several SCRUM teams
• Transparent management at all levels
• Clear link between IT projects and strategy

Comparison: the methods at a glance

• SCRUM – small to medium project size, very high flexibility, low documentation effort, very well suited to SMEs.
• Prince2 – medium to large project size, medium flexibility, high documentation effort, well suited to SMEs.
• IT-PEP – medium to large project size, medium flexibility, high documentation effort, specifically suited to automotive suppliers.
• CMMI – not a project model as such, high flexibility, conceptual documentation effort, good for orientation in SMEs.
• SAFe – large project size, high flexibility, high documentation effort, only relevant for SMEs when scaling across several teams.

Conclusion

Professional IT project management is the key to successful digitalisation in SMEs. Whether agile, classic or hybrid – what matters is that the method fits the project, the organisation and its level of maturity. A structured approach creates transparency, saves costs and delivers better results.