Teams continually refine the backlog to ensure it always contains some stories ready for implementation without significant risk or surprise. The team backlog will have been partially filled during PI Planning, and the teams will have established their PI Objectives. Most of the work is captured by user stories, but other work and activities (e.g., training, support) may also be included. The Team Backlog holds all the upcoming work needed to advance the solution. Scrum Iterations and events, including Iteration Planning, Review, and Retrospective, are briefly described in the following sections and in more detail in SAFe articles. The following sections provide an overview of this cycle. These events are often held at the same time and place to reduce overhead. Each event within this cycle provides an opportunity to inspect progress and make mid-course corrections. The SAFe Scrum Cycleįigure 1 illustrates the basic Scrum cycle using SAFe terminology (e.g. The self-management and cross-functional nature of the Scrum team-along with constant communication, constructive conflict, and dynamic interaction - creates a more enjoyable, fun, and productive work environment. Moreover, since Scrum teams have all the roles and skills needed to develop and deliver increments of value, they are designed to operate with the minimum possible constraints and dependencies with other teams. They then build, test and deploy the new functionality, and ensure built-in quality for each solution increment. They create and refine backlog items, expressed as Stories and acceptance criteria, defining and committing to iteration goals. Indeed, teams determine how they do their work and the scope they can commit to within the iteration time box. SAFe Principle #9, Decentralize decision-making, ensures alignment, and fosters subtle and minimal management direction for SAFe Scrum teams. Teams have the authority and autonomy to plan, execute and manage their work, make decisions within their scope, and adapt to changing conditions in the best way they see fit. DetailsĪgile Teams applying SAFe Scrum follow a regular cadence of events to achieve a common objective, delivering value to the enterprise and its customers. This article describes how Agile Teams apply SAFe Scrum. SAFe Scrum teams cooperate with other Agile Teams and ART stakeholders, building and deploying Solutions that benefit its Customers. However, all SAFe teams apply Built-in Quality techniques and other practices and activities not defined in Scrum. However, they are not limited to Scrum and may also use SAFe Team Kanban. Many teams use SAFe Scrum as their primary Agile Team process. SAFe Scrum teams use iterations, Kanban systems, and Scrum events to plan, execute, demonstrate, and retrospect their work. SAFe Scrum is an Agile method used by teams within an ART to deliver customer value in a short time box. Note: For more on SAFe Scrum, please read the additional Framework articles in the Scrum series, including Scrum Master/Team Coach, Iterations, Iteration Planning, Iteration Goals, Iteration Review, and Iteration Retrospective
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |