Your SlideShare is downloading. ×
SCRUM an  agile  software development  methodology Prepared by: Bahaa Farouk 06/20/11 Copyright @ QualiFied Technology - J...
Agenda <ul><li>What’s Agile? </li></ul><ul><li>Introduction to SCRUM </li></ul><ul><li>SCRUM History & Background </li></u...
What’s Agile? <ul><li>Agility </li></ul><ul><ul><li>The ability to both  create  and respond to  change  in order to profi...
Introduction to SCRUM <ul><li>Scrum is an  Agile  Software Development Process.  </li></ul><ul><li>Scrum is not an acronym...
Introduction to SCRUM  (cont.) 06/20/11 Copyright @ QualiFied Technology - June 2011
Introduction to SCRUM  (cont.) <ul><li>Jeff Sutherland (a guru) states: </li></ul><ul><ul><li>“ Scrum assumes that the sys...
Historical Background <ul><li>Jeff Sutherland  </li></ul><ul><ul><li>first person to apply concepts of Scrum to software d...
Historical Background  (cont.) <ul><li>Jeff Sutherland and Ken Schwaber </li></ul><ul><ul><li>collaborated to define the p...
Overview <ul><li>Scrum is named after the game of Rugby in which a group is responsible for picking up the ball and moving...
Overview  (cont.) <ul><li>Scrum principles: </li></ul><ul><ul><li>Quality work: empowers everyone involved to be feel good...
Scrum Methodology 06/20/11 Copyright @ QualiFied Technology - June 2011
Components <ul><li>Roles: </li></ul><ul><ul><li>Scrum Master </li></ul></ul><ul><ul><li>Developer </li></ul></ul><ul><ul><...
Components  (cont.) <ul><li>Pregame </li></ul><ul><ul><li>Planning and Architecture: </li></ul></ul><ul><ul><li>Identify p...
Components  (cont.) <ul><li>Game </li></ul><ul><ul><li>Sprints lasts for 30 days </li></ul></ul><ul><ul><li>Analysis, Desi...
Components  (cont.) <ul><li>Values: </li></ul><ul><ul><li>Flexible deliverable </li></ul></ul><ul><ul><li>Flexible schedul...
Scrum Process Flow 06/20/11 Copyright @ QualiFied Technology - June 2011
Components  (cont.) 06/20/11 Copyright @ QualiFied Technology - June 2011
Components  (cont.) <ul><li>Product Backlog </li></ul>06/20/11 Copyright @ QualiFied Technology - June 2011
Components  (cont.) <ul><li>Sprint Backlog </li></ul>06/20/11 Copyright @ QualiFied Technology - June 2011
Components  (cont.) <ul><li>What Happens During a Sprint? </li></ul><ul><ul><li>Frequent, short Scrum  Meetings </li></ul>...
Components  (cont.) <ul><li>What’s a Scrum Meeting? </li></ul><ul><ul><li>Short  (15 - 30 min) frequent meetings, facilita...
Components  (cont.) <ul><li>At the End of a Sprint? </li></ul><ul><ul><li>Status  meeting with all stakeholders.  </li></u...
Process Comparison  06/20/11 Copyright @ QualiFied Technology - June 2011
Advantages <ul><li>Extreme value </li></ul><ul><li>Supports business value driven S/W Dev. </li></ul><ul><li>Control of ve...
Advantages  (cont.) <ul><li>Insists that the Client prioritize required functionality. </li></ul><ul><li>Ability to respon...
Disadvantages <ul><li>Scrum is not effective for small projects </li></ul><ul><li>Expensive to implement </li></ul><ul><li...
Usage Guidelines –  When to use <ul><li>requirements are  not clearly  defined.  </li></ul><ul><li>work is delivered in  i...
Usage Guidelines –  When to avoid <ul><li>there  isn’t a flexible  environment </li></ul><ul><li>corporate culture  isn’t ...
Conclusion <ul><li>Scrum offers: </li></ul><ul><ul><li>a high degree of flexibility </li></ul></ul><ul><ul><li>promises a ...
Recommendations <ul><li>We recommend Scrum as an  adaptive  and  flexible  development methodology that creates a  culture...
References <ul><li>Schwaber, Ken and Mike Beedle.  Agile software Development with Scrum.   Prentice Hall, 2002. </li></ul...
The End. <ul><li>Thank you </li></ul><ul><li>Questions or comments </li></ul>06/20/11 Copyright @ QualiFied Technology - J...
Upcoming SlideShare
Loading in...5
×

