When should the V-cycle method be used in a project?

Definition of the V-cycle

The V-cycle model in project management is derived from the waterfall model that was theorized in the 1970s, allowing development processes to be represented linearly and in successive phases. However, from the beginning of the 2000s, it began to be questioned due to the acceleration of technological changes, which favored the emergence of so-called “agile” methods. The term “V” in the V-cycle refers to the schematic representation of this cycle, which takes the form of a V, with a descending phase followed by an ascending phase. The V-cycle links a validation phase to all the implementation phases.

The V-cycle method is often used in software or system development projects, where it is crucial to follow a structured and methodical process. It is particularly suitable when project specifications are well defined from the start and there are few changes or uncertainties throughout the development process.

Some situations where the V-cycle method may be appropriate

• Projects with stable requirements

When project requirements are clearly defined from the start and are unlikely to change significantly throughout the project, the V-cycle approach can be effective. It makes it possible to follow a linear process and to verify at each stage that the requirements are met.

• High risk projects

If the project has significant risks, such as safety issues or regulatory compliance issues, the V-cycle method may be appropriate. It offers a high level of verification and validation at each stage, which helps to minimize risks and ensure that requirements are properly taken into account.

• Projects with detailed specifications

When project specifications are very detailed and require a rigorous approach, this practice can be beneficial. It allows a clear path to be followed from the development phase to the test phase, ensuring that every aspect of the project is properly treated.

• Projects with strict traceability

If traceability of requirements is a priority, the V-cycle method may be appropriate. It allows each stage of the development process to be linked to the corresponding requirements, which facilitates verification and validation.

However, it is important to note that the V-cycle method may be less suitable for projects where requirements are subject to frequent change, where an iterative approach is required, or where flexibility and responsiveness are a priority. In such cases, Agile methodologies such as Scrum or Kanban may be more appropriate.

The scrum method, an iterative process

In industrial sectors, companies must be reactive and adapt quickly to changes in these sectors. This requires effective communication and rapid implementation of decisions made. Let's see if Scrum meets these requirements.

The Scrum method, in reference to the rugby melee, is an agile organization method that is widely used in software development, but also applicable to other areas. It is based on an iterative and incremental process, promoting collaboration, transparency and adaptability.

In Scrum, the project is divided into work cycles called “sprints.” Each sprint has a fixed duration, usually two to four weeks, and produces a potentially usable deliverable at the end of the sprint. Sprints are preceded by a sprint planning meeting, where the Scrum team selects backlog items. (list of tasks or functionalities to be performed) to be included in the sprint.

The development team then works independently to achieve the sprint goals. Daily coordination steering meetings called “melees” (or “stand-up meetings”) are organized to discuss the progress of work, challenges encountered and planning for the next day and to facilitate decision-making.

At the end of each sprint, a sprint review is organized to present the work done to stakeholders and to gather their feedback. A sprint retrospective is also carried out to assess the process and identify possible improvements for future sprints.

Key roles in Scrum include:

• Product Owners: Responsible for defining project goals, prioritizing backlog items, and ensuring that the team develops maximum value for the client.

• The development team: A group of professionals responsible for completing backlog tasks and delivering features at the end of each sprint.

• Scrum Masters: Responsible for facilitating the Scrum process, removing obstacles encountered by the team, and ensuring that Scrum principles and rules are adhered to.

The Scrum method offers a flexible approach that makes it possible to adapt to frequent changes and optimize collaboration between team members. It focuses on the regular delivery of features, a high degree of transparency, and the self-organization of the team.

What is the difference between the Scrum method and the V-cycle?

The Scrum method may have some shortcomings in terms of documentation and technical quality. Scrum teams sometimes tend to overlook these aspects in order to deliver the product as quickly as possible. However, this approach is flawed.

Agility is not just about delivering the product quickly, but rather about delivering high-quality products on a regular basis, which is fundamentally different.

Wanting to deliver quickly by sacrificing quality documentation, that is to say by writing as the project evolves, is in reality contrary to the agile approach. Indeed, the maintenance teams that will take over the project may be disoriented if it is not regularly updated.

This problem is less present in the V-cycle method, because each actor in the project communicates mainly through the documents transmitted at each stage. As a result, the documentation is generally well up to date.

In short, the V-cycle, with its planned structure and well-defined development phases, makes it possible to prevent the lack of communication while ensuring compliance with deadlines.

What are the 5 stages of the agile life cycle?

Step 1: Define the project framework

To begin with, it is necessary to define the framework of the project, including the main objective and associated requirements. Before moving on to the development phase, needs analysis and the definition of specifications are essential.

Let's take an example to better understand. Let's say you are a professional photographer and you want to develop a new wedding photography service. Your objective could be “Create a high-end wedding photography service” and your requirements could be “Offer customized packages that meet the specific needs of customers.”

Step 2: Prepare the backlog

Once the project framework is established, it is time to prepare the backlog. This consists of drawing up a comprehensive list of actions to be taken to reach the final objective and prioritizing them. During this exercise, it is important to keep in mind the framework of the project as well as the needs of the customers.

As a photographer, you can take into account different customer requests for photography styles, shooting locations, custom photo albums, etc. You can organize these requests in a tracking table, where you have a “Full Backlog” column for all requests and a “Sprint Backlog” column where you select the tasks to be completed for each sprint based on their priority.

Step 3: Work on sprint tasks

Once the backlog tasks are set, it's time to work on each one throughout the sprint.

During each sprint, you can focus on specific aspects of the wedding photography service, such as creating an online portfolio, developing packages and rates, planning shooting sessions, etc. By the end of each sprint, you should have completed some of the planned work, for example, finalized an online portfolio to present your work to potential clients.

Step 4: Gather feedback

At the end of each sprint, it is important to do a sprint review. During this review, gather as much feedback as possible from your customers or users.

Organize meetings with the bride and groom to present your portfolio to them and discuss their expectations. Take note of their preferences in terms of photography styles, shooting locations, etc. This feedback will help you adapt your offer and better meet customer needs.

Also, do a sprint retrospective with your team (if you have one) to assess sprint results, identify strengths and weaknesses, and take action to improve your service.

Step 5: Start over

After collecting feedback from your customers and users, it's time to start the process again. Consult the “Full Backlog” column for all requests that have been made to you and determine which ones are priority.

Then transfer these requests to the “Sprint Backlog” column and create a list of the various tasks you need to complete to process them.

Work on these tasks during a sprint. At the end of the survey, gather feedback again, add it to your backlog, and start the cycle again to continue improving your wedding photography service.

In the context of agile methods such as Scrum, XP, RAD, etc., the project evolves by iterations, through the repetition of a cycle of operations (the sprint in the context of Scrum). As we have seen, the V-cycle defines the entire final product from the initial stages and leaves little room for adaptation later on.

On the other hand, agile methods make it possible to develop the product by incrementation. We produce a little more each time, piece by piece, to arrive at the final result. The V-cycle, on the other hand, concentrates the realization of the whole in a single phase, which is entirely designed beforehand and verified afterwards.

This lack of adaptation and flexibility of the V-cycle has led precisely to the emergence of agile methods, especially in the fields of software and marketing, in order to respond to technological changes and consumer demands that are evolving more and more rapidly.