El Bruno

Hi,

yesterday talking with Avanade Ana on some project management, was an example that I usually say that it helps me to see if that has been designed to level planning is what is really making the team.

Regardless of whether work with tasks associated to a User Story of a Master Story List or tasks associated to a Use Case or a formal requirement of CMMI, the next question leaves notice that something is not working as it should:

What task I relate this CheckIn?

When working with Visual Studio and Team Foundation Server, one of the policies of CheckIn always active is which obliges each change of code that gets into the Source Control repository to be associated with one or more WorkItems. In this way we can have an initial traceability between the history of the source code and the tasks carried out by the team.

But when a developer doesn’t find a work item (Task or Bug) to relate a change, this tells us that we are working on something not planned. As we are agile, this isn’t a problem, because change is welcome, but it is a good time to get a couple of questions.

For example, ask if the content of the work we have planned for this iteration is correct. If someone can’t find a WI to associate, that means that well not working on something for the iteration, or to perform part of the work included in the iteration, we have to make unplanned tasks that may affect the final result of the same.

The basis of this premise is that apart from the original planning, the task that we are actually carried out, is the team, so if the team is doing something that is not defined anywhere, because… we have moved long

Greetings @ Here

The Bruno