Choosing the right project management system

The Kanban method is primarily used in contexts where workflow management and continuous improvement are essential. Here are the main use cases:

1. Types of Work Suited for Kanban

Kanban is ideal for activities that require a continuous and adaptable workflow, with tasks that can be processed individually and updated in real-time.

Examples:

• IT Support and Maintenance (ticket management, incident resolution)

• Software Development (continuous deployment, incremental improvement)

• Digital Marketing (campaign management, content creation)

• Customer Service (request tracking and response)

• Industrial Production and Logistics (inventory management, flow optimization)

2. Types of Projects Suited for Kanban

Kanban is particularly effective for projects that are:

• Continuous Workflow: Without clear beginning or end, like support teams or DevOps

• With Evolving Tasks: When priorities change frequently and need to be quickly readjusted

• Not Requiring Rigid Planning: Unlike Scrum, Kanban is more flexible and doesn't rely on fixed sprints

3. When to Avoid Kanban?

If a project requires extensive upfront planning with strict deadlines and defined milestones (e.g., software construction with precise deliveries), Scrum or traditional waterfall project management may be more appropriate.

Conclusion

In summary, Kanban is an excellent choice for teams with:

• Continuous workflow

• High flexibility

• Real-time task management

The Lean method is used to optimize processes by reducing waste and maximizing customer value. It is particularly suited to environments where continuous improvement and efficiency are essential.

1. Types of Work Suited for Lean

Lean is effective in sectors where resource optimization and reduction of unnecessary tasks are priorities.

Examples:

• Industry and Manufacturing (production optimization, reduction of unnecessary inventory)

• Software Development (Lean Software Development) (rapid delivery, minimization of unnecessary code)

• Startups (Lean Startup) (rapid idea validation, adjustments based on customer feedback)

• Healthcare and Hospitals (reduction of wait times, improvement of care)

• Services and Administration (internal process efficiency, automation)

2. Types of Projects Suited for Lean

Lean is particularly useful for projects:

• Requiring continuous improvement: For example, a manufacturing process where waste is progressively reduced

• With limited resources: Startups often apply Lean to quickly test their products without massive initial investment

• Where adaptability is key: Lean allows quick project adjustment based on user feedback or market changes

3. When to Avoid Lean?

• If the project is highly structured and rigid, with fixed requirements (e.g., bridge construction or satellite launch)

• If iterations and continuous adjustments are not possible, as in certain regulatory projects

Conclusion

Lean is ideal for environments where efficiency and continuous improvement are crucial. It is particularly suitable for industries, startups, and services seeking to:

• Minimize costs

• Maximize value

• Quickly adapt to customer needs

ALM (Application Lifecycle Management) refers to application lifecycle management, encompassing all phases of software development, from ideation to production and maintenance. It typically includes the following aspects:

1. Requirements Management

• Definition of needs and expected functionalities

2. Planning and Design

• Development of architectures and development plans

3. Development

• Code writing and functionality implementation

4. Testing and Quality Assurance

• Verification and validation to ensure compliance and reliability

5. Deployment and Production Release

• Software delivery to end users

6. Maintenance and Support

• Bug fixes, updates, and evolution

ALM often relies on integrated tools that allow development, testing, and operations teams to collaborate effectively throughout the software lifecycle. Solutions such as Azure DevOps, Jira, GitLab, or IBM Engineering Lifecycle Management are commonly used to ensure this management.

Exemples de software dédiés ALM :

📌 Project Context

The government wants to implement a website facilitating French nationality applications for immigrants. Currently, the process is cumbersome, manual, and leads to excessive delays. The new site should allow users to submit documents, track their application, and communicate with relevant authorities.

The French nationality application platform project can be handled in Waterfall mode, but it has several characteristics that could also justify an Agile or hybrid approach. Let's analyze the advantages and limitations of Waterfall for this project.

Arguments for Waterfall

1. Compliance and Regulation

