By François Le Crom, VP R&D
In the software industry, there’s no debate: agile methodologies are now the de-facto standard. If you haven’t done so already, you need to make your R&D teams agile. But why is this so ?
First, because it’s an industry where things change, fast. You have to be extremely reactive. You need to deliver value to customers in rapid cycles – almost continuously, as opposed to the 6+ month cycles of yesteryear. So your roadmap must adapt to events.
Second, because the work itself is getting increasingly complex. You can no longer afford to work in monolithic serial mode: write a detailed book of requirements, then develop, then test – and deliver the result to the customer after a year. You need to zoom into the details as you go along, advancing in small increments and getting feedback from your customer as you develop so that you can adapt to changing needs. That’s the agile methodology.
But how do you transform your teams so that they adopt this methodology? How do you make your R&D teams agile?
That’s what I have been doing since I joined Anevia in 2018. Anevia had already adopted the agile methodology, of course. But some teams were more agile than others. And all teams could be lifted to an even higher level of agility.
The goal for us at Anevia is to be able to deliver something valuable to our customers at the end of each sprint. That’s every three weeks. And we have already reached that goal for one of our products.
Find out how we reached this goal at Anevia, and the lessons I’ve learnt in the process, in this article I wrote for BusineXperience.
Share this article