Practice: Avoid guesses, do what is expected to be done

Archive for 'practice'

Practice: Avoid guesses, do what is expected to be done

Posted on 11. Aug, 2010 by Guilherme Silveira.

Symptom: faced with two possibilities because the client did not let his desire clear enough, one path is chosen and it is often the wrong one. After delivering a new functionality, the client is the one who is going to test, approve and use it. Because it is difficult for developers to think as their [...]

Continue Reading

Practice: Favor finishing a story over starting a new one

Posted on 11. Jul, 2010 by Guilherme Silveira.

Symptom: Right before your development cycle finishes, which can be an iteration, a sprint or anything similar, all stories are marked as finished, giving a feeling of complete success. During the review meeting, when the Product Owner verifies what has been done, the number of approvals is extremely low: most of the stories are rejected. [...]