Comments on: Visualizing a Large Product Backlog With a Treemap http://blog.mountaingoatsoftware.com/visualizing-a-large-product-backlog-with-a-treemap Succeeding With Agile® Mon, 15 Mar 2010 07:36:32 +0000 http://wordpress.org/?v=2.9.1 hourly 1 By: Mike Cohn http://blog.mountaingoatsoftware.com/visualizing-a-large-product-backlog-with-a-treemap/comment-page-1#comment-34256 Mike Cohn Sat, 14 Mar 2009 02:18:07 +0000 http://blog.mountaingoatsoftware.com/?p=33#comment-34256 Burndown charts still show progress best in most cases. Color can be used to show some degree of progress with tree maps. Usually I use them that way and if the color indicates a troubled theme, I go look at a burndown chart or talk to the product owner and ScrumMaster about it. Burndown charts still show progress best in most cases. Color can be used to show some degree of progress with tree maps. Usually I use them that way and if the color indicates a troubled theme, I go look at a burndown chart or talk to the product owner and ScrumMaster about it.

]]> By: John Esser http://blog.mountaingoatsoftware.com/visualizing-a-large-product-backlog-with-a-treemap/comment-page-1#comment-34255 John Esser Sat, 14 Mar 2009 01:34:27 +0000 http://blog.mountaingoatsoftware.com/?p=33#comment-34255 Mike, nice article. I can see tree maps as a useful visual tool for viewing the realtive size of themes against each other, but they don't seem to indicate progress and projected finish time well. It seems you could do "theme burndowns" or "burndown rollups" across teams very easily. They would also be accurate as long as you have a consistent baseline for story point estimation. Mike, nice article. I can see tree maps as a useful visual tool for viewing the realtive size of themes against each other, but they don’t seem to indicate progress and projected finish time well. It seems you could do “theme burndowns” or “burndown rollups” across teams very easily. They would also be accurate as long as you have a consistent baseline for story point estimation.

]]> By: Orlando Car Rental http://blog.mountaingoatsoftware.com/visualizing-a-large-product-backlog-with-a-treemap/comment-page-1#comment-23174 Orlando Car Rental Wed, 24 Sep 2008 14:05:34 +0000 http://blog.mountaingoatsoftware.com/?p=33#comment-23174 Hey! thanks Mike this was great posting it will actually help to be more organized, I'm a big time management nut so, this kind falls directly into my home base visualizing allows you to look ahead and see any hiccups that may be in the road (kind of like a road map). Hey! thanks Mike this was great posting it will actually help to be more organized, I’m a big time management nut so, this kind falls directly into my home base visualizing allows you to look ahead and see any hiccups that may be in the road (kind of like a road map).

]]> By: Mike Cohn http://blog.mountaingoatsoftware.com/visualizing-a-large-product-backlog-with-a-treemap/comment-page-1#comment-20723 Mike Cohn Wed, 06 Aug 2008 11:54:34 +0000 http://blog.mountaingoatsoftware.com/?p=33#comment-20723 Hi Shawn-- I'm glad you found the Agile Estimating and Planning book to be useful. The advice on establishing a common baseline that I blog about here (as soon as I can find a spare 10 minutes) will be consistent with what's described in the book. --Mike Hi Shawn–

I’m glad you found the Agile Estimating and Planning book to be useful. The advice on establishing a common baseline that I blog about here (as soon as I can find a spare 10 minutes) will be consistent with what’s described in the book.

–Mike

]]> By: Shawn Lauzon http://blog.mountaingoatsoftware.com/visualizing-a-large-product-backlog-with-a-treemap/comment-page-1#comment-20654 Shawn Lauzon Tue, 05 Aug 2008 00:07:30 +0000 http://blog.mountaingoatsoftware.com/?p=33#comment-20654 Mike, I was re-reading your excellent Agile Estimating and Planning book, and again came across your suggestion on how to establish a common basis for estimates. You mention in your previous response (July 19th) that you would blog about this topic soon; do you have new recommendations, or just the tips from the book? Thanks ... shawn. Mike,