• Subject to strict legal constraints (GDPR, FranceConnect, sensitive data management)

• Clear definition of requirements from the start is essential to avoid legal issues later

2. Sequential and Predictable Process

• Project steps follow a logical sequence: requirements analysis → design → development → validation → deployment

• Each phase must be validated before moving to the next, Waterfall secures each milestone

3. Clear Budget and Timeline

• Public administration and government agencies often need precise budget and schedule

• A rigid framework like Waterfall reassures stakeholders about deadlines and costs

4. Documentation and Traceability

• This type of project requires rigorous documentation, especially for data security and procedure validation

• Waterfall's strong emphasis on documentation is an advantage here

Limitations of Waterfall

1. Evolving Needs During Development

• If changes are needed after the specification phase, Waterfall doesn't handle them well

• In digital projects, users often have new needs after initial testing

2. Long Development Time Before First Tests

• With Waterfall, testing and validation come after development

• If a problem is detected late, correction can be costly and cause delays

3. User Experience Not Tested Early

• The project involves a platform with complex user interface (forms, application tracking, administrative interactions)

• Not testing quickly with users could result in poor experience and require heavy redesigns

Alternative: A Hybrid Approach

If the project must respect a strict framework but also adapt to user feedback, a hybrid approach could be more effective.

Waterfall Design Phase

• Requirements definition

• Legal validation

• System architecture

Agile Development Phase with Sprints

• Breakdown into priority features

• Progressive delivery of testable prototypes

• Continuous feedback integration

Conclusion: Waterfall or Not?

• If the project is fixed and emphasis is on regulation, security, and documentation → Waterfall is a viable option

• If user experience is key and adjustment based on feedback is necessary → A hybrid model (Waterfall + Agile) would be more effective

1. Project Context

A space agency (e.g., ESA, NASA, CNES) is launching a project to develop control and navigation software for a scientific satellite.

The system must:

• Control orientation and trajectory of the satellite

• Manage communications with ground stations

• Supervise onboard scientific instruments

Once the satellite is launched, software modifications will be impossible, except for minor updates via telecommunication. No errors can be tolerated.

2. Why Waterfall is the Best Approach?

1. Requirements are Fixed from the Start

• All satellite components must be precisely specified before development begins

• It is impossible to add features after launch

2. Strong Sequentiality is Required

• No room for frequent adjustments once the satellite is built and assembled

• Each module must be designed, tested, and validated before integration into the satellite

3. Dependence on Rigorous Testing and Certification

• Testing is first done on simulators before physical integration

• Software is then tested in simulated space conditions (zero gravity, extreme temperatures, cosmic radiation)

• The slightest error can compromise a multi-billion euro mission

4. Complete Documentation is Required

• Every line of code, protocol, and recovery procedure must be documented so engineers can intervene if problems arise

• The software must be able to function for years, even decades, without major updates

3. Waterfall Cycle Phases Applied to this Project

Analysis and Specifications

• Identification of satellite and mission requirements

• Definition of physical and environmental constraints

Design

• Detailed architecture of embedded software

• Development of communication and error correction protocols

Development

• Software implementation according to validated specifications

• Technical documentation and operation simulation

Testing and Validation

• Laboratory and simulator testing

• Verification in real environment on a test satellite

• Validation by space agency and other relevant authorities

Deployment and Maintenance

• Software installation and integration in the satellite

• Launch and performance monitoring via telemetry

• Remote correction plans in case of failure

Conclusion: A Perfect Project for Waterfall

• No possibility of modification after deployment

• Very high cost of error

• Need for rigorous and progressive validation

• Documentation essential for ensuring long-term stability

In this type of project, Agile is unsuitable, as rigor, traceability, and predictability are essential!

Project Context

The government wants to develop an official web platform allowing citizens and businesses to:

• Declare their income

• Pay their taxes online

• Track their payments and obtain tax certificates

• Interact with administration through secure messaging

Why Waterfall is Suitable?

