SlideShare utilise les cookies pour améliorer les fonctionnalités et les performances, et également pour vous montrer des publicités pertinentes. Si vous continuez à naviguer sur ce site, vous acceptez l’utilisation de cookies. Consultez nos Conditions d’utilisation et notre Politique de confidentialité.
SlideShare utilise les cookies pour améliorer les fonctionnalités et les performances, et également pour vous montrer des publicités pertinentes. Si vous continuez à naviguer sur ce site, vous acceptez l’utilisation de cookies. Consultez notre Politique de confidentialité et nos Conditions d’utilisation pour en savoir plus.
Scrum is the agile development process that allows teams to deliver usable software periodically throughout the life of the project, absorbing change and new requirements as the project proceeds.
Service Accounts detailsVPN Access for Remote Development3 ServersSQL Clustered InstanceNotify the HR and other departments for meetings--------------SQL Server 2012? Check the limitations for SQL 2008?Work PlaceBadge Pass
Agenda Agile and Scrum Business Problem Scrum Process Scrum Team Artifacts Product Backlog Sprint Backlog
Scrum and AgileAgile is the ability to create and response to change.Scrum is the most popular of the Agile methods.• Absorb Change• New Requirements• Deliver software periodically
Problem - Why Scrum?‣ Releases take too long‣ Stabilization takes too long‣ Changes are hard to make‣ Quality is falling
How does Scrum help to solve it?• Traditional development methodologies rely on documents to record and pass on knowledge from one specialist to the next.• Feedback cycles are too long or even nonexistent.• Scrum Provides Platform for people to work together effectively• Makes visible every problem.
Starting ScrumThe best thing you can do is hire an experienced coach. you need a Scrumteam. Product Owner, Scrum Master and team members.Then follow this sequence of steps:• 1. Train the Scrum Team• 2. Establish the vision• 3. Write user stories to form the product backlog• 4. Order the backlog items by business value• 5. Size the backlog items• 6. Re-order the backlog, as necessary, by additional factors• 7. Create the initial release plan• 8. Plan the first sprint• 9. Start sprinting
Scrum Methodology Release planning Product SprintVision Backlog Backlog Planning Deployment Development Sprints Build Unit Testing Shipable Quality Assurance Product
Sprint Mechanism User stories Acceptance criteria Sprint Business rules Planning Development Work Unit Testing Quality Assurance BuildRetrospec Deployments Work Daily tive Scrum Meeting Sprint Review Value to customer Code is complete Testing is complete Documentation is complete
Scrum Roles Product Owner Scrum Master The Team Other stakeholders• Manages Product • Responsible for • Architect and • Customers Backlog facilitating process develop code as per • Vendors the backlog items• Makes decisions on • Manage Sprint Scope communication between the Teams • Perform Unit Testing• Provides details on features including • Produce project • Perform Quality acceptance criteria reporting to keep Assurance track of project• Decides on release performance • Merge Code and date and content ensure deploy- • Assists Product ability• Accepts the Owner in leveraging deliverables Scrum & managing the product backlog
Meetings• Release Planning: the product owner, Scrum team meet to plan and schedule the releases for sprints• Sprint planning: the team meets with the product owner to choose a set of work to deliver during a sprint• Daily scrum: the team meets each day to share struggles and progress• Sprint reviews: the team demonstrates to the product owner what’s completed during the sprint• Sprint retrospectives: the team looks for ways to improve the product and the process.
Sprint Planning Meeting• It is a negotiation between the team and the product owner about what the team will do during the next sprint.• The product owner and all team members agree on a set of sprint goals, which is used to determine which product backlog items to commit from the uncommitted backlog to the sprint.• This portion of the sprint planning meeting is time-boxed to four hours.
Daily Scrum• The meeting starts precisely on time• All are welcome, but normally only the core roles speak• The meeting length is set (time boxed) to 15 minutes• The meeting should happen at the same location and same time every day• During the meeting, each team member answers three questions: – What have you done since yesterday? – What are you planning to do today? – Any impediments/stumbling blocks?• It is the role of the Scrum Master to facilitate resolution of these impediments, although the resolution should occur outside the Daily Scrum itself to keep it under 15 minutes.
Sprint Review Meeting• At the end of each sprint a sprint review meeting is held.• Scrum team shows what they have accomplished during the sprint. Typically this takes the form of a demo of the new features• Participants in the sprint review typically include the Product Owner, the Scrum team and the customers• Progress is assessed against the sprint goal determined during the Sprint planning meeting
Sprint Retrospective Meeting• The team and Scrum Master meet to discuss what went well and what to improve in the next sprint. The product owner does not attend this meeting.• The sprint retrospective should be time-boxed to three hours.
Artifacts• Product backlog: prioritized list of desired project outcomes/features• Sprint backlog: set of work from the product backlog that the team agrees to complete in a sprint, broken into tasks• Impediment backlog: List of issues that are preventing the team from progressing or improving• Burndown charts: at-a-glance look at the work remaining (can have two charts: one for the sprint and one for the overall project)• Velocity chart: To track the performance of each sprint