Skip to content

Posts from the ‘Scrum’ Category


Scrum Methods: Planning for Value

Steve Jobs was obsessed with providing the best user experience to his customers.  Because, above all else, that is what they valued most.  He was the grand master at delivering value to his customers.  Not necessarily in terms of dollars, but in terms of what they wanted.  And while technology helped get him there, his focus was always on exceeding the expectations of the user. Read more »


The Absence of Commitment

Back in 2011, Ken Schwaber and Jeff Sutherland, the established authorities on Scrum standards, replaced the term commitment with forecast within the official Scrum Guide. While this may seem like a minor, irrelevant change, the implications are indeed significant. Read more »


Scrum Values: Predictability

As Scrum becomes ever-so-popular among software development teams, some people may actually wonder why. Certainly increased productivity and improved quality are on the list, but predictability is a huge benefit that is often over-looked. Whether your product development is driven by schedule, scope, or budget, being able to accurately and consistently predict when a set of features will be done is often critical to a successful product launch. And considering how often Waterfall projects miss their mark, it should be no surprise why Scrum has been so successful (when done correctly). Read more »


A Dozen Ways to Fail at Scrum

Scrum provides a process framework to help realize the benefits of Agile principles. The value of Scrum has been demonstrated many times, on numerous projects, throughout various industries. It is a fairly simple and straightforward set of practices and guidelines that will (usually) result in greater adaptability to change, improved productivity, high quality products, and happier customers (over waterfall methods). Read more »


What makes a good ScrumMaster?

The role of a Scrum Master requires skills in a variety of disciplines. But for starters, good soft skills are a must. A good Scrum Master must be able to communicate effectively and be able to relate well to all team members. He/She must be able to influence others and constantly sell the value Scrum to team members and other stakeholders. Everyone has an opinion on how Agile principles should be applied and Read more »


Scrum Values: Visibility

One value of Scrum that is often overlooked is visibility, which actually enables critical Scrum practices. Visibility is realized by communicating project status to all stakeholders, which includes the status of individual and team commitments, impediments, progress, along with other project metrics and indicators. Scrum is based on empirical process methods, which demands process transparency to enable inspection and adaption at all stages of development. Read more »


Scrum Methods: Defining the User Role

Software development teams new to Scrum often struggle with writing user stories.  And the biggest challenge is usually incurred right from the beginning; defining the user role.  While this can be challenging in any type of development, it is especially difficult in systems development.  Defining the user roles for application software is fairly straightforward, but user roles for systems software is often more complicated. Read more »


Scrum Methods: User Story Authorship

Scrum is not just a change in methodology; it is a change in culture. It is not simply a practice of iterative development; it embraces the principles defined in the Agile Manifesto and places the customer at the center of product development. For organizations that adhere to Agile practices, their highest priority is to satisfy the customer through early and continuous delivery of valuable software.1 Read more »