Hell again! Thanks to earlier help from people here, I've now successfully completed our first sprint, and persuaded the management to go full steam ahead with Agilo. It's early days, but I thought I'd share some of the questions my team has asked, and problems they've run into:
* Team Members In small organisations, the same person may have different roles in different teams. For example, while I can be the sprint manager of one sprint, I could be a programmer on another... I don't particularly mind if 'sprint managers' are always 'sprint managers', as sprint security isn't a real issue for us.. But I think in larger organisations this would be a problem (don't want people 'accidentally' changing things in the wrong sprint ;-). My main concern is that I cannot assign the same person into multiple 'teams'.... So, I guess that's three questions: 1. Any plan to allow a person to be on multiple teams with a different hour-rating for each team? 2. Any plan to separate TRAC / AGILO permissions such that you have different rights depending on Sprint (or more easily, Team)? 3. Any plans to separate out the sprint administration from the trac- administration, so that a non trac_admin can create and administer sprints? Or is this already in place, and I've just not played with it enough :) You might say 'just get them to log in using multiple logins, e.g. n...@team1 and n...@team2, but we're using SSPI authentication for our SVN / wiki etc, so I don't want to have to make the team start to remember multiple usernames / passwords on top of their NT ones. * New Projects / trac.ini editing Setting up Trac / Agilo projects is a bit of a bind when using the command-line. Is there any plan to provide an 'uber-admin' page, which allows for the control of projects (i.e. creation / deletion / editing of termplate pages etc?). I'd like my users to be able to set up new trac environments/ sprints themselves. Now, I know that this is probably a 'trac' question.. but it'd probably increase Agilo's "appeal" if there's less mucking about on the command line. Especially since to use this in a commercial environment, this means that anyone who's allowed to set up a new trac environment must be given /very/ permissive rights on the trac server, which most sysadmins might baulk at (e.g. RDP / local admin!). Also, the trac admin page doesn't really cover everything that Agilo has (in the trac.ini file). Things like SVN path etc seem to be uneditable... (is this true?) So I guess this comes down to two questions again:- 1. Any plans to provide a web-based admin to allow for the creation / deletion of Trac / Agilo environments? 2. Any plans to extend the admin page to include some of the other trac.ini entries, such as SVN path and header logo? * SVN Branches Very often our sprints are coupled with SVN branches. Very occasionally a sprint might actually cover multiple SVN repositories (because we've segregated out our independent components). The way that Trac has a one environment to one SVN repository link is a little restrictive. With only a small amount of extra complexity for the user, a much more flexible environment would be something like:- 1. The creator specifies a set of comma-separated Repositories when creating an environment, (not just one). 2. when creating a sprint, selects 0, 1 or many of the repositories, and enters a path within those as the pertinent 'root' folders of the sprint (e.g. /Branch/Sprint1). 3. When the "Browse Source" button is clicked, instead of dumping at a repo, a set of 'Available Repositories' appears (with their current head versions, etc), (much like the 'Available Projects' page at the front of Trac). 4. Another button be on the LHS "Browse Source(s) for Sprint:" [ Sprint 1 ] [View]. This would then take you to a filtered version of the page in 3, which showed the current revisions from each of the pertinent repositories / top-level branches. When clicking on these, they take you to a specific location within the repo. I think this would make the agilo/trac/svn linkage rather spiffing :) I do realise that some of this is probably better targetted at the 'trac' people, but I'm not savvy enough to see where the border lies :) Thank you for taking the time to read this far. I hope that this is useful. All the best, Nick --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Agilo for Scrum" group. This group is moderated by agile42 GmbH http://www.agile42.com and is focused in supporting Agilo for Scrum users. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/agilo?hl=en -~----------~----~----~----~------~----~------~--~---
