Scrum Methodology - OOD [000377]

719 views

Published on

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

  • Be the first to like this

No Downloads
Views
Total views
719
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
17
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Scrum Methodology - OOD [000377]

  1. 1. Scrum Nor masharah Binti Husain (m20111000377)Nurhidayah Binti Abdul Rahman (M20111000376)
  2. 2. What is Scrum Scrum is an agile, lightweight process that can be used to manage and control software and product development using iterative, incremental practices Scrum is a software development methodology which consists of: - Management methodology - Enhancement methodology - Maintenance methodology
  3. 3. History Origin in Rugby  Getting an out of play ball into play Used to describe hyper-productive development
  4. 4. Why Scrum Software Development Lifecycle  Requirements Gathering and Analysis  Design  Implementation  Testing  Delivery Output of one stage serves as input for the succeeding stage Assumption  Each stage produces a predictable and defined output  Application of the process results in repeatable outputs
  5. 5. Scrum model
  6. 6.  Scrum Master (experienced engineer)  Responsible for removing impediments that stall the progress of Scrum Team Members  Interface between the management and the scrum team  Should be able to make quick decisions based on incomplete data
  7. 7.  Product Backlog  List of features under consideration  Business features and technology features Product Owner  Sole owner of the product backlog  Changes to the product backlog have to be approved by the product owner  Project Manager
  8. 8.  Scrum Team  Designers, Testers Sprint  Lasts for about 30 days  Implement the top priorities in the Project Backlog called as the Sprint Backlog  Sprint estimates updated as tasks are completed or new tasks crop up  Potentially shippable product increment
  9. 9.  Daily Scrum Meeting  Lasts about 15 minutes  What was achieved since the last meeting?  What are the impediments to your tasks?  What will you achieve before the next meeting? Sprint Review  Lasts for about 4 hours  Provides feedback to the management  Provides feedback to the next Sprint
  10. 10. Pros Good in team work Team learns and contributes through the process Team becomes autonomous and strives for excellence Rotation of leadership depending on the phase gives a distributed nature of project execution Reduced need for meetings, authorization and reporting Iterative model leading to a delivery every 30 days
  11. 11. Cons The basic premise that the team is committed to the project. If the team is not committed then process collapses The managements comfort level in delegation of tasks Emotional impact of failure on team members if the project fails

×