Scribd
Upload
25 views22 pages

Lecture 04 - Agile Models - Scrum

Uploaded by

reyankhan54975
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
25 views22 pages

Lecture 04 - Agile Models - Scrum

Uploaded by

reyankhan54975
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 22

SE 2101 Software

Engineering

Chapter 3
Software Engineering, A Practitioner’s Approach, Pressman R.
S.& Maxim B. R., 7th Edition, McGraw-Hill, 2015.

1
Recap

 Agile Models
 XP Programming
Today’s Agenda

 Agile Models
 Scrum
Agile process models

 Extreme Programming (XP)


 Scrum
 Adaptive Software Development
 Dynamic System Development Method (DSDM)
 Crystal
 Feature Driven Development
 Agile Modeling (AM)
Scrum
 Emphasizes use of a set of software patterns
 Backlog
 Sprints
 Scrum meetings
Scrum
Scrum’s Roles
 The Product Owner
 The Scrum Master
 The Team
 Everyone else is not part of Scrum
Scrum’s Practices
 The Sprint Planning Meeting
 The Sprint
 The Sprint Review Meeting
 The Daily Scrum
 Everything else is not part of Scrum
The Sprint Planning Meeting
 Product Owner describes highest priority features to the Team.

 Team decides what the can commit to delivering in the Sprint.


The Sprint Review Meeting
 Time boxed to one hour of prep and four hours of meeting.
 Team demonstrates product increment to product owner’s satisfaction.
 Informality is encouraged. PowerPoint is discouraged.
The Daily Scrum
 Time boxed to fifteen minutes!
 The Team and the Scrum Master only.
 What have you accomplished since yesterday?
 Are your Sprint Backlog estimates accurate?
 What are you working on today?
 Is there anything blocking you?
The Sprint Retrospective
 Time boxed to three hours.
 Team, Scrum Master, and (optionally) Product Owner review the last
Sprint
 What went well?
 What can be improved?
 Actionable items are presented to the Product Owner for prioritization
as non-functional requirements.
Scrum’s Artefacts
 The Product Backlog
 The Sprint Backlog
 The Sprint Burndown Chart
 The Product Increment
 Everything else is not part of Scrum
The Product Backlog
The Sprint Backlog
The Sprint Burndown Chart
The Product Increment
 Delivers measurable value
 “Potentially Shippable”: the process can be halted after every Sprint
and there will be some value, some ROI
 Must be a product, no matter how incomplete
Some reasons to avoid
Scrum
 Your current software development produces acceptable results
 Your project cannot be decomposed into good, increment-able requirements
(“big ball of mud”)
 Your engineering practices embrace heavy, up-front design, the construction of
baroque frameworks, and throw-it-over-the-wall attitudes towards QA.
 Nobody can agree on ‘done-ness’
 Your management practices embrace ‘do it now and forget what I told you to do
yesterday’.
Scrum and Agile principles

 Customer involvement
 Incremental development
 People not process
 Embrace change
 Maintain simplicity
Scrum Vs XP
Scrum XP

Sprint Increments

Product Backlog User Stories

30 days 15 days

Daily scrum Pair programming


Summary

 Agility principles
 XP
 Scrum
 When to choose which model?
The End.

You might also like