Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Scrum In Action
Mona Shokrof
Agile Coach and Trainer
Scrum Master, ITWORX Education
What is Scrum
2
Agile framework for completing
complex projects
Agile Values
Working Software over documentation
Individuals and interactions over process and tools
Responding to change ...
Principles behind Agile
Our highest priority is to satisfy the customer

through early and continuous delivery

of valuabl...
Principles behind Agile
The most efficient and effective method of 

conveying information to and within a development 

te...
Principles behind Agile
Agile processes promote sustainable development. 

The sponsors, developers, and users should be a...
Scrum been used by
• Microsoft
• Yahoo
• Google
• Apple
• Qualcomm
• Time Warner
7
• IBM
• Philips
• Siemens
• Nokia
• BBC
Scrum Usage
8
Scrum Origin
9
Characteristics
• Progress made through sprints
• Self organizing teams
• Inspection and adaption
• Team works as a unit ,...
Sprint
• One to four weeks long - constant duration
• No requirement change during the sprint
• Work on all stages until w...
Scrum Roles
• Team
• Scrum Master
• Product Owner
12
Scrum Team
• 5-9 persons
• Cross-functional
• Co-located
• Self Organizing
13
Product Owner
• Represents the Business side
• Makes scope vs. schedule decisions
• Prioritize the features
• Works with t...
Scrum Master
• Servant/Leader
• Focus on Agile values and principles
• Removes impediments
• Coach the team to be self org...
Scrum Artifacts
• Product Backlog
• Sprint Backlog
• Shippable Product Increment
16
Product Backlog
17
• Responsibility of the Product Owner

• Prioritized by the Product Owner
Product Backlog
• Features
• Defects
• Enhancements
• Experiments
Set of items that represent the components of the product
Product Backlog
Upcoming
sprints (2-3)
Current release
Future releases
Sprint Backlog
• Set of tasks to work on Product backlog item
• Responsibility of the team
• Task state updated daily
• Em...
Sprint Backlog
21
Product increment
• Working part of the product
• Potentially shippable
• Approved by the product owner
22
Definition of "Done"
• Team agreement
• What “Done” means ??
• Product Backlog item
• Task
23
Scrum Events
• Sprint Planning
• Daily Scrum
• Sprint Review
• Sprint Retrospective
24
Sprint Planning
• All team attends the meeting
• Choose highest priority product backlog items to work
upon
• Break down i...
Sprint Planning
• Typically 2 - 4 hours for 2 weeks sprint
• High level Technical design may be considered
26
Sprint Planning
• Sprint Goal : goal statement of the sprint
• Sprint Backlog
27
Output
Daily Scrum
• aka daily standup
• maximum 15 mins
• Defined time and place everyday
• Team alignment
• Not status for Scrum...
Daily Scrum
• What did you do yesterday?
• What will you do today?
• Is there anything blocking/delaying you?
29
Sprint Review
• Demo for potentially shippable product increment
• Product owner/team are attending
• Other stakeholders m...
Sprint Review
• Feedback gathered and put in Product Backlog
• Could include highlights of the done/remaining
product back...
Sprint Retrospective
• Team and Scrum master
• Product owner may attend
• Purpose is to inspect and adapt the process
• Al...
Sprint Retrospective
33
Scrum Brief
34
Additional Artifacts
• User Stories
• Burn down charts
• Burn up charts
35
User Stories
As a (user) , I want to (feature)
so I can (reason-benefit)
Burn down chart
Burn up chart
Additional Events
• Release planning
• Backlog refinement
39
Release planning
40
Workshop
41
The Greeting Card Application
References
• Scrum Guide

http://www.scrumguides.org/scrum-guide.html
• Mike Cohn Blog

http://mountaingoatsoftware.com/
•...
About Mona
Agile Coach and Trainer
www.shokrof.com
mona@shokrof.com
LinkedIn : Mona Shokrof
Agile ‫بالعربي‬
Upcoming SlideShare
Loading in …5
×

Scrum in action

1,170 views

Published on

This is the presentation for Scrum in Action in Mobile Weekend 2016 held in ITI in 15 April 2016

Published in: Leadership & Management

