Assigning tasks to users and creating individual burndowns

I need two enhancements:-

  1. Resource burn down chart - A graph against resources and total hours of work assigned to him/her.
  2. Rights to assign task to anyone - I am not sure, if this feature is there in kunagi. I need rights to assign task to any team member.

Statement from Kunagi Team

The features proposed here slightly oppose Scrum methodology and therefore do not meet central design concepts of Kunagi.

  1. Does only make sense in the light of 2.
  2. Opposes the self-organizing nature of Scrum teams. Furthermore, Team Members need to commit to doing something (which requires some interaction by the Team Member in question). Being assigned tasks contradicts this need.

Additionally, it is not clear what Scrum role should be given the possibility to assign Tasks to others.


Issue is closed.


Thu, Jan 13, 2011, 12:51 by Witek (SM,T)

I am very sceptical about this. This is, because it contradicts the basic idea of Scrum. Every team member should pick his next task when he is ready to do it.

Perhaps I did not understand your request, could you please give more explanations:

  1. Who do you want to have the right to assign tasks to others? The Product Owner, the Scrum Master or a Team member?
  2. Do you want this feature for the purpose to assign tasks on the beginning of the Sprint? If this is the case, could you explain, why?

Thu, Oct 13, 2011, 23:45 by Tad Mannes

Freedom is a good thing. Its too restrictive. We have a meeting, with one person with a laptop connected to a projector. It would be nice if we could assign tasks during the meeting without have every person sign on.

How about a little love :-)

Mon, Oct 17, 2011, 10:50 by Witek (SM,T)

Of course freedom is a good thing. Therefore Kunagi protects the Team from old school project managers and control freaks who often would like to assign tasks to the team and take away their freedom of self organization.

Another point is, that it is a good practice to pick tasks on demand. A Team member should claim the task just before he starts to work on it. That way there is always work for everybody, until all stories are completed. What is the purpose of assigning tasks up front?

Tue, Nov 8, 2011, 23:42 by Ken 'classmaker' Ritchie

Agree. It is a "pull" method when resources claim tasks just in time. Assignments, on the other hand, are a form of "push." Pull is more efficient and adaptive! Also, when people "sign up" for a task they usually have a stronger internal or emotional commitment to completing that task well.

Assignment may be a symptom of a lack of trust in the people or the agile process itself, by controlling resources in a misdirected attempt to control the outcome. That tends to be less effective and less adaptive. I know an executive in a large financial enterprise who has already demonstrated that their agile process-driven projects are more "in control" than their own best-practices plan-driven projects (meaning "in control" in the 6-sigma, statistical process control.)

So keep applying those Scrum practices, avoid misdirection, and Press ON!

Ken 'classmaker' Ritchie (Atlanta, Georgia, USA)
CSM, PMP, 6SigmaGB, CCP-Programming/Management.

PS, Interesting push-pull reading at ...enjoy!

Post a comment