Create a highly effective and flexible work process. Using a practical team example, you'll learn why scrum works so well, the roles, rituals, artifacts and contracts in a scrum process, as well as the lifecycle of a story, adapting and transitioning to scrum.  

Scrum: Novice to Ninja

Preface

Introducing Scrum

Scrum is about how a team works together, so it's important to start with who the team is. Who are the people involved in a typical web or mobile development project, and what do they anticipate when they think of scrum? 

Meet the Team

Scrum Roles

The practice of working on a scrum team is organized into a series of rituals. The rituals mark key events in the process of carrying out the work of a sprint. It's the responsibility of the scrum master to host each of the rituals, and make sure that they focus on their objectives, and produce the desired results for the benefit of the entire team.

Scrum Rituals

Artifacts are the tools of scrum that allow teams to manage their scrum process. They help team members communicate about the work they're doing, and provide a record of what the team has agreed to do and what they have accomplished. You can point to the artifacts of a scrum team to show people while you're working on, what you've accomplished, and what you expect to be able to achieve. 

Scrum Artifacts

For the first half of this book we've talked about scrum in the abstract. We discussed what it is, and how it works. We've broken it down into its roles, rituals, and artifacts. But scrum isn't just about the details. Scrum is about the people.

The Scrum Contract

We've gone through scrum in detail, talking about the roles, rituals, and artifacts necessary to keep a scrum team running smoothly. We've discussed the attitudes of the team members, and the concerns people have coming into scrum. Now it's time to start looking at actual scrum in process.

The Lifecycle of a Story

In the last chapter we were introduced to the product owner's world, and taken through the process of developing and creating a story for the team. We saw how requirements were gathered, how the product backlog was built up, and how the expectations of internal and external clients, along with other interested parties, translated into clearly defined scrum stories for the team.

Working Through Scrum

For most of this book, we've been talking about the practicalities of scrum. Although the core definition of scrum is very versatile, supporting a wide range of applications, we've gone into a fairly opinionated and detailed explanation of the mechanics of scrum as it can be applied for web and mobile teams. (Although many of these principles and practices apply just as well to many other kinds of development work.)

Making Scrum Work for Your Web or Mobile Team

We've talked about the systems that make scrum work. We've discussed the approach that scrum takes to product development, and some of the rituals and artifacts that help the people taking on the roles of scrum to get their work done efficiently and effectively in a sustainable manner.

Community Questions