The Agile Daily Standup - AgileDad20 Marras 2024

There's No Course Correction In Agile - Mike Cohn

Last week a client mentioned they were using feedback they’d received on an MVP to make “course corrections.”
My ears bristle whenever someone talks about correcting course on an agile project.
There’s no such thing as course correcting in agile.
Am I crazy? After all, a fundamental part of agile is acting on feedback to improve a product.
My problem with the concept of course corrections is the way it presupposes there is one correct course and that it’s possible to know it in advance.
That’s not the case.
Sure, many products begin with a product backlog that describes what the product owner thinks will be the right combination of features to achieve the desired outcomes.
But on any non-trivial product, this recipe cannot be fully known in advance.
Successful products are created by iteratively homing in on the right combination of features. And that set of features can only be discovered through trial and error.
No matter how much research a team does before developing a feature, they never know how users will respond to the new feature.
Will they love it? Will they hate it? Will they use it? Will they use it as intended?
So a product owner or manager places a sequence of bets. The result of each bet guides the product owner in placing the next bet.
Course-correcting means there was a single, correct course. It implies that development has somehow deviated from this correct course and must be brought back in line.
Instead of talking about course corrections, I talk about course adjustments. As a team learns more, it adjusts course—which is the way to succeed with agile,

How to connect with AgileDad:

- [website] https://www.agiledad.com/

- [instagram] https://www.instagram.com/agile_coach/

- [facebook] https://www.facebook.com/RealAgileDad/

- [Linkedin] https://www.linkedin.com/in/leehenson/

Tämä jakso on lisätty Podme-palveluun avoimen RSS-syötteen kautta eikä se ole Podmen omaa tuotantoa. Siksi jakso saattaa sisältää mainontaa.

Jaksot(1641)

Be Here Now - Mike Cohn

Be Here Now - Mike CohnOne of my favorite books is one I’ve never completely read. It’s called Be Here Now. A friend’s older brother was reading it when I was 10. He let me page through his copy.The b...

4 Syys 9min

Be Here Now - Mike Cohn

4 Syys 9min

The Importance of Recognition

The Importance of Recognition Today we celebrate being recognized as a TOP 3 Agile Coaching podcast on the internet! How important is recognition? VERY IMPORTANT!! How to connect with AgileDad:- [webs...

4 Syys 5min

Agile Is Not Dead. AI Didn’t Kill It. And Waterfall Is Not Back

Agile Is Not Dead. AI Didn’t Kill It. And Waterfall Is Not BackA recent article claimed that Agile is dead, AI killed it, and Waterfall is back.It is a strong headline. It is also the kind of headline...

10 Elo 9min

How to Do Hard Things When You Have Zero Motivation

How to Do Hard Things When You Have Zero MotivationOne of the biggest mistakes you can make if you want to be consistent is trying to “trick” your brain.We’ve all seen the advice:“Just do it for two m...

7 Elo 5min

Agile Practitioners and Future Jobs

Agile Practitioners and Future JobsThere are insights that only come to me after a good conversation. My earlier self would have said “too late, a missed opportunity, again less than perfect”. Right n...

6 Elo 6min

Why Every Software Project Needs Project Management

Why Every Software Project Needs Project ManagementWhen people think about software development, they often imagine developers writing code. However, building successful software involves much more th...

5 Elo 3min

Isn’t That My Manager’s Job?

Isn’t That My Manager’s Job?When I work with product leaders on product strategy, one of the most common responses I hear is, “Isn’t that my manager’s job?” Sometimes it comes as a complaint. Sometime...

4 Elo 6min