Which methodology could make your complex Digital Projects a success?
World of Digits / Explore
The same problems can arise with digital projects, further complexified by the abstract nature of its domain.
When a customer orders a car, one wouldn’t expect him to complain about the color or the engine’s performance upon delivery, nor would he expect to have these changed without paying for them. On the opposite, when a client orders a website, it’s not rare that he ends up asking for more animations on the home page or adding an extra field in a form. A lot of Project or Account Managers will agree with the fact that asking more budget to the client for this kind of forgotten or misunderstood features is always tricky and can create a bad client relationship.
According to my experience, here are the main reasons:
To solve these frequent issues, agencies have thought of different solutions:
For all of these reasons, complex digital projects managed using the traditional project management methodologies have generated a lot of frustration and have shown limitations.
That certainly explains mainly why, in 2001 in Utah, 17 developers decided to produce the ‘Agile Manifesto’ that resulted in 4 core values:
To summarise briefly, managing a project using the traditional methodology could be compared to a relay race where each runner waits for the previous one to start his part and observes from a distance the rest of the race whereas the Agile methodology is more similar to a Rugby game where a pluridisciplinary team moves together progressively at the same rhythm.
Scrum, which is probably the most famous Agile method, implies a dedicated collocated team working on short iterations (called sprints) in a daily physical collaboration with the business (represented by the Product Owner). A Scrum team can be composed of internal employees but can also be provided fully or partly by a consulting agency specialised in Agile transformation and its application.
Having the Scrum development team working directly at the client’s office has a lot of advantages and can solve most problematic issues facing agencies as described above:The dedicated team is generally invoiced on a daily basis and therefore the budget is based on the time spent on the project/product and not on the functionalities. This allows to start the project very quickly and avoid endless discussions between the agency and the client on which features were foreseen or not. It follows the value “Customer collaboration over contract negotiation”. It also pushes the business to focus on the most valuable features. Instead of developing long and complex projects that could take often more than one year, the Scrum methodology encourages companies to deliver valuable products as quickly as (humanly) possible to directly experience the product on the market and quickly measure the outcomes. This way, companies are “Responding to change over following a plan.”
The client represented by the Product Owner is often seated next to the development team and is involved in most of the Scrum ceremonies and decisions. It allows him to give continuous feedback to the team and avoid having to validate long analysis. It follows the value ‘Individuals and interactionsover processes and tools’ and fosters ‘Working softwareover comprehensive documentation’.
It’s not a coincidence if Agile projects are 28% more successful than traditional projects. (Source: ClearCode) and that the Agile methodology has a 64% success rate, compared to just 49% for the waterfall mode (source Ambysoft).
Scrum is however not 100% applicable for all digital projects and clients as it requires firstly an important budget and secondly team members to be fully allocated to the project. Developing for example a showcase website for a few weeks using the whole Scrum methodology might not be adapted. However, an agency managing multiple small projects for multiple clients could still integrate some Agile principles such as having a pluridisciplinary team, holding scrum ceremonies, following a Scrumboard, etc. This is why at World Of Digits, we also have a multi-skilled team working in-house to provide web solutions for smaller projects for our clients.
To sum up, as soon as a digital project is complex enough, I would strongly recommend applying the Scrum methodology to go from a relationship of caution and tension with your clients to a collaboration based on trust and on the common desire of adding value to the final product and end-users. Such a change is of course challenging to implement. If you want to know more about applying Scrum in your company, contact our Scrum experts or get Scrum Master certified.
written by Samuel Gutmann9