Learn how handoffs, individual task ownership, and status-report daily scrums keep Scrum teams from collaborating—and what to change next sprint.
Learn how handoffs, individual task ownership, and status-report daily scrums keep Scrum teams from collaborating—and what to change next sprint.
In context
- Topic: Proyectos, PMO y Riesgos — Gestión de proyectos, oficinas de proyecto y riesgo del portafolio.
- Source: Mountain Goat Software
Continue reading at the original source →
Excerpt published automatically by the site radar. The full text belongs to its publisher and is linked above.
Why it matters
Projects rarely fail on the day they are declared failed. They fail months earlier, in a meeting where somebody saw the problem coming and calculated it was not in their interest to say so. Everything else — the slipping schedule, the stretching budget — is the visible consequence of that silence.
I read these things looking for where the risk sat before it became an incident. It was almost always already written in some register nobody reviewed, with an assigned owner who never found out they were one. A risk identified and not managed is worse than one never identified: it creates the false sense that there is control.
What usually goes wrong
What I see fail most is the absent sponsor. They sign the kick-off, appear in the photo, and do not come back until there is a problem. Without somebody with real authority clearing obstacles every fortnight, the project manager ends up negotiating as an equal with areas that do not report to them, and loses.
What to watch
- How it was estimated and how close the same organisation's previous estimates turned out to be.
- Who the sponsor is and how often they actually show up — not on the org chart, in the calendar.
- Whether the status report shows any red projects: an all-green portfolio is a portfolio without information.
How I read this entry
I would use it to review how the organisation estimates. If historical estimates were systematically out by half and nobody adjusted the method, no project will land well: you are planning with a ruler that measures short and blaming the team for not reaching the mark.
This entry is an excerpt from the original source, selected by the site radar. The commentary above is the site's own and does not belong to the cited publisher.
Living through this in your own team?
Open the chat and tell me how you're handling it. I'm interested in comparing notes.
