Classifying a company’s projects by major category may seem like a theoretical exercise. In practice, the chosen category determines the management method, team composition, and governance mode. Misidentifying the nature of a project means applying a Scrum framework to a regulatory project or managing an IT overhaul like a marketing project. This overview of project categories in companies details the distinctions that matter for choosing the right management approach.
AI Projects and Regulatory Classification: An Emerging Category to Integrate
Classic typologies (IT project, organizational project, product project) did not cover initiatives related to generative artificial intelligence. Since early 2025, the adoption of generative AI has accelerated in HR and marketing departments, according to the McKinsey report “The state of AI in 2025”.
Read also : Keys to Defining Effective Strategic Directions in Your Business
The gradual enforcement of the European AI Act now imposes a classification of AI projects by risk level: prohibited, high, limited, minimal. Every company launching a project incorporating AI must audit the initiative from the initiation phase to determine which risk category it falls into.
This regulatory constraint effectively creates a new category of projects, transversal to the professions. A marketing project using an automatic content generation tool is no longer just a “marketing project”: it also falls under AI governance and requires specific legal validation. To delve deeper into the different types of projects on Le Guide PME, the distinction between internal and external projects remains a useful first filter before adding this regulatory layer.
Further reading : The latest automotive trends to know to stay ahead in 2024
Comparative Table of Project Categories in Companies
Rather than listing the categories one by one, a structured comparison allows us to visualize what truly distinguishes each project family in terms of method, duration, and management.
| Category | Main Objective | Preferred Method | Typical Duration | Governance |
|---|---|---|---|---|
| IT / Infrastructure Project | Deploy or migrate a system | Waterfall, PMBOK | 6 to 24 months | IT steering committee, fixed milestones |
| Product / Innovation Project | Design and launch an offer | Scrum, agile methods | 3 to 12 months (sprints) | Product owner, prioritized backlog |
| Organizational Project | Transform an internal process | Agile-waterfall hybrid | 6 to 18 months | General management, change management |
| Sustainability / ESG Project | CSRD compliance, carbon footprint | Management by regulatory deliverables | 12 to 36 months | CSR committee, external reporting |
| AI Project | Automate or enhance a profession | Agile + AI Act audit | 3 to 18 months | Data officer, legal validation |
This table reveals a clear gap: the management method varies as much as the objective. An ESG project is not managed with the same tools as a product project, even if both involve cross-functional teams.
Hybrid Agile-Waterfall Projects: The Category Progressing in Industry
The PMI survey “Pulse of the Profession 2025” confirms a growing preference for hybrid agile-waterfall approaches in industrial sectors. The principle: apply agile flexibility in the design phase (iterations, rapid prototyping), then switch to fixed milestones and sequential management for production and deployment.
This approach addresses a concrete problem. Pure agile methods (Scrum, Kanban) work well when the deliverable is software or digital. As soon as a project involves a physical production chain, certifications, or security constraints, unlimited iterations become impractical.
When to Choose a Hybrid Approach
- The project combines an exploratory phase (feasibility study, prototyping) and a realization phase subject to strict standards, as in construction or aerospace.
- The business teams and technical teams do not use the same management vocabulary: the hybrid allows each group to work with its logic while sharing common milestones.
- Management requires budget visibility at a fixed date (waterfall governance) while accepting that the functional scope may evolve along the way (agile decision).
A common pitfall is to label a waterfall project as “hybrid” simply by adding daily meetings. A true hybrid project explicitly separates agile phases from sequential phases in the schedule, with formalized transition criteria.
ESG and Sustainability Projects: Budgets Surpassing IT in Europe
According to Deloitte, sustainability projects (ESG) have surpassed IT projects in terms of allocated budget in large European companies since late 2024. The direct cause: reporting obligations related to the CSRD directive, which require companies to structure and publish verifiable non-financial data.
This budget shift has consequences for project organization. ESG initiatives mobilize unusual profiles within a project management framework: environmental lawyers, external auditors, sustainable procurement managers. The ESG project manager coordinates external as well as internal stakeholders, which changes the necessary management tools.
Differences in Management Between IT Projects and ESG Projects
A classic IT project follows an internal decision cycle: the steering committee validates, the team delivers. An ESG project, on the other hand, depends on external standards updated by standardization bodies. The project timeline is not entirely controlled by the company.
This external dependence brings ESG projects closer to regulatory projects. The management method must integrate continuous regulatory monitoring and reprogramming margins, which clearly distinguishes them from product projects or innovation projects managed in short sprints.
Choosing the Right Project Category: Decision Criteria
Before selecting a method (agile, PMBOK, hybrid), the first decision concerns the category in which the project falls. Three criteria help make this decision:
- The nature of the deliverable: software, an internal process, a compliance report, or a physical product do not call for the same team organization.
- The degree of external constraint: a project subject to regulation (AI Act, CSRD) requires governance including legal validations, unlike an internal continuous improvement project.
- The predictability of the scope: if the need is stable and well-defined, a sequential cycle is sufficient. If the scope is likely to evolve, an agile component in project management becomes necessary.
Categorizing a project does not mean sticking an administrative label on it. It is the first management decision, one that conditions the team composition, tool choice, and governance mode. A misclassification results in reorganization along the way, with the delays and additional costs that this entails.