I occasionally get questions from clients who are using Agile and Scrum
frameworks for software development.
Techniques and tools aside, it is often questions about the fundamentals of
collaboration that seem to be getting in the team's way.
Hi Gordon:
One thing you enlightened me on was the peril of raising defects instead of
recognizing and reporting that a story is simply not actually done by pulling
the story back to in progress.
I'm having trouble convincing some team mates of the simplicity of that
concept. Oddly enough, logic like "If it's not done, don't report it as done"
does not seem to be winning the argument for me. (Logic is overrated, I
find.)
Thanks and best regards,
Tom C.
Unlike most of the rest of the universe, the concept of a piece of software
being "done" is always going to be the crossing of an imaginary line with
invisible endpoints. Most... (more)