Thanks to the support of our users (see the discussion group thred http://groups.google.com/group/agilo/browse_thread/thread/c119eb374b731436) which helpd in nailing down a significant number of bugs,...
I am an Agile Coach and Trainer, I helped founding agile42, and I am helping customers all around the world to become more Agile. I am a speaker, and a writer, and I like to have fun :-)
- 26 July 2008
Thanks to the support of our users (see the discussion group thred http://groups.google.com/group/agilo/browse_thread/thread/c119eb374b731436) which helpd in nailing down a significant number of bugs, we just released another version of Agilo for Scrum 0.6.6.
The Bug fixed:
- Wrong calculation of Resources allocation time, while the total have been correct, in some situations the individual allocation where fractioned
- Support for unicode characters in resources names, there was a bog avoiding to update a task containing a unicode character in one of the resource names
- Improved stylesheet for agilo-theme.
Thanks once more for ...
One of the "assumption" that is often made, when starting to adopt Scrum, is that there will be a Product Owner and there will also be a Product Backlog. Well, it happens that the Product Backlog quality is one of the major responsible for the outcome of what the team will produce in terms of software, and is absolutely one of the most difficult things to work out. There are many problems related to having a right Backlog in place, and as you may guess there is no "one recipe" for the right Backlog, only some important ingredients to mix up in the right way ;-)
Product Backlog: Requirements or User Stories?
Hi there, spending some extra time at the airport (thanks to lovely pilot strikes) gives me the chance to write a bit about Scrum and the Product Backlog. A Product Backlog is a stack of "features" prioritized by Business Value, which means that on top of the stack there is always the most valuable item for the customer/client.
The owner of the Product Backlog is the Product Owner and as such should be the one and only authorized to make changes to the Product Backlog, given also the fact that the main responsibility ...