@dariogriffo@allenholub@flappytweety But that is my point. I would not use scrum to deal with standard requests of work, I would use kanban. But if I had to build something complex then regular feedback is invaluable when navigating complexity. That is what scrum is designed for.
@flappytweety@allenholub If you are worried about writing shit code then build a smaller chunk of working software where the code isn't shit. Slice the value.
@penguinvondoom@flappytweety@allenholub So you think businesses do have a bottomless pot of money allowing their teams to take as long as it takes to get solutions right with clean code?
@flappytweety@allenholub I think of the timebox as an investment. The business are investing in say 2 weeks of development. It means the team have a finite amount of time to find a solution, build, demonstrate it and learn from the feedback that comes from the demo. Do people panic during a hackathon?
@atlnerd4love@allenholub Haven't you just demonstrated where it might be appropriate, in the form of options.
Whether you are then held to those estimates and punished for not meeting them is a different conversation.
@allenholub I'm confused. Scrum does suggest that PBIs are user stories. In fact Scrum does not even mention user stories at all. Extreme Programming does, but Scrum doesn't.
@iamtestr@allenholub Kanban has practices that can help manage the flow of value. Delivering valuable software, and working closely with users/customers is awesome, but they are principles you have chosen to use, that wouldn't change if you switch to scrum or XP or any number of frameworks/methods.
@neil_killick I like the principle, but I work with a team that slices their stories by user capabilities rather than releasable value. They then use the stories as historical data when using monte carlo forecasting. But I am guessing the stories you describe here are a standalone feature.
@allenholub @smelly_Cat_0204 What if you were porting a system from a monolith to a microservices architecture, and there is a minimum set of core functionality that is needed for customers to do what they were able to do on the old system and that was around 6m to 1y worth offort, but you didn't know that.
@allenholub Very true @allenholub. But only today I was suggesting to a team to open up their estimate range to cover the uncertainty. If the biz wants to pay more money for more accuracy then that's their choice. A waste imho, but their choice.