Technical Backlog Items and Bad Scrum
Mishkin Berteig
I'm a business leader, technology practitioner and people-inspirer - I fix productivity/efficiency problems in your organization. I do speaking, training, consulting and coaching on Agility, Innovation and AI.
The relationship between the business people and the Scrum team doing product development is simple: business people decide what product to build and why, and the technical people decide how to build it and who does it. Yet, in many organizations, I see techies insisting on putting lots of technical garbage on the Product Backlog. This is unacceptable and is a huge reason many Scrum implementations are no better than traditional waterfall projects. Here are two in-depth explorations of this idea.
First, a YouTube video:
Then, an in-depth Agile Advice article: Technical Push-Back - When is it Okay? When is it Bad?
PS. If you liked the video, please subscribe to our YouTube channel - we have lots more videos coming!
VP, Customer Experience at Xello
9 年As a product owner, what are the best ways to record technical debt and what are some approaches to prioritizing that work amid the continuous delivery of working software?