geek academy batch 2 : intro to scrum
DESCRIPTION
TRANSCRIPT
SCRUM
1st WEEKSAT, NOVEMBER 23, 2013 – SUN, NOVEMBER 24,
2013GEEK ACADEMY Batch 2 2013
THIS CLASS
GETNOT
CLASS AGENDA
SCRUM OVERVIEWS
ROLESACTIVITIES
ARTIFACTS
PLANNING & ESTIMATION DEFINITION OF DONE
SPRINTBACKLOG
RETROSPECTIVE REVIEWSREFINEMENT
DAILY
SCRUMGEEK ACADEMY 2013
WHAT IS SCRUM ?
TIME
SPRINT
1 2 3 4 5 6
SCRUM OVERVIEWS
SCRUM OVERVIEWS
• THREE(3) SCRUM ROLES
• SIX(6) ACTIVITYS
• THREE(3) ARTIFACTS
SCRUM ROLES
Team
PRODUCT OWNER
• Should have a vision for the product.
• Defines the features of the product, decides on release date and content.
• Is responsible for the profitability of the product (ROI).
• Prioritizes features according to market value.
• Can change features and priority every sprint.
Team
SCRUM TEAM• Self-organizing;
• Cross-functional with no roles;
• Seven plus or minus two;
• Responsible for committing to work;
• Authority to do whatever is needed to meet commitment;
• Open, collocated space;
• Resolution of conflicts;
• Working agreements:
SCRUM MASTER• Removing the barriers between
development and the customer so the customer directly drives development;
• Teaching the product owner how to maximize ROI and meet their objectives through Scrum;
• Improving the lives of the development team by facilitating creativity and empowerment;
• Improving the productivity of the development team in any way possible; and, Improving the engineering practices and tools so each increment of functionality is potentially shippable.
SCRUM ACTIVITIES
PRODUCT BACKLOG : PRIORITY
FEATURE LOW PRIORITY
HIGH PRIORITY
PRODUCT BACKLOG : SIZE
LOW PRIORITY
HIGH PRIORITY
LOW PRIORITY& COARSE GRAIN
HIGH PRIORITY& FINE GRAIN
PRODUCT BACKLOG : ESTIMATE
LOW PRIORITY& COARSE GRAIN
HIGH PRIORITY& FINE GRAIN
1 3 2
2 8 5
SCRUM ACTIVITIES
SCRUM ACTIVITIES
SPRINT PLANNING PART I
SPRINT PLANNING PART II
DAILY SCRUM
BACKLOG REFINEMENT
SPRINT REVIEWSSPRINT RETROSPECTIVE
SPRINT PLANNING PART I & II
Sprint planning part 1
- Clarification on backlog item
- Tentatively select backlog items for sprint
Sprint planning part 2
- Hours based sprint planning
- Commit to the items, get back to PO
SHIPPABLE PRODUCT
?
SHIPPABLE PRODUCT
REQUIREMENT GATHERING
ANALYSTARCHITECTURE
DESIGN
UNIT TEST FUNCTIONAL TEST
IMPLEMENTED
REFACTORED
BLA BLA BLA REVIEWSMIGRATE SCRIPT
DOCUMENT
DEFINITION OF DONE
• Over time Done should include everything needed before deployment.
• Team together with product owner defines what “done” means.
• Examples of “done” -> Design, coding, unit testing, integrated ,Static analysis, refactored, Acceptance tested, deployable
• Not done backlog items should not be reviewed
DAILY SCRUM
• Three questions;
• What have you done since last meeting?
• What will you do before next meeting?
• What is Impediments ?
• Daily 15 minute status meeting;
• No discussion. Discussion after the daily Scrum
BACKLOG REFINEMENT
ENOUGH FOR 1-2 Sprints
LOW PRIORITY& COARSE GRAIN
HIGH PRIORITY& FINE GRAIN
1 3 2
2 8 5
1 3 2
2 5
2 5
2 5
2
2
2
2
2
2
SCRUM ARTIFACTS
Product Backlog Sprint Backlog Burndown
SCRUM BOARD
SPRINT REVIEWS
• Team presents “done” functionality and discusses with PO and stakeholders.
• Team cannot present functionality that is not “done”
• Get Product’s Feedback
• Product Owner prioritizes backlog accordingly
SPRINT RETROSPECTIVE
• Goal : Reflect and create actions for improvements
• Question
• What went well during last sprint
• What could be improved during last spint
• Improvements needing action will be added to next sprint
SPRINT RETROSPECTIVE
SCRUM ?
SCRUM OF SCRUM
http://www.scrumalliance.org/articles/46-advice-on-conducting-the-scrum-of-scrums-meeting
REFERENCES
o http://www.scrumprimer.org/anime
o http://frank.vanpuffelen.net/2010/09/color-coding-your-scrum-board.html
o http://www.boost.co.nz/blog/wp-content/uploads/2012/04/scrum-board2-e1334284189527.jpg
o The Scrum Primer v 2.0o http://www.infoq.com/minibooks/Scrum_Primer
Q&A
GEEK ACADEMY 2013
GEEK ACADEMY 2013