The Scrum approach to agile software development marks a dramatic departure from waterfall management. Scrum and other agile methods were inspired by its shortcomings. Scrum emphasizes collaboration, functioning software, team self management, and the flexibility to adapt to emerging business realities.

October 2008

Scrum User Stories

Submitted by admin on Fri, 10/24/2008 - 15:02

In Scrum, work is typically expressed in the Product Backlog as user stories. A team may write its user stories in a number of ways as long as they are written from the perspective of the end user. Team members are encouraged to think of their work from the perspective of who will use it (hence “user” story). A team can express a story as a noun (i.e.

Scrum Impediments

Submitted by admin on Fri, 10/24/2008 - 14:49

In Scrum, an impediment is anything that keeps a team from being productive. An impediment can literally be anything, from a team member who is slacking to a freezing team room. But if it’s blocking the team from performing to the best of its abilities, it’s an impediment. To help maximize efficiency, the role of the ScrumMaster is completely dedicated to resolving impediments.

Scrum Sprint

Submitted by admin on Fri, 10/10/2008 - 13:11
In the Scrum method of Agile software development, work is confined to a regular, repeatable work cycle, known as a sprint or iteration. Scrum sprints used to be 30 days long, but today we advise one-week or two-week sprints. If a team has trouble doing a two-week sprint, we suggest trying a one-week sprint to see where the snags are. During each sprint, a team creates a potentially shippable product increment, no matter how basic that product is. Working within the boundaries of such an accelerated timeframe, the team would only be able to build the most essential functionality.

The Scrum Team Role

Submitted by admin on Fri, 10/10/2008 - 12:52

There are three roles in the Scrum method of software development: the Product Owner, the ScrumMaster, and the team. A Scrum team includes seven members, plus or minus two. Scrum teams are cross-functional, including the skills (but ideally not the job titles) of software engineers, architects, programmers, analysts, QA experts, testers, UI designers, etc.