SCRUM Development Process

3,937

Published on

Published in: Technology, Business
0 Comments
6 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
3,937
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
0
Comments
0
Likes
6
Embeds 0
No embeds

No notes for slide

Transcript of "SCRUM Development Process"

  1. 1. SCRUM an agile software development methodology Prepared by: Bahaa Farouk 06/20/11 Copyright @ QualiFied Technology - June 2011
  2. 2. Agenda <ul><li>What’s Agile? </li></ul><ul><li>Introduction to SCRUM </li></ul><ul><li>SCRUM History & Background </li></ul><ul><li>Overview </li></ul><ul><li>Methodology </li></ul><ul><li>Components </li></ul><ul><li>Process Comparison </li></ul><ul><li>Advantages vs. Disadvantages </li></ul><ul><li>Usage Guidelines </li></ul><ul><li>Conclusion </li></ul><ul><li>Recommendation </li></ul>06/20/11 Copyright @ QualiFied Technology - June 2011
  3. 3. What’s Agile? <ul><li>Agility </li></ul><ul><ul><li>The ability to both create and respond to change in order to profit in a turbulent business environment </li></ul></ul><ul><li>Chaordic </li></ul><ul><ul><li>Exhibiting properties of both chaos and order </li></ul></ul><ul><ul><li>Things get done because people adapt, not because they forced follow processes </li></ul></ul><ul><li>Agile view is a chaordic view </li></ul><ul><ul><li>“ Balanced between chaos and order, depends on the falling at the edge of chaos.” </li></ul></ul>06/20/11 Copyright @ QualiFied Technology - June 2011
  4. 4. Introduction to SCRUM <ul><li>Scrum is an Agile Software Development Process. </li></ul><ul><li>Scrum is not an acronym </li></ul><ul><li>name taken from the sport of Rugby , where everyone in the team pack acts together to move the ball down the field </li></ul><ul><li>analogy to development is the team works together to successfully develop quality software </li></ul>06/20/11 Copyright @ QualiFied Technology - June 2011
  5. 5. Introduction to SCRUM (cont.) 06/20/11 Copyright @ QualiFied Technology - June 2011
  6. 6. Introduction to SCRUM (cont.) <ul><li>Jeff Sutherland (a guru) states: </li></ul><ul><ul><li>“ Scrum assumes that the systems development process is an unpredictable , complicated process that can only be roughly described as an overall progression .” </li></ul></ul><ul><ul><li>“ Scrum is an enhancement of the commonly used iterative/incremental object-oriented development cycle” </li></ul></ul>06/20/11 Copyright @ QualiFied Technology - June 2011
  7. 7. Historical Background <ul><li>Jeff Sutherland </li></ul><ul><ul><li>first person to apply concepts of Scrum to software development in 1993 </li></ul></ul><ul><li>A variation of Sashimi </li></ul><ul><ul><li>Japanese designed an all at once approach after their bad experiences with Waterfall </li></ul></ul><ul><li>The initial use of the word &quot;Scrum&quot; was used in 1987 to describe time-boxed, self-organizing, teams in product development </li></ul>06/20/11 Copyright @ QualiFied Technology - June 2011
  8. 8. Historical Background (cont.) <ul><li>Jeff Sutherland and Ken Schwaber </li></ul><ul><ul><li>collaborated to define the process through 1995 . In 1996 wrote the seminal article for Scrum Software Development process </li></ul></ul><ul><ul><li>jointly used and improved Scrum at a variety of software development organizations from 1996 until now </li></ul></ul><ul><ul><li>now promoting the idea of certifying ScrumMasters </li></ul></ul>06/20/11 Copyright @ QualiFied Technology - June 2011
  9. 9. Overview <ul><li>Scrum is named after the game of Rugby in which a group is responsible for picking up the ball and moving it forward. </li></ul><ul><li>It is an iterative, incremental process for developing any product or managing any work. </li></ul><ul><li>Scrum focuses on the entire organization for its implementation to be a success. </li></ul>06/20/11 Copyright @ QualiFied Technology - June 2011
  10. 10. Overview (cont.) <ul><li>Scrum principles: </li></ul><ul><ul><li>Quality work: empowers everyone involved to be feel good about their job. </li></ul></ul><ul><ul><li>Assume Simplicity: Scrum is a way to detect and cause removal of anything that gets in the way of development. </li></ul></ul><ul><ul><li>Embracing Change: Team based approach to development where requirements are rapidly changing . </li></ul></ul><ul><ul><li>Incremental changes: Scrum makes this possible using sprints where a team is able to deliver a product (iteration) deliverable within 30 days. </li></ul></ul>06/20/11 Copyright @ QualiFied Technology - June 2011
  11. 11. Scrum Methodology 06/20/11 Copyright @ QualiFied Technology - June 2011
  12. 12. Components <ul><li>Roles: </li></ul><ul><ul><li>Scrum Master </li></ul></ul><ul><ul><li>Developer </li></ul></ul><ul><ul><li>QA </li></ul></ul><ul><ul><li>Documentation member </li></ul></ul><ul><ul><li>Project manager </li></ul></ul>06/20/11 Copyright @ QualiFied Technology - June 2011
  13. 13. Components (cont.) <ul><li>Pregame </li></ul><ul><ul><li>Planning and Architecture: </li></ul></ul><ul><ul><li>Identify project </li></ul></ul><ul><ul><li>Prioritizing functional requirements </li></ul></ul><ul><ul><li>Identify resources available </li></ul></ul><ul><ul><li>Establishing the target environment </li></ul></ul>06/20/11 Copyright @ QualiFied Technology - June 2011
  14. 14. Components (cont.) <ul><li>Game </li></ul><ul><ul><li>Sprints lasts for 30 days </li></ul></ul><ul><ul><li>Analysis, Design, Develop </li></ul></ul><ul><ul><li>Testing (this happens throughout sprint) </li></ul></ul><ul><ul><li>Review </li></ul></ul><ul><ul><li>Adjust </li></ul></ul><ul><li>Postgame </li></ul><ul><ul><li>Closure (this includes delivering a functioning deliverable, sign-off, start next sprint. </li></ul></ul>06/20/11 Copyright @ QualiFied Technology - June 2011
  15. 15. Components (cont.) <ul><li>Values: </li></ul><ul><ul><li>Flexible deliverable </li></ul></ul><ul><ul><li>Flexible schedule </li></ul></ul><ul><ul><li>Small teams </li></ul></ul><ul><ul><li>Frequent reviews </li></ul></ul><ul><ul><li>Collaboration </li></ul></ul><ul><ul><li>Team Empowerment </li></ul></ul><ul><ul><li>Adaptability </li></ul></ul>06/20/11 Copyright @ QualiFied Technology - June 2011
  16. 16. Scrum Process Flow 06/20/11 Copyright @ QualiFied Technology - June 2011
  17. 17. Components (cont.) 06/20/11 Copyright @ QualiFied Technology - June 2011
  18. 18. Components (cont.) <ul><li>Product Backlog </li></ul>06/20/11 Copyright @ QualiFied Technology - June 2011
  19. 19. Components (cont.) <ul><li>Sprint Backlog </li></ul>06/20/11 Copyright @ QualiFied Technology - June 2011
  20. 20. Components (cont.) <ul><li>What Happens During a Sprint? </li></ul><ul><ul><li>Frequent, short Scrum Meetings </li></ul></ul><ul><ul><li>Each team produces a visible, usable increment </li></ul></ul><ul><ul><li>Each increment builds on prior increments </li></ul></ul><ul><ul><li>Clearly defined deliverables and responsibilities </li></ul></ul><ul><ul><li>Each team member buys into the assignment </li></ul></ul>06/20/11 Copyright @ QualiFied Technology - June 2011
  21. 21. Components (cont.) <ul><li>What’s a Scrum Meeting? </li></ul><ul><ul><li>Short (15 - 30 min) frequent meetings, facilitated by the ScrumMaster </li></ul></ul><ul><ul><li>All team members attend </li></ul></ul><ul><ul><li>One activity, ScrumMaster asks each attendee 3 questions: </li></ul></ul><ul><ul><li>What have you completed (relative to the Backlog) since the last Scrum meeting? </li></ul></ul><ul><ul><li>What got in your way of completing this work? </li></ul></ul><ul><ul><li>What will you do between now and the next Scrum meeting? </li></ul></ul>06/20/11 Copyright @ QualiFied Technology - June 2011
  22. 22. Components (cont.) <ul><li>At the End of a Sprint? </li></ul><ul><ul><li>Status meeting with all stakeholders. </li></ul></ul><ul><ul><li>Increments are delivered . </li></ul></ul><ul><ul><li>Surprises are reported. </li></ul></ul><ul><ul><li>ANYTHING can be changed, work can be added, eliminated, re-prioritized. </li></ul></ul><ul><ul><li>New estimates and team assignments are made for the next Sprint. </li></ul></ul>06/20/11 Copyright @ QualiFied Technology - June 2011
  23. 23. Process Comparison 06/20/11 Copyright @ QualiFied Technology - June 2011
  24. 24. Advantages <ul><li>Extreme value </li></ul><ul><li>Supports business value driven S/W Dev. </li></ul><ul><li>Control of very complex process of product development </li></ul><ul><li>Allows Developers to focus on delivering a usable functionality to the client </li></ul><ul><li>Generates productivity improvements </li></ul>06/20/11 Copyright @ QualiFied Technology - June 2011
  25. 25. Advantages (cont.) <ul><li>Insists that the Client prioritize required functionality. </li></ul><ul><li>Ability to respond to the unpredictable in any project requirements. </li></ul><ul><li>Flexibility </li></ul><ul><li>Knowledge sharing between Developers </li></ul><ul><li>Collective ownership </li></ul>06/20/11 Copyright @ QualiFied Technology - June 2011
  26. 26. Disadvantages <ul><li>Scrum is not effective for small projects </li></ul><ul><li>Expensive to implement </li></ul><ul><li>Training is required </li></ul>06/20/11 Copyright @ QualiFied Technology - June 2011
  27. 27. Usage Guidelines – When to use <ul><li>requirements are not clearly defined. </li></ul><ul><li>work is delivered in increments </li></ul><ul><li>work is measured and controlled </li></ul><ul><li>productivity is maximized by applying known technologies </li></ul><ul><li>organizations are willing to do anything and everything for a project to succeed </li></ul><ul><li>project is important and no one has confidence that any existing approach will work. </li></ul>06/20/11 Copyright @ QualiFied Technology - June 2011
  28. 28. Usage Guidelines – When to avoid <ul><li>there isn’t a flexible environment </li></ul><ul><li>corporate culture isn’t conducive to this of development environment </li></ul><ul><li>teams of developers are more than 10 . Six is ideal. </li></ul><ul><li>Cost is a major issue </li></ul><ul><li>No management support </li></ul><ul><li>No formal training available </li></ul>06/20/11 Copyright @ QualiFied Technology - June 2011
  29. 29. Conclusion <ul><li>Scrum offers: </li></ul><ul><ul><li>a high degree of flexibility </li></ul></ul><ul><ul><li>promises a high probability of success </li></ul></ul><ul><li>Scrum benefits: </li></ul><ul><ul><li>an anticipating culture </li></ul></ul><ul><ul><li>increases the sense of urgency </li></ul></ul><ul><ul><li>promotes the sharing of knowledge </li></ul></ul><ul><ul><li>encourages dense communications </li></ul></ul><ul><ul><li>facilitates honesty among developers </li></ul></ul>06/20/11 Copyright @ QualiFied Technology - June 2011
  30. 30. Recommendations <ul><li>We recommend Scrum as an adaptive and flexible development methodology that creates a culture of communication , knowledge sharing and teamwork within an organization. </li></ul>06/20/11 Copyright @ QualiFied Technology - June 2011
  31. 31. References <ul><li>Schwaber, Ken and Mike Beedle. Agile software Development with Scrum. Prentice Hall, 2002. </li></ul><ul><li>Sutherland, Jeff. “Inventing and Reinventing Scrum in five companies”, 21 September 2001 </li></ul><ul><li>www.controlchaos.com/scrumwp.htm </li></ul><ul><li>www.agilescrum.com/ </li></ul><ul><li>www.mountaingoatsoftare.com/scrum/ </li></ul><ul><li>www.objectmentor.com </li></ul><ul><li>agilealliance.com/articles/articles/InventingScrum.pdf </li></ul><ul><li>jeffsutherland.com/ </li></ul>06/20/11 Copyright @ QualiFied Technology - June 2011
  32. 32. The End. <ul><li>Thank you </li></ul><ul><li>Questions or comments </li></ul>06/20/11 Copyright @ QualiFied Technology - June 2011

×