Recommended
Recommended
More Related Content
Similar to Backlog or Black Hole? How to Manage Massive Backlogs
Similar to Backlog or Black Hole? How to Manage Massive Backlogs (20)
Recently uploaded
Recently uploaded (20)
Backlog or Black Hole? How to Manage Massive Backlogs
- 1. Backlog or Black Hole? How to Manage Massive Backlogs
- 2. 2© Perforce Software Inc. All Rights Reserved. Presenter Johan Karlsson jkarlsson@perforce.com Product Evangelist, Hansoft Perforce Software
- 3. 3© Perforce Software Inc. All Rights Reserved. What You’ll Learn 1 How to Identify a Backlog Problem 2 Common Causes of Oversize Backlogs 3 How to Regain Control of Your Backlog
- 4. 4© Perforce Software Inc. All Rights Reserved.
- 5. 5© Perforce Software Inc. All Rights Reserved. Can’t see the massive backlog because of all the backlog items?
- 6. 6© Perforce Software Inc. All Rights Reserved.
- 7. 7© Perforce Software Inc. All Rights Reserved. Other Warning Signs Low Feasibility — Your product backlog has too much work to complete in a reasonable time frame. Low Trust — People are secretly creating their OWN lists, apart from the real product backlog. Low Pride — You want to hide the product backlog from teams and stakeholders.
- 8. 8© Perforce Software Inc. All Rights Reserved. A Common Model That Causes Problems See Pawel Brodzinski Options, Options, Options: http://brodzinski.com/2013/09/options-options-options.html Tasks, spikes, bugs, sub- tasks etc….
- 9. 9© Perforce Software Inc. All Rights Reserved. Typical Reasons Provided Hoarding Dependency Resolution Lack of Clear Ownership Information Need
- 10. 10© Perforce Software Inc. All Rights Reserved. Two Paths Forward Easy Hard
- 11. 11© Perforce Software Inc. All Rights Reserved. • Short-term solution. • Throw the old backlog out. • Start fresh. • Result… The Easy Route Easy
- 12. 12© Perforce Software Inc. All Rights Reserved. Can’t see the massive backlog because of all the backlog items?
- 13. 13© Perforce Software Inc. All Rights Reserved. • Long-term solution. • Understand problem as systematic. • Deal with root causes (the decision-making model). • It impacts: • Culture • Autonomy • Organization The Hard Route Hard
- 14. 14© Perforce Software Inc. All Rights Reserved. Solution? Tools Expertise Decision-Making Model
- 15. 15© Perforce Software Inc. All Rights Reserved. A Better Model Limit backlog size on each level
- 16. 16© Perforce Software Inc. All Rights Reserved. Prioritize Culture! Culture First — We must establish a culture that enables a better decision-making process. Then Backlog — With proper culture in the place, backlog can be addressed holistically.
- 17. 17© Perforce Software Inc. All Rights Reserved. Concrete Practices Demand ”why” statement. Handle aging backlog items. Celebrate deliveries! Have ”kick-outs” instead off ”kick-offs”. Be transparent. (”We have an issue here.”) Rank items (There can only be one #1.) *Radical* Rotate product owners.Product Backlog 1 2 3
- 18. 18© Perforce Software Inc. All Rights Reserved. • Don’t avoid it, deal with it! • Deal with it permanently through better decision-making. • But culture first, or you won’t get anywhere. Takeaways
- 19. Questions? Thank you very much for attending!
- 20. Attend our next Hansoft Demo on May 9! Try Hansoft Free. Visit www.perforce.com Johan Karlsson, jkarlsson@perforce.com
- 21. Follow us for news and insights! Visit www.perforce.com
Editor's Notes
- Been with Hansoft, a backlog management tool, for 5 years, seen hundreds of backlogs Joined Perforce when they acquired Hansoft last year Feel free to reach out to me after this presentation with any questions you might have.
- @JAKE — We’d like this slide to look like it becomes TOTAL MESSY CHAOS [ORDER > CHAOS]
- Information Need — Detailed scope is valued, so everything is broken down to its most-granular level before work starts. Hoarding — Like squirrels, people document everything, are afraid to remove anything. Lack of Clear Ownership — People take care of what’s THEIRS. Where two people own, no one owns. Dependency Resolution — Backlog explodes from interdependencies. (”If we do that, we must do this!”)
- Tech: Excel: Not collaborative as it does not scale Issue tracker like JIRA: Not built for backlog management, are issues really what youw ant? Imagine the time people are spending in tools like JIRA today to make changes. There are real backlog management tools out there, obviously Hansoft is one of those. Expertise: — Understanding your market, understanding how your product is improved, understanding where limits can be set (attending this webinar will help!) New Decision Making Model - Even with all the tech and expertise – the root cause is often systemic and a new decision making model would be needed. SCRUM is a typical first example.
- (nothing that is validated or can be validated)
- If you want to have a demo of this – please reach out to me directly.
- Facebook: https://www.facebook.com/Perforce/ LinkedIn: https://www.linkedin.com/company/perforce-software?trk=top_nav_home Twitter: https://twitter.com/perforce Blog: https://www.perforce.com/blog