A web project involves many internal stakeholders within the agency: designers, developers, integrators (see our article on web professions ), and at the clients: business managers, product managers, the IT department, etc. It is therefore necessary to coordinate the different talents invested in the project. All must be aligned to ensure the fluidity of project management . And of course, it is necessary to ensure that the expectations of users and clients are met .
To oversee all of this: a digital project manager . This person must manage their teams, make decisions, anticipate and ensure the smooth running of the project. But how do you manage its design? What are the important steps in a successful web project ?
Digital project management. In the photo we see a person's hands organizing a project on different screens
Design patterns of a web project
When designing a web project, you have the choice between adopting a traditional method or an agile method.
The classic method
In the traditional approach, called waterfall or V, the project is divided into tasks . In this model, the design and development of the project take time and require great rigor in execution . This method makes it possible to anticipate unforeseen events .
Project planning is done with the implementation of a macro-planning . In this planning, the tasks are sequenced, the development stages are broken down. Planning tools like GanttProject are often integrated into project management tools.
Example of a Gantt chart
Example of a Gantt chart (source Gantt.com )
The organization of the teams is defined at the launch of the project. A Steering Committee , a Project Committee , functional and technical meetings and a Quality Plan document are set up. In this context, the project manager can be associated with a project director or technical project manager.
The agile method
In the agile approach (or agile method ), the project is built gradually, based on feedback from users and the customer. This method is scalable , unlike the V method. The deadlines are divided into several sprints . At the beginning of the project, a product backlog is defined, i.e. the list of user expectations. These expectations are then distributed in each of the sprints. The duration of the task is determined according to a number of complexity points to be processed and not in days. At the end of each sprint, the tasks are reassessed and readjusted as needed. This constant reassessment allows us to stay as close as possible to user and customer needs.
In the team organization we find a daily scrum , a sprint planning meeting , a sprint review and a retrospective .
The choice of the method to adopt is decisive for the band database progress of the project and its implementation. In this choice, it is necessary to take into account: the teams and their habits, the deadline for rendering the project, the level of uncertainty of the project, if the prices, deadlines and functionalities are fixed. This choice must be clear to avoid any confusion.
Agile method function diagram with the different stages: product backlog, sprint planning, sprints, sprint review and retrospective
Agile Method Diagram
Which method is best suited to my project? To learn more, we recommend reading our article: " Agility, semi-agility, batch, V-cycle... how to choose? "
The steps of web project management
The 9 steps of a web project
The 9 Steps of Web Project Management
1. The preliminary draft
This step defines the strategic directions of the project. During this phase it is possible to conduct user tests , surveys or user research , etc.
This preliminary draft answers the questions:
What project?
Why this project?
How to carry out this project?
In what time frame?
What are the performance indicators to monitor?
2. The specifications
Developing a specification is essential. It is the reference document . It describes each function from the “user” and “functional and technical administrator” points of view. It sets the framework and gives the vision of the project .
