Can a sprint span multiple projects?
I'm interested in using Gemini at my company, but we can't use it if sprints are treated as a project version - which is the case for many issue trackers that I've encountered. We have a team of people that work on multiple projects during each sprint. A sprint is a unit of time, during which each person can schedule and work on tasks during that time. We'd like to do moving items from the backlog, scrum board manipulation, time-tracking, burn-downs, and burn-ups within a single team sprint across all projects.
From a product standpoint, it would be ideal if a sprint is defined as a period of time for a group of people to get work done across any projects. That way multiple teams within a company could have their own sprints (possibly on different schedules) and separate burn-downs. Whether a project version is completed during a sprint is a decision made by people working on the sprint.
If this approach is feasible with Gemeni, I'm very interested. Otherwise, please let me know if + when this approach to scheduling and working is supported.
john.crim
· 1 |
|
Monday, January 14, 2013, 7:28:39 AM |