Category: product
[Apple is a] company that can make a mobile phone with no buttons, no picture messaging, slow Web access and no video capture into the most desirable phone on the planet © crave @ cnet
This Monday I was following the opening WWDC keynote. I find it remarkable how Apple manages to pump out one excellent product after another. In most of the areas they decide to touch they are able to rapidly become the makers of the most desirable product on the market. Their iPod redefined the music player market, MacBooks are becoming more beautiful faster, than Microsoft can copy even minor bits of Mac OS X, now iPhone with its MobileMe are going to get a decent part of the smartphone market piece. Even their relative failures would be considered a success for many other companies.
I often wonder what kind of software product/project is a best-fit for Agile development model. While the answer lies somewhere in the product architecture, customer feedback loop, team structure, geographical distribution of teams and various other aspects, I am starting to realize that the "Delivery Channel and Mechanism" will actually provide a good decision box to start the algorithm. "Ends justify the Means" seems very appropriate here.
Bas Vodde collected and published examples and templates of the Scrum product and Sprint backlogs. Most of them are in MS Excel format. Some (XLS) include a lot of comments, some (XLS) are very colourful. Check them out, Excel can really cover most of the needs of the archived backlog tracking.
Cached templates
Here are the cached copies of templates that I reviewed on this website. Or will review soon ;)
See Also