15
-
Upload
samuel90 -
Category
Technology
-
view
797 -
download
1
description
Transcript of 15
![Page 1: 15](https://reader035.fdocuments.us/reader035/viewer/2022070302/5480b00fb4af9f98028b4690/html5/thumbnails/1.jpg)
Agile Method - Scrum
Present by Gloria Law
April 7, 2008
![Page 2: 15](https://reader035.fdocuments.us/reader035/viewer/2022070302/5480b00fb4af9f98028b4690/html5/thumbnails/2.jpg)
Agenda
• Introduction• Waterfall Life Cycle• Agile Method• Scrum• Sprints• Potentially Shippable
Product Increment• Product Owner• Product Backlog
• ScrumMaster• Daily Scrum Meeting• Scrum of Scrums• Sprint Planning• Release Planning• Sprint Review• Risk Management• System Representation• Advantage & Disadvantage
![Page 3: 15](https://reader035.fdocuments.us/reader035/viewer/2022070302/5480b00fb4af9f98028b4690/html5/thumbnails/3.jpg)
Introduction
• Need software management methods to decrease the cost
• 28% completed on time and budget
• 23% failed
• 49% challenged
• 72% not meeting original goals
![Page 4: 15](https://reader035.fdocuments.us/reader035/viewer/2022070302/5480b00fb4af9f98028b4690/html5/thumbnails/4.jpg)
Waterfall Life Cycle
X
![Page 5: 15](https://reader035.fdocuments.us/reader035/viewer/2022070302/5480b00fb4af9f98028b4690/html5/thumbnails/5.jpg)
Agile Method• Continuous attention to technical excellence and
good design • Self-organizing teams • Customer satisfaction by rapid, continuous
delivery of useful software • Working software is the principal measure of
progress • Delivered frequently
![Page 6: 15](https://reader035.fdocuments.us/reader035/viewer/2022070302/5480b00fb4af9f98028b4690/html5/thumbnails/6.jpg)
Agile Method (cont)
•Late changes in requirements •Close, daily cooperation between business people and developers •Face-to-face conversation is the best form of communication •Time is a fixed variable
![Page 7: 15](https://reader035.fdocuments.us/reader035/viewer/2022070302/5480b00fb4af9f98028b4690/html5/thumbnails/7.jpg)
Agile Manifesto “We are uncovering better ways of
developing software by doing it and helping others do it. Through this work we have come to value:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on the right, we value the items on the left more.”
![Page 8: 15](https://reader035.fdocuments.us/reader035/viewer/2022070302/5480b00fb4af9f98028b4690/html5/thumbnails/8.jpg)
Scrum
• Rugby• Eight individual• Move the ball down
the field• One Goal
![Page 9: 15](https://reader035.fdocuments.us/reader035/viewer/2022070302/5480b00fb4af9f98028b4690/html5/thumbnails/9.jpg)
Sprints
• Scrum project make progress in a series of Sprints
• Timeboxed Period (2 – 4 weeks)• During Sprint, team does:
– Analysis– Design– Code– Test
• Product is potentially releasable after every Sprint
![Page 10: 15](https://reader035.fdocuments.us/reader035/viewer/2022070302/5480b00fb4af9f98028b4690/html5/thumbnails/10.jpg)
Potentially Shippable Product Increment
• At the end of each Sprint, the Team must produce a potentially shippable product increment (commit by the Team)– High Quality– Tested– Complete– Done
![Page 11: 15](https://reader035.fdocuments.us/reader035/viewer/2022070302/5480b00fb4af9f98028b4690/html5/thumbnails/11.jpg)
Product Owner
• Represents (or is) the user or customer for the project
• Knowing what to build and in what sequence
• Defines goals for overall project
![Page 12: 15](https://reader035.fdocuments.us/reader035/viewer/2022070302/5480b00fb4af9f98028b4690/html5/thumbnails/12.jpg)
Product Backlog
• The requirements
• A dynamic list of all desired work on the project
• Prioritized by the Product Owner
• Reprioritized at the start of each Sprint
![Page 13: 15](https://reader035.fdocuments.us/reader035/viewer/2022070302/5480b00fb4af9f98028b4690/html5/thumbnails/13.jpg)
ScrumMaster
• Responsible for enforcing the values and practices of the framework and the Team
• Remove impediments• Educate outside groups about how the
Teams is working• Improve productivity in any way possible• Facilitate Team meetings• Servant Leader
![Page 14: 15](https://reader035.fdocuments.us/reader035/viewer/2022070302/5480b00fb4af9f98028b4690/html5/thumbnails/14.jpg)
Daily Scrum Meeting
• Tasks that is completed• Obstacles to complete specific
task• Plan to accomplish between now
and the next Scrum meeting
![Page 15: 15](https://reader035.fdocuments.us/reader035/viewer/2022070302/5480b00fb4af9f98028b4690/html5/thumbnails/15.jpg)
Scrum of Scrum
• Synchronize inter-team work– Issue list is up-to-date– Discuss impediments
![Page 16: 15](https://reader035.fdocuments.us/reader035/viewer/2022070302/5480b00fb4af9f98028b4690/html5/thumbnails/16.jpg)
Sprint Planning
• Happens on the 1st day of the Sprint
• Scrum Team takes the Sprint Goal and decides what Product Backlog are necessary
• Team self-organizes around how they’ll meet the Sprint Goal
• Sprint Backlog is created
![Page 17: 15](https://reader035.fdocuments.us/reader035/viewer/2022070302/5480b00fb4af9f98028b4690/html5/thumbnails/17.jpg)
Release Planning
• Several Days before Sprint Planning
• What will be built
• Identify top level priorities
• Select more than what the Team can likely do in one Sprint
![Page 18: 15](https://reader035.fdocuments.us/reader035/viewer/2022070302/5480b00fb4af9f98028b4690/html5/thumbnails/18.jpg)
Sprint Review
• Updates to Product Owner
• Plans for next Sprint– Change in Requirements
• Demonstration
![Page 19: 15](https://reader035.fdocuments.us/reader035/viewer/2022070302/5480b00fb4af9f98028b4690/html5/thumbnails/19.jpg)
Risk Management
• Risk is low• Continue testing• Problem is notified
during Daily Scrum Meeting
![Page 20: 15](https://reader035.fdocuments.us/reader035/viewer/2022070302/5480b00fb4af9f98028b4690/html5/thumbnails/20.jpg)
Release Planning Sprint PlanningIdeas
ProgrammingDaily Scrum
Sprint ReviewRelease ReviewWorking Code
Error Error
Product Backlog
Release Backlog
SprintBacklog
System Representation
![Page 21: 15](https://reader035.fdocuments.us/reader035/viewer/2022070302/5480b00fb4af9f98028b4690/html5/thumbnails/21.jpg)
Advantage & DisadvantageTraditional Management Agile Method
Prioritization + Support for long-term plans + No delays on important features+ Less important features might
scaled back or dropped
Planning + Able to see the overall project + Micro Planning+ Avoid Requirement cramming- Might be headed toward wrong
direction
Communication - Lack of communication with the customer and team members
+ Good internal communication+ Higher quality
Documentation + Highly emphasize+ Requires in every stage
- Knowledge is stored mentally- Code is the documentation
Risk Management - Might not find bugs until later stage
+ Continuous testing and communication can find issues rapidly
![Page 22: 15](https://reader035.fdocuments.us/reader035/viewer/2022070302/5480b00fb4af9f98028b4690/html5/thumbnails/22.jpg)
Work Breakdown Schedule
• Requirement Analysis – Proposal (February)
• Research – Review Case Study (March) – Paper Analysis (March-April)
• Writing the Paper
• Proof Read
![Page 23: 15](https://reader035.fdocuments.us/reader035/viewer/2022070302/5480b00fb4af9f98028b4690/html5/thumbnails/23.jpg)
Reference• Pressman, Roger S. “Software Engineering.” Software Engineering Project Management.
Pp. 30-47. IEEE. 2000.• Highsmith, Jim & Cockburn, Alistair. “Agile Software Development: The Business of
Innovation.” IEEE Computer. September 2001.• "Agile software development." Wikipedia, The Free Encyclopedia. 19 Apr 2007, 10:26 UTC.
Wikimedia Foundation, Inc. 19 Apr 2007 <http://en.wikipedia.org/w/index.php?title=Agile_software_development&oldid=124050398>.
• Rising, Linda & Janoff, Norman. “The Scrum Software Development Process for Small Teams.” IEEE Software. July/August 2000.
• Brooks, Frederick. The Mythical Man-Month: Essays on Software Engineering. MA: Addison-Wesley Professional 1975.
• Sutherland, Jeff. “Agile Development: Lessons Learned From the First Scrum.” Cutter Agile Project Management Advisory Service. Executive Update, Vol. 5, No. 20. October 2004.
• Anderson, David. Agile Management for Software Engineering. New Jersey: Prentice Hall, 2004.
• KarlstrÖm, Daniel & Runeson, Per. “Combining Agile Methods with Stage-Gate Project Managment.” IEEE Software. May/June 2005.
• “Agile Manifesto.” 19 Apr 2007, 10:26 UTC. <http://www.agilemanifesto.com>