Scrum in action

  1. 1. Scrum In Action Mona Shokrof Agile Coach and Trainer Scrum Master, ITWORX Education
  2. 2. What is Scrum 2 Agile framework for completing complex projects
  3. 3. Agile Values Working Software over documentation Individuals and interactions over process and tools Responding to change over following a plan Customer Collaboration over Contract Negotiation 3
  4. 4. Principles behind Agile Our highest priority is to satisfy the customer
 through early and continuous delivery
 of valuable software. Working software is the primary measure of progress. Deliver working software frequently, from a 
 couple of weeks to a couple of months, with a 
 preference to the shorter timescale. Welcome changing requirements, even late in 
 development. Agile processes harness change for 
 the customer's competitive advantage. 4
  5. 5. Principles behind Agile The most efficient and effective method of 
 conveying information to and within a development 
 team is face-to-face conversation. Business people and developers must work 
 together daily throughout the project. Simplicity--the art of maximizing the amount 
 of work not done--is essential. Build projects around motivated individuals. 
 Give them the environment and support they need, 
 and trust them to get the job done. 5
  6. 6. Principles behind Agile Agile processes promote sustainable development. 
 The sponsors, developers, and users should be able 
 to maintain a constant pace indefinitely. Continuous attention to technical excellence 
 and good design enhances agility. The best architectures, requirements, and designs 
 emerge from self-organizing teams. At regular intervals, the team reflects on how 
 to become more effective, then tunes and adjusts 
 its behavior accordingly. 6
  7. 7. Scrum been used by • Microsoft • Yahoo • Google • Apple • Qualcomm • Time Warner 7 • IBM • Philips • Siemens • Nokia • BBC
  8. 8. Scrum Usage 8
  9. 9. Scrum Origin 9
  10. 10. Characteristics • Progress made through sprints • Self organizing teams • Inspection and adaption • Team works as a unit , doing all work in iterations 10
  11. 11. Sprint • One to four weeks long - constant duration • No requirement change during the sprint • Work on all stages until work done during the sprint 11
  12. 12. Scrum Roles • Team • Scrum Master • Product Owner 12
  13. 13. Scrum Team • 5-9 persons • Cross-functional • Co-located • Self Organizing 13
  14. 14. Product Owner • Represents the Business side • Makes scope vs. schedule decisions • Prioritize the features • Works with the team closely 14
  15. 15. Scrum Master • Servant/Leader • Focus on Agile values and principles • Removes impediments • Coach the team to be self organizing • Protects the team from external interference 15
  16. 16. Scrum Artifacts • Product Backlog • Sprint Backlog • Shippable Product Increment 16
  17. 17. Product Backlog 17 • Responsibility of the Product Owner
 • Prioritized by the Product Owner
  18. 18. Product Backlog • Features • Defects • Enhancements • Experiments Set of items that represent the components of the product
  19. 19. Product Backlog Upcoming sprints (2-3) Current release Future releases
  20. 20. Sprint Backlog • Set of tasks to work on Product backlog item • Responsibility of the team • Task state updated daily • Emerging tasks are added while working 20
  21. 21. Sprint Backlog 21
  22. 22. Product increment • Working part of the product • Potentially shippable • Approved by the product owner 22
  23. 23. Definition of "Done" • Team agreement • What “Done” means ?? • Product Backlog item • Task 23
  24. 24. Scrum Events • Sprint Planning • Daily Scrum • Sprint Review • Sprint Retrospective 24
  25. 25. Sprint Planning • All team attends the meeting • Choose highest priority product backlog items to work upon • Break down items into tasks • Team estimate tasks • Team commits to finish these items 25
  26. 26. Sprint Planning • Typically 2 - 4 hours for 2 weeks sprint • High level Technical design may be considered 26
  27. 27. Sprint Planning • Sprint Goal : goal statement of the sprint • Sprint Backlog 27 Output
  28. 28. Daily Scrum • aka daily standup • maximum 15 mins • Defined time and place everyday • Team alignment • Not status for Scrum Master 28
  29. 29. Daily Scrum • What did you do yesterday? • What will you do today? • Is there anything blocking/delaying you? 29
  30. 30. Sprint Review • Demo for potentially shippable product increment • Product owner/team are attending • Other stakeholders may attend • Purpose is to inspect and adapt the product 30
  31. 31. Sprint Review • Feedback gathered and put in Product Backlog • Could include highlights of the done/remaining product backlog items • Typically 30 - 60 mins 31
  32. 32. Sprint Retrospective • Team and Scrum master • Product owner may attend • Purpose is to inspect and adapt the process • All team encouraged to speak • Typically 1-2 hours 32
  33. 33. Sprint Retrospective 33
  34. 34. Scrum Brief 34
  35. 35. Additional Artifacts • User Stories • Burn down charts • Burn up charts 35
  36. 36. User Stories As a (user) , I want to (feature) so I can (reason-benefit)
  37. 37. Burn down chart
  38. 38. Burn up chart
  39. 39. Additional Events • Release planning • Backlog refinement 39
  40. 40. Release planning 40
  41. 41. Workshop 41 The Greeting Card Application
  42. 42. References • Scrum Guide
 http://www.scrumguides.org/scrum-guide.html • Mike Cohn Blog
 http://mountaingoatsoftware.com/ • Agile Manifesto
 http://agilemanifesto.org/ 42
  43. 43. About Mona Agile Coach and Trainer www.shokrof.com mona@shokrof.com LinkedIn : Mona Shokrof Agile ‫بالعربي‬

×