A Case Study: The Journey of Systems, Inc. to CMMI Level 5�锯� 389Master to remove any impediment that is stopping the team from producing production-quality code. The impediment list is simply a set of tasks that the Scrum Master uses to track the impediments that need to be solved. �Task list: The task list is a list of tasks to turn product backlog into working product functionality. Tasks are estimated in hours, usually between 1 and 16. Tasks with more than 16 hours are broken down later. Team members sign up for tasks. Team members shouldn sign up for work prematurely (until actually starting that task). Estimated work remaining is updated daily; any team member can add, delete, or change the sprint backlog. Work for the sprint emerges; if teams believe that this has become too much, they can meet again with the product owner. �Product burndown chart: The product burndown chart gives an indication of how quickly the team is urning�through the work and delivering product backlog requirements. It is a useful tool for helping to plan when to release or when to remove requirements from a release if progress is not rapid enough.10.3.1.6 Scaling Scrum in Big ProjectsThe primary way of scaling Scrum to work with large teams is to coordinate a crum of Scrums.�With this approach, each Scrum team proceeds as normal but each team also contributes one person who attends Scrum of Scrum meetings to coordinate the work of multiple Scrum teams. These meetings are analogous to the daily Scrum meeting, but do not necessarily happen every day. In many organizations, having a Scrum of Scrums meeting two or three times a week is sufficient. Implementing Scrum is basically an organizational change. Implementing such a change in a large organization is a complex task that requires a field-tested methodology. The next subsection describes how EKD, a business process methodology, was integrated with Scrum at Systems, Inc.10.3.1.7 EKD, Patterns, and Scrum at Systems, Inc.In Chapter 2 we discussed the Enterprise Knowledge Development (EKD) methodology and how it can be used to describe processes. In this subsection we present how Scrum components were developed using the EKD description of patterns at Systems, Inc. After providing some examples, we will describe some basic elements of a Scrum patterns repository, and how it was populated, maintained, and used.10.3.1.7.1 Scrum, EKD, and Pattern DescriptionScrum patterns consist of Scrum activities, roles, and artifacts. Figure 10.3 lists key Scrum activities. After describing these elements at Systems, Inc. using EKD 2010 Taylor and Francis Group, LLC
