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.

December 2008

Scrum Sprint Zero

Submitted by admin on Fri, 12/19/2008 - 12:05
In Scrum's definitions, every Sprint is an attempt to produce a potentially-shippable product increment, no matter how small. Every Sprint contains a combination of analysis, design, infrastructure, development, testing, and integration. Therefore, the common dysfunction called "Sprint Zero" is actually a contradiction in terms. Companies (and misinformed consultants and trainers) use this as a way to avoid changing waterfall habits.

Scrum with a Physical Taskboard

Submitted by admin on Tue, 12/09/2008 - 13:19

Agile management practices, which include Scrum, were originally conceived for use in small, collocated teams. Ideally, a team’s size falls between five and 10 members, all of whom are located in the same place. With no obstructions to communication, that arrangement facilitates ongoing collaboration and optimizes the team’s productivity. According to research, teams in such an environment prefer highly visible communication and coordination tools that reinforce collaboration.

Scrum Epics

Submitted by admin on Wed, 12/03/2008 - 09:02
In Scrum, the teams that complete the work spend time refining the top items in the Product Backlog. To minimize work in progress, user stories shouldn't consume more than one quarter of a Sprint. In most cases they can be made much smaller than that while still providing visible value to the customer. What happens when a story includes too many unknowns to tell just how big it is?