11 Jun Your media library project using Agile methodology?
Each of your projects deserves a method adapted to your needs, determined on a case-by-case basis. Our teams can advise you in choosing the one that’s best for you. More and more often, we recommend Agile methodology – for our media library projects, for example. The approach often suits these projects for a number of reasons. Our clients’ need to experiment, iterative work based on an existing solution, etc.
What is Agile methodology?
Bringing together the best practices from IT development projects, this methodology can be applied successfully to communications and marketing projects. Such as during the configuration and launching of a media library.
Agile methodology is based on four fundamental values:
- The team (“Individuals and their interactions rather than processes and tools”),
- The application (“Operational software rather than exhaustive documentation”),
- Collaboration (“Collaboration with clients rather than contractual negotiation”),
- Acceptance of change (“Adapting to changes rather than following a plan”).
Agile methodology focuses on the users, encouraging interaction with them.
What’s the difference between Agile methods and traditional ones?
In “classic” project management, the various steps are established based on a linear approach. They are carried out one after the other, with a predefined goal. This traditional method is often called the “V-model”. It involves a phase at the beginning of a project during which precise and detailed specifications are established, which serve as the basis for a strict schedule that leaves little leeway for changes and adjustments during the course of the project.
Agile methodology, on the other hand, divides a project into several parts referred to as sprints. By establishing short-term aims in this way, it makes it possible to regularly review each modification and to adjust the subsequent course of the project accordingly, allowing users to change their minds at any time. At the end of each sprint, users always have a test version: in addition to truly collaborating with the project team, they can regularly see what progress has been made in the configuration of their media library.
As a result, Agile methodology offers numerous advantages
- For users: Agility allows users to manipulate a partially configured platform very quickly. Whether the solution is correctly configured can be verified under real conditions. Without having to wait for all specifications to be completed. This simplifies things and allows you to avoid getting bogged down in abstract technical aspects: you see what you’ve designed very quickly. The ultimate aim is to satisfy actual needs rather than to respect those expressed at the project’s outset, which may have evolved.
- For the project: Agile methodology avoids the classic tunnel effect of V-model projects – that is, the phase during which users lose sight of their project’s progress while waiting for the prescribed delivery. The methodology is even more adapted if the user chooses to start with a standard front office such as Wedia CrossMedia’s: adapting an existing model rather than creating complete and definitive specifications on a template-by-template basis saves time.
Ultimately, Agile methodology can result in:
- a configuration that’s better adapted to actual needs, while allowing you to avoid much of the analytic formalism of classic methods,
- and, consequently, reduced costs by prioritizing what really matters for a project.