We got talking about this at lunch today. Unfortunately I have not done an agile project that didn't suffer from this... from Michael Feathers IterationSlop:
"The worst form of iteration slop is what I call trailer-hitched QA. When your team does trailer-hitched QA the developers work until the last possible moment within the iteration and when the iteration ends, they hand off to the QA team. The QA team gets the "final" build and they work with it for a while, running more automated and manual tests. Often this takes close to the length of an iteration. At the end of the process, QA gives their approval and the development team looks back at them, in the distance, and says 'Great! We really did finish that work!'"
How common is this? Post me some numbers if you have a chance, % projects that you have been on where trailer-hitched QA was standard. At the moment I am 100% for two agile projects -- both were trailer-hitched (one successfully completed, the other looks good at the moment, although the QA is well behind).
Subscribe to:
Post Comments (Atom)
-
I went looking for “just a prompt” and accidentally built a tiny AI coworker. In Cursor, using GPT-5.1 / GPT-5.1-codex, I asked for a stand... -
Yesterday, ClubHub was mostly an idea and an architecture doc. Today, it has: A working dashboard showing real member and event counts ...
-
Imagine kicking off a new feature and having a team of AI colleagues rally to design, code, test, and review it—while you watch the progres...
1 comment:
How about, team finishes 75% of the iterations for release and then QA starts becoming interested in taking a look.
:-(
Changing an organization is -hard-.
Post a Comment