The Team did a fantastic demo. Everything worked flawlessly, even that mocked up user interface that clearly showed that hidden feature. The audience seemed to understand the features shown, and approve of them—there even was a round of applause after the demo. The developers walk back to the team room with big smiles on their faces.
“Do we have a retrospective now?”
“Why have a retrospective? Everything went right, didn’t it? No need to discuss what went wrong when everything went right!”
Right?
Wrong.
A long time ago in my company, when we were still making software for other companies, we did a project that turned into a disaster. Deadlines were not met, the software had lots of bugs, the customer was unhappy, and we had ...
Get Scrum for Teams now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
