Some time ago I encouraged you to put your sprint backlog on the wall because of transparency and efficiency. Today I want to ask you to go even further and put your backlog on the wall (or whiteboard if you want). The whole product backlog? Yes - the whole product backlog - with each story that belongs to it.
And the great question is: But why? Let's see.
Pokazywanie postów oznaczonych etykietą product backlog. Pokaż wszystkie posty
Pokazywanie postów oznaczonych etykietą product backlog. Pokaż wszystkie posty
wtorek, 22 lipca 2014
wtorek, 21 maja 2013
Use your wall
In my current project we're using Jira to track the progress in project, to storing backlog items and so on. And after few years I need to admit that is really great tool, at least is perfect for ours needs.
Ok, it's almost perfect - it's completely unrelated with motivation in our team.
Why I think so? Because we're looking at it only when one of us needs to do something there. Team members moves issues from one column to the other, product owner sorts backlog whenever there is a need, we are adding notes, attachments or we made clarification for the issues and many other things, but all of those are activities related with project life cycle. Not with motivation.
Ok, it's almost perfect - it's completely unrelated with motivation in our team.
Why I think so? Because we're looking at it only when one of us needs to do something there. Team members moves issues from one column to the other, product owner sorts backlog whenever there is a need, we are adding notes, attachments or we made clarification for the issues and many other things, but all of those are activities related with project life cycle. Not with motivation.
Subskrybuj:
Komentarze (Atom)