Management Consulting
Software Engineering
Product & Strategy
AI
Security
Cloud
Data
Talent
Agile Transformations Explained with Mike Cottmeyer
LeadingAgile CEO and Founder, Mike Cottmeyer led two sessions at Agile 2017: “Agile Transformations Explained” and “Faster Food and a Better Place to Sleep: Applying Agile Outside of Software“. In this interview Mike and Dave discuss how an organization can get better at setting appropriate constraints, making iterative and incremental decisions that inform execution and creating feedback loops that will help drive a more successful adoption of agile across the organization.
Click here for an audio only version of this interview.
If you’d like to learn more about Mike’s sessions at Agile 2017:
Agile Transformations Explained: http://sched.co/ATZ5
Faster Food and a Better Place to Sleep: Applying Agile Outside of Software: http://sched.co/ATa2
And if you would like to contact Mike, here is how you can reach him:
Web: https://liminalarc.co/guides/mike-cottmeyer/
Twitter: https://twitter.com/mcottmeyer
LinkedIn: https://www.linkedin.com/in/cottmeyer/
Comment (1)
Alex
Don’t forget that in traditional project management change is acceptable. Change Requests exist for that reason. The example given about driving to San Francisco is more closely associated with a traditional project management approach with a very lenient view on Change Requests.
In an agile environment, we should start with an idea, such as driving to California, but let the learning from each iteration guide not only the route, but the final destination.
We have the idea to go to San Francisco. Why is it we want to go San Francisco? To see the Golden Gate Bridge? Let’s find a bridge within the first iteration and see if we learn from that. Perhaps we don’t like bridges at all. Maybe we need to pivot away from San Francisco.
Our journey should be set up to test hypotheses as soon as possible so that our destination is adjusted to get the most return when we eventually get there.