Hi Nigel, On Friday 02 July 2010, culliard wrote: > Ability to add user stories directly from backlog/whiteboard.
Definitely! > If task estimated days is updated, the same value should also be > applied to Remaining time. One less field to fill in when creating a > load of tasks (time saved adds up). If a task is re-estimated then > remaining time from previous work on the task is irrelevant. > Remaining time can be tweaked if necessary and updated daily. I'm not sure what you mean by estimated days. By default, Agilo does not capture estimated days (which sounds like you mean 'initial remaining time'), only the actual remaining time of a task - at the end that is 0. > Ability to create task and add new task in one operation - again > saves time when adding many tasks So you mean having a new dialog immediately after the old one closes? > It would be useful to have user story 'info' button on whiteboard - > same as in backlog. Which button do you mean? On the white board, you can just click "Add new task" or open an existing task and then expand the user story with the "Show Story" button. > Backlog view should show sum of story points, task estimates, > remaining time and actual days. Separate columns should not be > required. - just a dedicated row for 'totals' underneath column text. > How do I get Total Story points to display on backlog? This is useful > for release backlog. Note we use only user stories and tasks - not > Requirement. Yeah, we had to remove this feature to get the last release out and did not yet add it again. No excuse not to have it! > Backlog should also have ability to collapse/expand user stores (or > maybe hide/display tasks) and save view for the reason described > above. I read another post suggesting something similar. Personally, I've never missed this feature. If you hide closed tickets, you should only see tasks of the top stories very close to the top of the screen. Since you work the backlog from the top to bottom, I never needed to scroll a lot. It almost seems like having to collapse a story means it is in your way of working on a lower priority story... which poses the question why you do not work on the higher priority story first? :-) > It would be very useful to have filters on backlog/sprint e.g. owner, > status etc. There's a filtering option. You can set the backlog_filter_attribute option in the [agilo-general] to filter by any attribute you like (owner, component, status) -- although instead of filtering by owner or status, I recommend the "hide closed" and "show mine" button. > Whiteboard should clarify state of user story. I know 'Done' is > supposed to mean developed and accepted but need some clarification > is it is with programmer or tester. I suppose there are two ways - > Done column divided into 2 - completed and accepted. Completed is > based on sub-tasks > - Inprogress split in 2 - in progress development and in-progress > acceptance testing Done should mean "done" by your definition of done -- which probably includes acceptance tests are done. As testers should be part of the sprint just as developers (teams are cross-functional), you could create tasks for testing at task breakdown, and make them part of your estimation. Then when a story is implemented, but needs an acceptance test written or executed, you can simply see it on the whiteboard or backlog as that. > Sprints should have a goal. It is possible to add this to sprint > description field. I would suggest that it should also be shown on > Backlog/whiteboard. Since description can be very long maybe a > separate field for the sprint goal would be better. Yeah. We're on the same page here. Right now you can use the description field for this, but as you say, it is not shown at a lot of places (like the header of the white board). > Ability to assign contingency against specific person. Our developers > usually have to support several products at the time as developing > new ones. I need to evaluate changes coming in Trac specificallly > multiproject support but has Agilo 1.3.0 been tested with it? No, the 0.12 release is not yet supported. There's no time frame for when the switch will happen yet. > When using days not all of agilo show correct units. > - whiteboard shows 'H'. > - Admin -> Teams -> Manage teams shows 'weekly capacity in hours'. > - Selecting a team, each developers capacity in 'h' > - Contingents don't show any hours That's true, there are some inconsistencies in there. > Team Capacity My sprint is starting 2nd July to and finishes on 30th > (i.e. all done by close of 29th) > I have 6 team members (D = Developer) units in days for all of July > (1st to 30 th July > - D1 - 15 (0.75 per day) > -D2 - 13.5 (0.75 per day) > -D3 - 11.7 (0.65 per day) > -D4 - 15 (0.75 per day) > -D5 - 10.8 (0.6 per day) > -D6 - 1.6 (0.8 per day) > > Contingency for D1 = 5days > > Total team Capacity = 59.1 days this sum is correct apart from the > fact that it includes 1st and because it is passed I can't change it. > Should it only show for sprint duration - not whole months? The Total team capacity is per sprint. I hope I could resolve some uncertainties that you may have had. Obviously, I cannot give you an immediate response for the features requested, but I have brought up your suggestions with our Product Owner and we'll see what he selects for the next releases. Cheers Robert -- Follow Agilo on Twitter: http://twitter.com/agiloforscrum Please support us by reviewing and voting on: http://userstories.com/products/8-agilo-for-scrum http://ohloh.net/p/agilo-scrum http://freshmeat.net/projects/agiloforscrum You have received this message because you are subscribed to the "Agilo for Scrum" Google Group. This group is focused on supporting Agilo for Scrum users and is moderated by agile42 GmbH <http://www.agile42.com>. To post to this group, send email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/agilo
