Skip to main content

What is Scrum?

Scrum is an agile approach to product development that is centered around brief, informal stand-up meetings.

The term "scrum" originated in the game of rugby. A rugby scrum is a way of resuming a game that has paused due to an accidental foul or the ball having gone out of play. Opposing players engage head-to-head and compete for possession of the ball, which is thrown into the fray.

A "media scrum" is an impromptu press conference in which the media gather around a political figure and bombard her with questions.

Thus "scrum" has come to refer more generally to a short, informal gathering.

In the Scrum approach to product development, scrums are frequent (often daily) stand-up meetings in which each member of the product team states his immediate goal and any risks or obstacles he is facing. The scrums typically start at precisely the same time every day and are often time-boxed to 15-20 minutes.

Other Scrum practices include:
  • Iterations ("sprints") with a maximum duration of thirty days.
  • No changes during a sprint to the planned set of deliverables within it.
  • Demo to external stakeholders at the end of each iteration.
  • On-going measurement of progress and re-estimation of remaining scope.
Roles in Scrum include:
  • Product owner is the voice of the customer and determines and prioritizes what will go in the product.
  • Scrum master facilitates the planning, sprint, and meeting processes. The emphasis is on removing obstacles rather than dictating how individuals achieve goals.
  • Team is composed of the designers, developers, and testers that build the product.
  • Users sometimes attend meetings and give feedback on demos.
  • Stakeholders are not users but may be buyers or vendors.
  • Managers set up the environment for the team.
Artifacts in Scrum include:
  • Product backlog is a prioritized list of requirements or features planned for the product.
  • Sprint backlog is a prioritized, detailed list of requirements, features, or tasks planned for a sprint.
  • Burn down chart depicts the number of backlog items (or the estimated task hours) remaining in a sprint or for the product as a whole.
Executives and product managers are concerned mostly with product backlogs and high-level visibility into the team's progress.

Comments

Popular posts from this blog

Why Spreadsheets Suck for Prioritizing

The Goal As a company executive, you want confidence that your product team (which includes all the people, from all departments, responsible for product success) has a sound basis for deciding which items are on the product roadmap. You also want confidence the team is prioritizing the items in a smart way. What Should We Prioritize? The items the team prioritizes could be features, user stories, epics, market problems, themes, or experiments. Melissa Perri  makes an excellent case for a " problem roadmap ", and, in general, I recommend focusing on the latter types of items. However, the topic of what types of items you should prioritize - and in what situations - is interesting and important but beyond the scope of this blog entry. A Sad but Familiar Story If there is significant controversy about priorities, then almost inevitably, a product manager or other member of the team decides to put together The Spreadsheet. I've done it. Some of the mos

Interaction Design: the Neglected Skill

Your product development organization has a big, gaping hole in it. (Be prepared to feel defensive as you continue reading.) One of the most important roles in product development is the role of interaction designer. An interaction designer designs how the users will interact with the product and conceptualize the tasks they perform. He decides whether, for example, the user interface will be command driven, object oriented (clicking on objects then specifying what to do with them), or wizard based. The interaction designer decides the individual steps in the use cases. Every company has one or more people that play the interaction designer role. Usually, those people have little or no expertise in interaction design. Sadly, they typically don't even realize how unqualified they are. Let's see who typically plays the role at companies. Engineer . An engineer is an expert on building what is designed. Yes, an engineer may know how to design the internal structure of the hardware

Is Customer Development Pseudoscience?

The “Science” of Lean Startup Lean startup practitioners embrace the scientific method, seeking the "truth" about what business model and strategy will lead to product success. We do so by: Formulating hypotheses Crafting and running experiments to test them Learning from the experiments Iteratively feeding our learnings back into revised hypotheses Sounds pretty scientific, at least in spirit, doesn't it? Yet this process actually neglects a key ingredient in the scientists' mode of operation. To identify what’s missing, let’s examine “customer development”. Customer Development Steve Blank is one of the pioneers of the lean startup movement. He introduced into the lean startup lexicon the term “customer development”. Customer development consists of sessions and interactions with customers to test hypotheses. For example, a product manager might interview a prospect, asking if she agrees with the product manager’s hypotheses about the problem