Throughout the Getting Predictable blog, I talk about alignment. For many, the word “alignment” is a bit vague. Does it mean we agree? Does it mean I actively support you? If I don’t actively support you, but I don’t block you either, am I “aligned” with you? As it relates to projects, doesn’t alignment simply […]
Scope Creep. Sometimes it’s politically motivated. Sometimes it’s intentional. Sometimes it’s a misunderstanding. But it’s always painful.
It’s not often, but I believe we have all experienced the meeting that goes too smoothly. There’s anywhere from four to eight people, trapped with each other for an hour, around our favorite conference table.
Recently, we’ve introduced Commitment Based Estimation to a couple of our software teams. Typically, this helps a team provide highly-accurate estimates. These teams go on to deliver successfully by meeting these estimates.
In this blog I usually write about best practices that help set teams up for success. That is really what Getting Predictable is about.
Recently a consultant asked me if I encourage teams to do a project postmortem or retrospective once a project is done. The goal is to review what worked well and what didn’t.
Facilitating a panel is not so different than facilitating a requirements session.