I was re-reading your excellent Agile Estimating and Planning book, and again came across your suggestion on how to establish a common basis for estimates. You mention in your previous response (July 19th) that you would blog about this topic soon; do you have new recommendations, or just the tips from the book? Thanks …

shawn.

]]> By: Dusan Kocurek http://blog.mountaingoatsoftware.com/visualizing-a-large-product-backlog-with-a-treemap/comment-page-1#comment-20427 Dusan Kocurek Sat, 26 Jul 2008 15:45:40 +0000 http://blog.mountaingoatsoftware.com/?p=33#comment-20427 Hi to all, we implemented this great idea in ScrumDesk. See more on page http://www.scrumdesk.com/weareworkingon.html. Hi to all,

we implemented this great idea in ScrumDesk.
See more on page http://www.scrumdesk.com/weareworkingon.html.

]]> By: Mike Cohn http://blog.mountaingoatsoftware.com/visualizing-a-large-product-backlog-with-a-treemap/comment-page-1#comment-20072 Mike Cohn Sat, 19 Jul 2008 01:38:33 +0000 http://blog.mountaingoatsoftware.com/?p=33#comment-20072 Hi Shawn- Yes, you would need to have a consistent scale for all stories. There are ways to do this but since I haven't blogged about it before I'll try to do so soon. Hi Shawn-

Yes, you would need to have a consistent scale for all stories. There are ways to do this but since I haven’t blogged about it before I’ll try to do so soon.

]]> By: Shawn Lauzon http://blog.mountaingoatsoftware.com/visualizing-a-large-product-backlog-with-a-treemap/comment-page-1#comment-20066 Shawn Lauzon Fri, 18 Jul 2008 21:41:20 +0000 http://blog.mountaingoatsoftware.com/?p=33#comment-20066 Hi Mike, I like how this visualizes, but don't you need to have a consistent scale of all your story points across the entire project? If you don't have that, the sizes won't be equal. With 500+ developers on a project, getting some consistency across all of those people would be quite difficult. Hi Mike,
I like how this visualizes, but don’t you need to have a consistent scale of all your story points across the entire project? If you don’t have that, the sizes won’t be equal. With 500+ developers on a project, getting some consistency across all of those people would be quite difficult.

]]> By: Syed Rayhan http://blog.mountaingoatsoftware.com/visualizing-a-large-product-backlog-with-a-treemap/comment-page-1#comment-19450 Syed Rayhan Sat, 12 Jul 2008 19:55:41 +0000 http://blog.mountaingoatsoftware.com/?p=33#comment-19450 Mike, Thanks for this timely idea. We are developing a Web-based Scrum tool- ScrumPad (http://www.scrumpad.com). We implemented themes as tags, but were investigating how best to display large product backlog. This is something we would incorporate in our product soon. I agree we could organize themes at any levels, but I would say having a few level deep might make a product-backlog unnecessarily complex than it needs to be. Mike,
Thanks for this timely idea. We are developing a Web-based Scrum tool- ScrumPad (http://www.scrumpad.com). We implemented themes as tags, but were investigating how best to display large product backlog. This is something we would incorporate in our product soon. I agree we could organize themes at any levels, but I would say having a few level deep might make a product-backlog unnecessarily complex than it needs to be.

]]> By: pligg.scrum-on.com http://blog.mountaingoatsoftware.com/visualizing-a-large-product-backlog-with-a-treemap/comment-page-1#comment-19219 pligg.scrum-on.com Thu, 10 Jul 2008 13:38:53 +0000 http://blog.mountaingoatsoftware.com/?p=33#comment-19219 <strong>Visualizing a Large Product Backlog With a Treemap...</strong> Mike Cohn writes about using a treemap concept to visualize product backlog. What is especially nice about this aproach it is that the estimate becomes more tangible.... Visualizing a Large Product Backlog With a Treemap…

Mike Cohn writes about using a treemap concept to visualize product backlog. What is especially nice about this aproach it is that the estimate becomes more tangible….

]]>