Coach-Ram

What Is Agile Spillover? Spillover is when planned work (a product backlog item or story) is left unfinished at the end of the sprint or iteration and carries over to a subsequent sprint. Spillover in agile tends to occur for one of three reasons: Ambitious sprint goal, or Too much unplanned work, or Underestimating the effort required to complete the work. Occasional unfinished work is not a bad thing . In fact, it’s  normal and desirable to occasionally aim a little high in a sprint and  come up short. Too many spillovers, however, can reduce predictability, diminish creativity, harm morale, and threaten project timelines. Commitments Are Not Guarantees A sprint goal  is a commitment, not a guarantee. A commitment is a promise to try to achieve a goal. If forced to make a guarantee, a team will commit to less so that the guarantee is safe. Sometimes we do need to make guarantees, such as when a client or customer needs some capabili...

  The real art of leadership is not in the title you hold, but in the presence, you bring When Excellence Isn't Enough A few months ago, a senior leader whom I was coaching shared a concern which had been weighing him down. His performance reviews were exceptional. His team delivered results quarter after quarter. His peers respected him. Yet when the C-suite role opened up, he wasn't even in the conversation. "What am I missing?" he asked, his voice carrying equal parts frustration and genuine bewilderment. The answer wasn't in his spreadsheets or strategic plans. It wasn't about working harder or delivering more. The missing piece was something more subtle, more human, and yet more powerful than any metric could capture. It was his Executive Presence. The Executive Presence Paradox Here's what fascinates me about executive presence: everyone can sense it, yet few can define it. We know it when we see it. We feel it when someone walks into a...