SCRUM -an agile software developmentmethodology                       Claudiu Pantea
Introduction to SCRUM   Scrum is an Agile Software Development    Process.   Scrum is not an acronym   name taken from ...
Introduction to SCRUM (cont.)   Jeff Sutherland (a guru) states:       “Scrum assumes that the systems development      ...
Description Overview   Scrum is named after the game of Rugby in    which a group is responsible for picking up    the ba...
Description Overview (cont.)   Scrum principles include:       Quality work: empowers everyone involved to be        fee...
Scrum Methodology
Description Components   Roles:       Scrum Master       Developer       QA       Documentation member       Project...
Description Components (cont.)   Processes:   Pregame     Planning and Architecture:        - Identify project       ...
Description Components (cont.)   Processes:   Game     Sprints:- lasts for 30 days      - Analysis, Design, Develop  ...
Description Components (cont.)   Values:       Flexible deliverable       Flexible schedule       Small teams       F...
Scrum Process Flow
Process Comparison
Description Advantages   Extreme value - reduces risk in ROI   Supports business value driven S/W Dev.   Control of ver...
Description Advantages (cont.)   Flexibility   Knowledge sharing between    Developers   Collective ownership   OO tec...
Description Disadvantages   Scrum is not effective for small projects   Expensive to implement   Training is required
Usage Guidelines – When to use   requirements are not clearly defined.   work is delivered in increments   work is meas...
Usage Guidelines – When to avoid   there isn’t a flexible environment   corporate culture isn’t conducive to this    of ...
Usage Guidelines – Implementation   Need for an extra member just in case an    active member is absent, the documentatio...
Scrum Success Factor
Scrum and CMM   CMM advocates Repeated Defined problems,    solutions, Developers and organizational    environment.   S...
Conclusion   Scrum offers:       a high degree of flexibility       promises a high probability of success   Scrum ben...
Bibliography   facweb.cti.depaul.edu
Upcoming SlideShare
Loading in …5
×

Scrum

175 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
175
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Scrum

  1. 1. SCRUM -an agile software developmentmethodology Claudiu Pantea
  2. 2. Introduction to SCRUM Scrum is an Agile Software Development Process. Scrum is not an acronym name taken from the sport of Rugby, where everyone in the team pack acts together to move the ball down the field analogy to development is the team works together to successfully develop quality software
  3. 3. Introduction to SCRUM (cont.) Jeff Sutherland (a guru) states:  “Scrum assumes that the systems development process is an unpredictable, complicated process that can only be roughly described as an overall progression.”  “Scrum is an enhancement of the commonly used iterative/incremental object-oriented development cycle”
  4. 4. Description Overview Scrum is named after the game of Rugby in which a group is responsible for picking up the ball and moving it forward. It is an iterative, incremental process for developing any product or managing any work. Scrum focuses on the entire organization for its implementation to be a success.
  5. 5. Description Overview (cont.) Scrum principles include:  Quality work: empowers everyone involved to be feel good about their job.  Assume Simplicity: Scrum is a way to detect and cause removal of anything that gets in the way of development.  Embracing Change: Team based approach to development where requirements are rapidly changing.  Incremental changes: Scrum makes this possible using sprints where a team is able to deliver a product (iteration) deliverable within 30 days.
  6. 6. Scrum Methodology
  7. 7. Description Components Roles:  Scrum Master  Developer  QA  Documentation member  Project manager
  8. 8. Description Components (cont.) Processes: Pregame Planning and Architecture: - Identify project - Prioritizing functional requirements - Identify resources available - Establishing the target environment
  9. 9. Description Components (cont.) Processes: Game Sprints:- lasts for 30 days - Analysis, Design, Develop - Testing (this happens throughout sprint) - Review - Adjust Postgame - Closure (this includes delivering a functioning deliverable, sign-off, start next sprint.
  10. 10. Description Components (cont.) Values:  Flexible deliverable  Flexible schedule  Small teams  Frequent reviews  Collaboration  Team Empowerment  Adaptability
  11. 11. Scrum Process Flow
  12. 12. Process Comparison
  13. 13. Description Advantages Extreme value - reduces risk in ROI Supports business value driven S/W Dev. Control of very complex process of product development Allows Developers to focus on delivering a usable functionality to the client Generates productivity improvements by implementing a framework that empowers teams and thrives on change Insists that the Client prioritize required functionality. Ability to respond to the unpredictable in any project requirements.
  14. 14. Description Advantages (cont.) Flexibility Knowledge sharing between Developers Collective ownership OO technology
  15. 15. Description Disadvantages Scrum is not effective for small projects Expensive to implement Training is required
  16. 16. Usage Guidelines – When to use requirements are not clearly defined. work is delivered in increments work is measured and controlled productivity is maximized by applying known technologies organizations are willing to do anything and everything for a project to succeed project is important and no one has confidence that any existing approach will work. control and management is Empirical
  17. 17. Usage Guidelines – When to avoid there isn’t a flexible environment corporate culture isn’t conducive to this of development environment teams of developers are more than 10. Six is ideal. Cost is a major issue No management support No formal training available
  18. 18. Usage Guidelines – Implementation Need for an extra member just in case an active member is absent, the documentation member substitutes Location: Although not impossible, its hard to implement Scrum when all team members are not in the same location Non-Supportive management Cost Lack of Customer Involvement Collective ownership Isolation of sprint team
  19. 19. Scrum Success Factor
  20. 20. Scrum and CMM CMM advocates Repeated Defined problems, solutions, Developers and organizational environment. Scrum says that this is not entirely possible because developers change from one project to another. Scrum assumes that the development process is always empirical and not defined. Scrum says uncertainties are impossible to measure, therefore, looks beyond the repeatable /defined approach
  21. 21. Conclusion Scrum offers:  a high degree of flexibility  promises a high probability of success Scrum benefits:  an anticipating culture  increases the sense of urgency  promotes the sharing of knowledge  encourages dense communications  facilitates honesty among developers
  22. 22. Bibliography facweb.cti.depaul.edu

×