Agile change and transformation
Working in software development means everything around us is in a constant state of change. Tools, requirements, process, maybe even team members! When things around you change, do you scream, “Why are we always Changing things?” or “What if we just wait?”.
I am frequently amused when the same people who believe that it is not possible to get the requirements for a product correct up front, and therefore want to use Scrum for development, will in the next breath explain how they aren’t quite ready to start using Scrum because they haven’t worked out all of the details of their Scrum approach! This type of thinking is poorly aligned with fundamental Scrum principles.
During my software development career, I have seen a good deal of software development approaches or methodologies used in different organizations. When a new and supposedly better approach is promoted, some people tend to adopt it with an attitude that could sometimes be close to a religious zeal.
This presentation explains how an organization moved from 17 component backlogs to one shared, results-focused product backlog—and what that changed for delivery speed and alignment.
You know that when you deal with this type of topic, you are writing about a touchy subject. When I write that Agile has sometimes been sacralized, my aim is not to hurt any religious or philosophical belief, but rather to see how men behave when adopting new ideas.
Agile is everywhere. Everybody is talking about it. Everybody wants to start the Agile journey with the various Agile frameworks like Scrum. And then, many hit the ceiling and give up the Agile journey altogether.
Benjamin Igna worked with Ford Motor Company and lead the transformation within the launch of the new Ford Explorer (EV). In this presentation, he shares his learnings and approaches during the change towards agility of the CX organization across 5 different Markets and cultures affecting multiple hundred people in sales and marketing.