Project management is no longer just about planning tasks and following a Gantt chart. Since August 2, 2026, the full implementation of the EU AI Act imposes new constraints on companies that use artificial intelligence tools to manage their teams. This regulation changes the rules of the game for any organization that relies on AI assistants for task allocation, performance evaluation, or human resource management.
EU AI Act and project management: what the regulation changes concretely
AI systems used to allocate tasks, monitor performance, or influence HR decisions are now classified as high-risk uses in employment under the European regulation.
For a project manager, this means that the choice of a management tool is no longer just a matter of features. It is necessary to verify that the platform complies with the transparency obligations imposed by the European regulation. Software that automatically assigns tasks based on individual productivity scores falls within the scope of high-risk systems.
Field feedback varies on this point: some companies have anticipated compliance, while others are discovering these obligations with the implementation timeline. Resources published on pm-blog.com allow tracking these regulatory developments applied to project management.
On the other hand, simple planning tools (shared calendars, Kanban boards without algorithmic scoring) are not subject to these constraints. The boundary lies in decision-making automation: as soon as an algorithm proposes or imposes a decision affecting an employee, the regulatory framework applies.
Agile method or traditional management: a choice that depends on the type of project
The debate between agile methodology and waterfall approach remains one of the most frequent in project management. Each approach addresses different project constraints, and the choice primarily depends on the degree of stability of the scope.
The waterfall approach works when the scope is stable and deliverables are defined from the outset. A construction project or regulatory compliance initiative, for example, does not handle short iterations well. Changing the scope mid-course is more costly in a sequential framework than in an iterative framework.
The agile method, on the other hand, is most beneficial when objectives evolve. A software development or digital transformation project benefits from short sprints and frequent user feedback. Teamwork is organized around rituals (daily standup, retrospective) that promote direct communication.
What both approaches share
Regardless of the chosen method, three elements remain crucial:
- A clear definition of objectives from the launch, even if they can evolve in agile, they must be articulated
- An identified responsible person for each task batch, to avoid the dilution of responsibilities among team members
- Regular checkpoints to measure actual progress against the plan, not just the volume of completed tasks
The choice of method does not guarantee project success. It is the rigor of execution and the quality of communication within the team that make the difference.
Multi-project management tools: governance rather than just productivity
Recent industry analyses describe an accelerated demand for project portfolio management platforms. The driving force behind this demand is no longer solely the pursuit of productivity. It is governance that drives companies to centralize their projects.
A manager overseeing multiple projects simultaneously needs to arbitrate between limited resources. Traditional tools (spreadsheets, task lists) reach their limits as soon as the portfolio exceeds three or four active projects. Dedicated platforms allow visualization of resource conflicts, project dependencies, and delay risks.
The selection criteria that really matter
Before choosing a tool, it is essential to clarify what the company seeks to resolve. Here are the most discriminating criteria:
- The ability to manage dependencies between projects, not just within a single project
- Algorithmic transparency if the tool incorporates decision-making AI, a condition now imposed by the EU AI Act
- Real adoption by teams, as a sophisticated tool that no one uses solves nothing
- The total cost of ownership, including training for employees and integration with existing systems
Conversely, features like visual reporting or gamification, often highlighted by vendors, have a limited impact on the actual success of projects.
Team communication and the role of the manager: the human factor remains central
The accumulation of tools and methods does not replace the quality of communication within a project team. A project rarely fails due to a lack of method, often due to a lack of communication.
The role of the manager is not limited to distributing tasks. It involves maintaining a framework where each team member understands the objectives, knows their responsibilities, and has a channel to report difficulties. Organizations that multiply communication channels (instant messaging, email, meetings, management tools) sometimes create more confusion than they resolve.
A primary channel for decisions, a single document space for deliverables, and fixed-frequency synchronization points: this simple structure covers most needs. The complexity of the organization must remain proportional to the complexity of the project.
Modern management is not defined by the adoption of the latest trendy tool or by the mechanical application of an agile method. It is measured by a company’s ability to combine an appropriate methodological framework, tools compliant with new regulatory requirements, and team communication that works on a daily basis. Since August 2026, the EU AI Act has been one of the constraints to integrate from the selection of a management tool.