Many large organizations find it hard to deliver valuable Results to their Stakeholders. Their size makes it difficult to adapt to the fact that both the realities of delivery and the Stakeholder’s minds change in unexpected ways. That’s when systematic scaling of Scrum becomes critical to an organization’s success.Read Full Article →

Stakeholders are the reason we develop Product in the first place. Stakeholders are those people that have needs, wants, and desires. (In an IT setting, these may be referred to as desirements, a processing task or type of output that is desired, but not absolutely necessary.) As a Scrum Team, we are trying to identify work that satisfies our Stakeholders.Read Full Article →

So, let me talk about the easy stuff first. One of the best things that can happen to a Scrum Team is that it finishes its work early in a Sprint. It amazes me that Teams are confused about what to do, but they are. So here goes… If the Team finishes early, it seems to me there are two choices:Read Full Article →

Let’s face it, you’re really busy. So, the idea of taking time out of your crazy work day to get a certification may make you ponder, “Is this really worth it? Will it help me do my job better?” If this is what comes to your mind about becoming a Certified ScrumMaster (CSM), don’t feel bad. Critically walking through the “why should I do this?” argument is time well spent. So is getting your ScrumMaster Certification. Here are some important reasons why.Read Full Article →

Once upon a time, there was a company. A large, multi-layered organization ordered with the task of developing and launching new software. And not just any software. Complex software, unlike anything the organization or the public at large had seen, or used, before. The new software carried with it a set-in-stone launch deadline. The pressure was immediately on to go live. And not just go live in one small testing site; rather, to roll out the software and go live everywhere at the same time...Read Full Article →