| Reporter |
John Crim (jcrim)
|
|---|---|
| Created | Jan 11, 2013 4:21:06 AM |
| Updated | Aug 20, 2013 10:19:33 PM |
| Priority | Normal |
| Type | Bug |
| State | Open |
| Assignee | Vadim Gurov (vgurov) |
| Subsystem | Agile Board |
| Fix versions | Backlog |
| Fixed in builds | No Fixed in build |
| Affected versions | No Affected versions |
| Browser | Any Browser |
| OS | Any OS |
| Verified in build | Not verified |
| Verified by | Nobody |
| Reviewed by | No reviewed by |
| Severity | Routine |
Per http://confluence.jetbrains.net/display/YTD4/Creating+a+Sprint , a sprint is a version in a project.
I'm interested in using YouTrack at my company, but this structure will prevent us from using it to manage our scrum process. 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 across within a single team sprint across all projects.
From a product standpoint, if I were designing YouTrack, I'd define a sprint 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 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 YouTrack, I'm very interested. Otherwise, please let me know if + when this approach to scheduling and working is supported.
I'm interested in using YouTrack at my company, but this structure will prevent us from using it to manage our scrum process. 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 across within a single team sprint across all projects.
From a product standpoint, if I were designing YouTrack, I'd define a sprint 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 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 YouTrack, I'm very interested. Otherwise, please let me know if + when this approach to scheduling and working is supported.