Is the V-cycle right for your project management?

Are you familiar with the V cycle, the classic project management model ?

Developed in the industrial sector in the 1980s, this method of organising activities has gradually spread to other fields, notably IT. Today, many organisations still find the V-cycle functional for the management of certain projects.

However, over the years, other project management models have emerged. We've heard more and more about Agility, Scrum... is the V cycle out of kilter?

However, we will see that it remains a classic but interesting working method.

Would you like to know whether the V cycle can meet your project management needs? This article identifies its advantages and disadvantages, and introduces you to suitable software and alternative methods.

But first of all, let's look at the very definition of the V cycle.

See all software Project Management

Using the V-cycle

Definition of the V-cycle

The V-cycle is defined as a project management model consisting of a top-down phase and a bottom-up phase.

Inspired by the waterfall model, it involves the same principle of sequential, linear management, minus the back-and-forth (the W-cycle includes adjustments based on feedback).

Here's what the V-cycle model looks like:

In this diagram, we can clearly see all the stages involved in the complete creation of a product, from the formulation of the need to the final verification of its conformity with that need.

9 stages

The nine stages can be grouped into three phases, giving us a clearer picture of the project's progress:

Design (the top-down part):

• 1 - expression of requirements and feasibility study,
• 2 - definition of specifications and functional specifications,
• 3 - general/architectural design,
• 4 - detailed design.

Implementation:

• 5 - for example, the production of automotive components or computer coding;

Validation (the bottom-up part):

• 6 - unit testing, for each component or functionality,
  ✅ this stage echoes the detailed design stage and is opposite it on the V diagram;
  
  
• 7 - Integration and integration tests, on the finished product,
  ✅ This stage verifies that the system defined in the general design stage is working properly;
  
  
• 8 - Validation, i.e. the functional compliance of the product or software with the specifications provided by the customer,
  ✅ this stage validates compliance with the specs defined in the top-down phase;
  
  
• 9 - Acceptance or acceptance testing by the customer,
  ✅ This stage validates compliance with the expression of requirements.

You've now grasped the principle, but you're probably wondering what the advantages of the V cycle are.

The different roles

Here are the different stakeholders:

• the project owner, i.e. the decision-maker or customer,
• the project manager, i.e. the project team,
• the project management assistance (PMA), the third-party consultant, the service provider speaking on behalf of the customer,
• the steering committee, and representatives of the project owner and the project owner at meetings.

Advantages of the V cycle

Firstly, let's look at the reasons why the V-cycle has developed as opposed to the traditional waterfall model:

• It avoids the need to go back and forth during the project life cycle: if problems are encountered, each stage of the bottom-up part can draw on the documentation produced during the corresponding stage of the top-down part (see illustration above).
  
  
• It provides more details during its test phase.

On the other hand, the V cycle seems fairly intuitive and simple to put into practice:

• All it requires is a few regular meetings to manage the project and monitor the budget. As for the documentation, it can be created from existing templates.
  
  
• It requires less training and fewer prerequisites than other methods such as Scrum.
  
  
• It is easily adapted to projects involving multi-site structures, unlike project management models that require daily meetings.

So is the V-cycle the miracle recipe for managing your projects with a master's hand?

But here's the thing...

Disadvantages of the V cycle

In recent years, the V cycle has come under increasing scrutiny.

Here are the main criticisms:

• It does not tolerate change well.
  Because of its sequential and linear construction, it is impossible to go backwards. However, it is not uncommon to encounter conceptual problems during the implementation and validation phase. Should the V-cycle then be restarted from the beginning? Or wait until the next V cycle to make the changes?
  
  

• It requires a great deal of documentation, which some people see as a waste of time.
  What's more, if it turns out to be imperfect, we can't rectify it in the intermediate stages provided for that purpose.
  
  

• It is difficult to adapt to certain types of project.
  Software development, for example, has difficulty coping with the lack of responsiveness and the separation between design and implementation.
  
  

• It can take a long time.
  There is a risk that the final version of the product will not be adapted to changes that have occurred during the design phase. This is the paradox of a model that does not accept change, even though its duration makes it impossible to avoid it.

