One of the problems I see in projects is that there is not a sufficient definition of done. For agile teams, it’s not clear what done means for a timebox. For non-agile projects, the team may not agree on what done means for a milestone or for a release. For an agile team, do you […]
I’ve been busy the last few weeks (as you can tell by the paucity of posts :-). I’ve been working with project managers, Scrum Masters, and technical leads who have been thrust into the role of Scrum Master. Here are some examples of the problems these nice folks have had: “When I want to use
Several years ago, a colleague emailed me, asking how to keep sponsors involved. My colleague was using company-mandated phase-gate lifecycle with long project durations (18-24 months). I’d recommended providing a project dashboard and showing the sponsor progress. My colleague was stumped–the dashboard wasn’t particularly helpful until they were in the testing phase and it
In the immortal words of Dilbert/Scott Adams, “Agile programming doesn’t just mean doing more work with fewer people.” See today’s cartoon.
I’m at the 13ICSQ conference this week. One person (at least) was confused about agile processes: Conference attendee: “Agile processes are a license to hack!!!!!!!” JR: “No. Every agile team I’ve seen is highly disciplined. No hacking there. I’m sure there are people who say they’re performing agile development, and they’re just hacking, but truly