Just like it happens with any other methodologies, it is very difficult that pure 100% Scrum can be implemented at every company. In our case, Scrum will only be suitable for our project management if we make slight changes to the methodology. We need the ability to summarize the workload by user when planning a sprint, as our technicians are very specialized in certain skills. I mean that there are many tasks which cannot be swapped among developers.

So please do not be too purist and do not consider this issue as a real threat to Scrum either )

Good luck!

I can see how it could be used to break some Scrum of the goals that Scrum is looking to achieve. I guess I could see us using it mostly in the initial sprint planning meeting more then anything. When we go into the second half developers like to say I will take this, I will take that type thing. We assign the task by going into detail, but it would allow us to quickly toss tasks around.

-Jeremy

We will probably implement this, but this is really not a feature that we think is adding value to a Scrum process. Actually this is going against the goals of a Scrum team. If we are adding this feature it is just to support other management methodologies.

Cheers,

Yes please. This is exactly what I want as a new feature in GreenHopper! Drag and drop to assign tasks to specific people and a tally of how much time has been assigned so far as well as each user's particular capacity in this iteration/sprint (which will not be the same for each user). The Jira permission schemes already allow for "Assignable user" permission at a project level, and this can be set to a role or group of named users...so limiting the list of assignable users could just take advantage of this existing Jira permission scheme.

It would be very handy in the sprint planning meetings to have a "User" view of the planning board in addition to the "Versions" and "Components." I would say to simply it, the users listed would be the individuals on the project that could be assigned tasks.