Discussion about this post

User's avatar
The Prairie Programmer's avatar

I think this sounds really good, but I doubt moving away from sprints would work well in most organizations. Smaller startups, sure, but rarely in established companies. The biggest hurdle, in my opinion is that lack of certainty from those running the business. Business people think they need estimates and certainty. They want to know what is going to be done and when, thus, knowing what work is going to be done in two weeks. If the people who run the organization can trust their development team, then maybe, but if the trust isn’t there, I really don’t see how they would move away from sprints…

Having said all that, thank you for this write up and some suggested approaches!

Expand full comment
Svet's avatar

I like that approach much more than sprints and waterfall, but of course the best approach would be based on your company's needs.

I am working in a huge corporation and we (devs) are giving feedback for improvement of the work process, a lot of teams started a transitioning from waterfall to sprints because of that, but I believe that the shape up would be the best approach and our team has been doing it without even realising we are doing that, thanks for sharing your thoughts, I'll do more research about the approach for sure and suggest to the people above me implementing it.

Expand full comment
10 more comments...

No posts