Remerciez-le!

Remerciez @Admin pour avoir partagé cet document gratuitement, de la manière la plus simple, en partageant sur les réseaux sociaux.

Scrum guide SCRUM GUIDE SCRUM GUIDE This guide explains how to use Scrum to build products In doing so it will describe how the framework and its artifacts time-boxes roles and rules work together Scrum does not include techniques and processes for buildi

SCRUM GUIDE SCRUM GUIDE This guide explains how to use Scrum to build products In doing so it will describe how the framework and its artifacts time-boxes roles and rules work together Scrum does not include techniques and processes for building products however it will point out the e ?cacy and aws of these techniques and processes Scrum is a framework for developing complex products and systems It is grounded in empirical process control theory Scrum employs an iterative incremental approach to optimize predictability and control risk Within each iteration Scrum employs self-organizing crossfunctional Teams to optimize exibility and productivity The heart of Scrum is a Sprint A Sprint is one iteration of a month or less that is of consistent length throughout a development e ?ort All Sprints use the same Scrum framework and all Sprints end with an increment of the end product that is potentially releasable The increment is a complete slice or piece of the ?nished product or system that is developed by the end of an iteration or Sprint One Sprint starts immediately after the prior Sprint ends Scrum employs time-boxes to create regularity The time-boxes within Scrum are the Sprint Planning Meeting the Sprint the Daily Scrum the Sprint Review and the Sprint Retrospective Scrum employs self-organizing cross-functional Scrum Teams to do the work Each Scrum Team has three roles where accountability and responsibility lie The ScrumMaster is responsible for ensuring the process is understood and followed The Product Owner is responsible for maximizing the value of the work done The Team does the work The Team consists of developers with all the skills to turn the Product Owner ? s requests into the potentially shippable increment each Sprint The Team is usually seven plus or minus two members The Scrum framework consists of these time-boxes Teams with roles and artifacts glued together by Rules One rule is that only the people committed to turning the Product Backlog into an increment namely the Team talks during a Daily Scrum TIP If there are fewer people on the team the team may reach skill constraints during parts of the Sprint If there are more members the team may be overwhelmed with too many people to collaborate and to keep informed In our experience however teams do range outside this recommended size of seven plus or minus two ??Agile Software Development with Scrum ? Ken Schwaber Microsoft Press SCRUM GUIDE Rules bind the roles time-boxes and meetings These rules are implicit throughout this document as the roles time-boxes and meetings are described When there are suggested approaches or TIPS on how to proceed these are in separate TIP boxes Scrum has been used to develop complex products since the early s Many best practices have been uncovered for developing complex products within the Scrum framework In tandem with this guide the books ??Agile Project Management with ? Scrum ? Schwaber Microsoft Press and ??The Enterprise and Scrum ? Schwaber Microsoft Press contain many tips about managing