1. Clear Requirements from the Start

• Tax and accounting rules are defined by law

• Must respect strict frameworks and not improvise features along the way

2. Strong Regulatory Constraints

• Tax management is governed by national and international laws

• Application must comply with security and data protection standards (GDPR, ISO 27001, etc.)

3. Fixed and Non-Negotiable Deadlines

• A tax platform must be ready for a specific date, before the tax declaration period opens

• There is no room for continuous iterations, as taxpayers must be able to use it immediately

4. Testing and Validation Before Launch

• Before launch, the application must be thoroughly tested to avoid any bugs that could distort declarations and lead to legal issues

• Cannot afford to go live with incomplete or beta features

5. Documentation and Training

• Tax administration and taxpayers must have clear guides on platform usage

• Support team must be trained before launch

Waterfall Cycle Phases for this Web Application

1. Analysis and Specifications

• Gathering requirements with Ministry of Finance

• Definition of tax rules and administrative workflows

2. Design

• Architecture definition (database, API with other tax systems)

• UX/UI design based on government accessibility standards

3. Development

• Module development: declaration, payment, tracking, messaging

• Implementation of tax rules in algorithms

4. Testing and Validation

• Regulatory compliance and security testing

• Verification with real scenarios (individual and business declarations)

5. Deployment and Maintenance

• Official launch before tax declaration period

• Annual update according to new tax laws

Conclusion: Is a Web App Possible in Waterfall? Yes, but with Conditions!

• A web application for tax management or other regulated administrative processes is a good candidate for Waterfall

• If requirements are fixed, post-launch changes are rare, and compliance is critical, Waterfall is relevant

• However, if the application needs to evolve quickly based on users, Agile or hybrid mode is better

This is why most government websites (taxes, social security, land registry, etc.) are often developed using Waterfall!

Is Spotify's project management a good example of using Scrum?

❌ No, Spotify doesn't strictly use Scrum, but rather an Agile-inspired model called the Spotify Model.

✅ However, Spotify did use Scrum initially before evolving towards a more flexible model adapted to its rapid growth.

The Spotify Model is an evolved version of Agile that moves away from strict Scrum rules while maintaining its fundamental principles. Spotify adapted Scrum to meet its needs for autonomy, innovation, and scalability at a large scale.

1. How Spotify Used Scrum Initially

At first, Spotify used Scrum in a traditional way:

• Autonomous Scrum teams, organized in 2-week Sprints

• Product Backlogs to manage feature priorities

• Daily Scrums, Sprint Reviews, and Retrospectives

However, as they grew, Spotify encountered limitations with Scrum:

• Too many dependencies between teams, which slowed down the process

• Difficulty synchronizing multiple Scrum teams working on different parts of the product

• Rigidity of Scrum roles, which didn't always align with Spotify's culture

2. Evolution to the Spotify Model

Instead of scaling Scrum, Spotify introduced a more flexible Agile model structured into Squads, Tribes, Chapters, and Guilds:

Key differences between Scrum and the Spotify model:

• No mandatory Scrum Master: Each Squad is autonomous and self-organized

• More process flexibility: Some teams use Sprints, others use continuous flow (Kanban)

• Emphasis on company culture and autonomy, rather than strict framework adherence

3. Is Scrum Suitable for Spotify Today?

• No, because Spotify has evolved towards a more adaptable and scalable model

• Yes, for small teams wanting to test new features

Scrum works well for startups or small teams, but a company like Spotify, with hundreds of interconnected teams, needs more flexibility.

Conclusion

• ❌ Spotify no longer follows Scrum strictly, but used it in its early days

• ✅ Scrum remains a good choice for smaller, autonomous teams

• ✅ For a large company like Spotify, a more flexible and less structured Agile model is preferable

Recommendations

• 💡 If you have a startup or project with a small team, Scrum is an excellent method

• 💡 If your organization is large and growing rapidly, you might want to draw inspiration from the Spotify model