Contents tagged with Agile Process Smells
-
Workshop at XP2006 on Agile Process Smells
Come to my Agile Process Anti-patterns Workshop on 6/21 10:45 - 3:30
-
Agile Process Smells: Solution Stories
One of the things that often happens when the product owner is technically savvy is that they start writing solution stories. That is they specify how something should be done technically rather than what should be done.
-
Agile Process Smells: Waiting on Specialists
A common smell that is often detected in teams trying to become more agile is more and more stories/backlog items incomplete at the end of the iteration. There are a couple of different reasons this might happen, but the one I'm interested in today can be detected by the claim "I finished my tasks". The clear implication is that "I got my stuff done, but someone else didn't".
-
Agile Process Smells: Introduction
I've been quiet recently, but busy. Last spring I moved from the consulting world back into "regular" employment where I manage a couple of product teams and internally consult on iterative software development and agile approaches. Since starting here I have run across a number of "Process Smells" that I encountered in my coaching/consulting days that are begging to be written down. So here I go.