All these frustrations have given rise to new working methods.

Alternatives to the V-cycle

There are several alternatives to the V-cycle. But we're going to concentrate on the Agile method, and more specifically the Scrum method.

V-cycle vs Agile

We're used to hearing about the Agile method. But in reality there is not one but several Agile methods.

In contrast to the cascade model, among others, they are characterised by a process that is :

• iterative: unlike the sequential and linear model, the iterative model involves the repetition of a cycle of operations. The project is refined with each iteration;
  
  
• incremental: the aim is to produce a little more each time, building the product piece by piece until the final result is achieved.

The combination of these two "Mona Lisa's" gives us a good idea of the iterative and incremental essence of Agile:

It's also important to stress that Agile methods require everyone to be involved, as well as being highly adaptable.

However, one of these methods has become very popular in recent years: the Scrum method, which is based on :

• 2 forms of division :
  • dividing time into sprints, or development cycles,
  • the division of tasks into user stories, or needs and functionalities to be developed;
    
    
• 3 main roles :
  • the Product Owner, a kind of project manager, the point of contact between the customer and the development team,
  • the Scrum Master, the conductor of the Scrum team,
  • the team: they carry out the tasks and produce the product;
    
    
• sprint meetings, known as Scrum Ceremonies.

V cycle vs Scrum, how do you choose?

Source : islean-consulting.fr

Ultimately, it all depends on the type of project you are going to work on and the teams you can call on. Because while Scrum is all the rage, using it doesn't mean you're immune to certain constraints.

• If you are working on a complex project, but have little visibility ;
• you are in a position to mobilise teams actively;

✅ O pt for Scrum. It's the most responsive method.

• If you or your customer have complete control over the project ;
• or the project involves few risks ;
• you prefer to rely on the documentation provided;
• you are mobilising staff who are difficult to bring together on a regular basis;

✅ O pt for the V cycle. It offers attractive economies of scale thanks to the fact that the entire scope of the project is dealt with in a single block.

So you've made your choice ;-)? Now let's look at the software you can use.

Selecting software for your project management

There is a wide range of software to help you manage your projects. Oracle SCM, for example, is perfectly suited to product lifecycle projects.

Choose yours according to the nature of your projects and the size of the portfolio you manage. To help you, here is a selection of three market-leading solutions:

• Bubble Plan - simple and graphic
  Whether you're a novice or an expert, Bubble Plan makes it easy to manage your projects.
  Intuitive, graphical and quick to learn, Bubble Plan lets you apply different project management methods, including the V cycle and Scrum.
  What's more, our support team will help you to get the most out of the tool, with personalised training and advice.
  
  
• Planisware Orchestra: PPM for large enterprises
  Planisware Orchestra is a highly visual tool that helps PMOs (Project Management Officers) manage, prioritise and plan the various projects of large companies.
  In fact, Planisware Orchestra combines both a strategic and operational vision, making it possible to manage an unlimited number of projects.
  And, of course, this solution combines different working methods (agile, V-cycle, state-gate, etc.), so as to meet all objectives.
  
  
• Project Monitor: collaborative and adaptable
  Available in both SaaS and on-premise modes, Project Monitor places particular emphasis on collective performance, encouraging collaborative working and exchanges between all the players involved in the project.
  Adaptable to all business lines (IT, strategy, R&D, etc.) and all working methods, Project Monitor provides teams with a library of different project models: V-cycle, Scrum, Prince2, etc., while remaining perfectly simple to use.
  And it's all so easy to use!

See all software Project Management

Project management... to each his own method and software

When it comes to project management, everyone has their own method.

While the V-cycle has many detractors today, we've found that it's still relevant in certain circumstances. It's up to you to weigh up the pros and cons.

To help you structure and equip your Project Office, we offer you this white paper :

One thing is certain, however: managing a large project or a substantial portfolio of projects requires the use of appropriate software. And the good news is that many of them can be customised to suit your needs, your company... and the working methods you have decided on.

For your part, do you prefer the V-cycle or the Agile method? Which project management model do you prefer?