Agile scrum introduction
-
Upload
ducquocvn -
Category
Technology
-
view
7.477 -
download
0
Transcript of Agile scrum introduction
Software development methodologies and Scrum
Agile Scrum Introduction
c Quc - [email protected]
( Twitter & SlideShare: ducquoc_vn )
Outline
Software development processes
Scrum benefits
Scrum roles
Scrum artifacts
Scrum daily stand-up
Scrum planning
Scrum review & retrospective
Q & A
Outline
Software development processes
Scrum benefits
Scrum roles
Scrum artifacts
Scrum daily stand-up
Scrum planning
Scrum review & retrospective
Q & A
Processes
http://1.bp.blogspot.com/_KijgS9tqTzs/THvKyoK1JlI/AAAAAAAAHgg/Xg5tZwropfM/s1600/ist2_6350519-agree-or-disagree-checkbox-choices.jpgTheory + Experiments + Practices Expericence (good practices & bad ones)Theory to utilize & promote good practices(PROCESS)
Processes - Software Development
C:\Users\Son Nguyen\Desktop\Evolution-1.jpgWaterfall
2003
UML
CMMi
Unified Process(RUP)
XP
Scrum
TL9000
Continuous Integration
TDD
2008
2007
2006
2004
2005
Lean
Kanban
Prince2
Processes - Waterfall
RequirementsRequirementsAnalysisArchitectureDesignDetailDesignImplementationTestingMaintenance
http://cdn.dipity.com/uploads/events/6419fb40d7f7c1ed8619bcdfd926b34f_1M.pngThe software factory
Processes - Waterfall works?
Processes - Waterfall with feedback
RequirementsRequirementsAnalysisArchitectureDesignDetailDesignImplementationTestingMaintenance
Processes - Iterative & Incremental
RequirementsQuick DesignImplementationEvaluation & UpdateRefine & ReworkFinal TestingRelease
Processes - Agile methodologies
People may think that this is the way Scrum manages requirement changes
Processes - Agile Scrum
C:\Users\Son Nguyen\Desktop\Evolution-1.jpgWaterfall
2003
UML
CMMi
Unified Process
XP
Scrum
TL9000
Continuous Integration
TDD
2008
2007
2006
2004
2005
Lean
Kanban
Agile
Prince2
Outline
Software development processes
Scrum benefits
Scrum roles
Scrum artifacts
Scrum daily stand-up
Scrum planning
Scrum review & retrospective
Q & A
Visibility
Business Value
Risk
Scrum benefits - project
Ability to Change
Ability to ChangeAdaptability goes down over time, regardless
Agile enables higher adaptability longer
With pluggable architectures encouraged by frequent deliveryWith encouraging the business decision makers to change their minds as they learn more about the market being sold to
In the beginning, if what is being created is the INFRASTRUCTURE, the investment needs to be protected from change. Adaptability goers down quickly as specs are frozen.
In agile, priorities may be changed and architectures may be refactored, resulting in systems that stay more adaptable longer
RiskThe risk of making the wrong thingIn plan-driven, customers may not see the product until is is ready for releaseAgile solicited feedback all along the way on features that are fully baked
The risk of missing an important feature
In plan driven, risk is mitigated by strict change control. In Agile, risk is mitigated by iterating to the correct answer. There is never more than a single iteration of work at rick at a time.
Scrum benefits - company
Use Scrum?Google - Facebook
Amazon - Twitter
IBM - DropBox
Salesforce - Intel
Yahoo - Nokia
Microsoft - GE
Time Warner
Lockheed Martin
Electronic Arts
rmcourse.jpg
Agile principles?
Scrum benefits - case study
2006: Sentinel project awarded to Lockheed Martin, 4 phases, $450m, 6 years.
2010, after four+ years, $421 spent and 1st phase and part of 2nd done. Mitre estimates another $351m and 6 years to complete.
FBI stops contract and brings in house.
Scrum studio in Hoover building basement, reduce staff from 400 to 40.
Project done in 1 year for $30m.
(source: www.justice.gov Inspector General reports)
Scrum benefits - simple
Certifications: CSM (course price: 1795 EUR for 2 days), PSM (500 $ for 120 minutes)
Outline
Software development processes
Scrum benefits
Scrum roles
Scrum artifacts
Scrum daily stand-up
Scrum planning
Scrum review & retrospective
Q & A
Scrum - overview
-- People in Team
-- Meetings
Easy to understand but extremely to implement.
Scrum roles - Pig & Chicken
Pigs: who are committed to building software regularly and frequently. (e.g. the Scrum team)
Chicken: who involved but not a pig. Usually they are informed of the progress. (e.g. stakeholders, managers)
060911-scrumtoon
Scrum roles - Scrum master
+ Scrum Master:
- Primary job is toremove impediments to the ability of the team to deliverthe sprint goal.
- Not necessarily the leader of the team (as the team is self-organizing) but acts as a buffer between the team and any distracting influences.
- Understands the benefits of the Scrum process to ensure that Scrum practices are used as intended.
Scrum roles - The Team
+ Product Owner:
- Customer representative
-Prioritizesproduct requirements
+ The Team:
- Includes others in Scrum team, who have the responsibility to deliver the product.
- Usually 5-9 people with cross-functional skills.
- Self-organizing
Outline
Software development processes
Scrum benefits
Scrum roles
Scrum artifacts
Scrum daily stand-up
Scrum planning
Scrum review & retrospective
Q & A
Scrum artifacts - overview
Taskboard, story, backlog, sprint, burndown, velocity, DoD, ...
But move people out if they cannot adapt
Scrum artifacts - taskboard
User stories (with tasks) visible ona physical board.
But move people out if they cannot adapt
Scrum artifacts - burndown chart
Burn chart is a graphical representation ofwork left to do versus time.
+ tracking the teams progress & predicting when tasks will be completed
+ how many story points the team can earn thevelocity. It helps predict delivery times based on number of story points.
But move people out if they cannot adapt
Scrum artifacts - Definition of Done
Scrum - meetings
(1) Daily Stand-Up
(2)
(3)
(4)
Easy to understand but extremely to implement.
Outline
Software development processes
Scrum benefits
Scrum roles
Scrum artifacts
Scrum daily stand-up
Scrum planning
Scrum review & retrospective
Q & A
Scrum - daily standup
Attendees: Anyone can attend, but only the pigs (Scrum team) may speak.
Scrum - daily meeting
Time: short (usually 5-15 minutes)!
It should start at the same time every working day (practically15-45 mins after start working time).
Venue: near the collaboration space,
i.e. near the Scrum taskboard enough to see the characters there.
Agenda: Everybody tells others about his tasks, in 3 points:
+ What has he done since the previous stand-up ?(DONEs yesterday)
+ What is he planning to do today ?(DOs today)
+ Is there any obstacle preventing him/her from doing what he/she has planned ?(any IMPEDIMENT)
Outline
Software development processes
Scrum benefits
Scrum roles
Scrum artifacts
Scrum daily stand-up
Scrum planning
Scrum review & retrospective
Q & A
Scrum - planning meeting
(time-boxed: 8 hours)
At the beginning of any Sprint (iteration 1-4 weeks), two half:
* BackLog selection (WHAT to do)
+ Some ofProduct Backlog(user stories) will be chosen to beSprint Backlog.
+Business value: is set by the Product Owner (client representative).
-> represents PRIORITY:how Important the story is to the client.
+Development effort: is set by the Team.
-> represents COMPLEXITY:how Hard to implement the story according to the average developers experience.
User Story: As a [USER] , I want [Feature X] so that [Y satisfied]
Scrum - planning tasks
* Task estimation (HOW to do)
+ each user story is broken down intoconcretetasks, and for each task every group votes a number as the estimated points for the task.
+ Planning poker cards: for displaying the voted/estimated points. One task point is implicitly considered1 man hour, for simplicity. (note: some may use 1 man day for 1 story point).
Scrum - planning estimation
* Task estimation (HOW to do)
+ If the points from the groups for the task are unanimous, or similarly (highest number is not higher than 1.5 the lowest number), the final estimated points is determined andmarked into the task.
+ If the points of the group are not similarly (see above), the groups of highest number and lowest number will, in turn,tell the team why they think their number is suitable. After that all groups will re-estimate that task again. (this step may be repeated several times until a compromise is reached)
+ Total estimated points for a story should not exceed a predefined certain amount (20-40 man hours), otherwise the story may either be labeled asepicto be broken into smaller stories so as to not violate that limitation.
Outline
Software development processes
Scrum benefits
Scrum roles
Scrum artifacts
Scrum daily stand-up
Scrum planning
Scrum review & retrospective
Q & A
Scrum - review meeting
Review meeting (time-boxed: 3-4 hours)
+ internal showcase for whole team (including chickens)
+ demonstrate what is being done
+ direct feedback (incomplete features do not count)
Different thinking between management and engineering levels -> engineering is forced to live a lie
Scrum - retrospective meeting
Retrospective meeting (time-boxed: 2-3 hours)
(All Scrum team members raise their opinions about the Sprint, in 3 topics)
+ what we did well?
+ what did not go well?
+ which improvement should be applied right next Sprint?
Different thinking between management and engineering levels -> engineering is forced to live a lie
Questions & Answers
www.implementingscrum.com -- Cartoon -- December 18, 2006
http://www.emoticonswallpapers.com/images/thank-you/thank-you-glitter-pictures-010.jpghttp://en.wikipedia.org/wiki/Scrum_(development) http://allaboutagile.com/how-to-implement-scrum-in-10-easy-steps/http://www.scrumalliance.org/articles/119-unlearn-what-you-have-learnedhttp://ducquoc.wordpress.com/2011/03/30/agile-scrum-summary/. . .
Bonus - Scrum origins
Jeff Sutherland
Initial scrums at Easel Corp in 1993
IDX and 500+ people doing Scrum
Ken Schwaber
Scrum presented at OOPSLA 96 with Sutherland
ADM, Author of three books on Scrum
Mike Beedle
Scrum patterns in PLOPD4
Mike Cohn
Co-founded Scrum Alliance in 2002, initially within the Agile Alliance
Click to edit Master title style
Click to edit Master text styles
Second level
Third level
Fourth level
Fifth level
11/2/2013
6
11/2/2013
Click to edit Master text stylesSecond level
Third level
Fourth level
Fifth level
Click to edit Master title style
11/2/2013
6
11/2/2013
Click to edit Master text stylesSecond level
Third level
Fourth level
Fifth level
Click to edit Master title style
Click to edit Master text styles
Second level
Third level
Fourth level
Fifth level
11/2/2013
6
11/2/2013
Click to edit Master text stylesSecond level
Third level
Fourth level
Fifth level
Click to edit Master title style
Click to edit Master text styles
11/2/2013
6
11/2/2013
Click to edit Master text stylesSecond level
Third level
Fourth level
Fifth level
Click to edit Master title style
Click to edit Master text styles
Second level
Third level
Fourth level
Fifth level
Click to edit Master text styles
Second level
Third level
Fourth level
Fifth level
11/2/2013
6
11/2/2013
Click to edit Master text stylesSecond level
Third level
Fourth level
Fifth level
Click to edit Master title style
Click to edit Master text styles
Click to edit Master text styles
Second level
Third level
Fourth level
Fifth level
Click to edit Master text styles
Click to edit Master text styles
Second level
Third level
Fourth level
Fifth level
11/2/2013
6
11/2/2013
Click to edit Master text stylesSecond level
Third level
Fourth level
Fifth level
Click to edit Master title style
11/2/2013
6
11/2/2013
Click to edit Master text stylesSecond level
Third level
Fourth level
Fifth level
11/2/2013
6
11/2/2013
Click to edit Master text stylesSecond level
Third level
Fourth level
Fifth level
Click to edit Master title style
Click to edit Master text styles
Second level
Third level
Fourth level
Fifth level
Click to edit Master text styles
11/2/2013
6
11/2/2013
Click to edit Master text stylesSecond level
Third level
Fourth level
Fifth level
Click icon to add picture
Click to edit Master title style
Click to edit Master text styles
11/2/2013
6
11/2/2013
Click to edit Master text stylesSecond level
Third level
Fourth level
Fifth level
Click to edit Master title style
Click to edit Master text styles
Second level
Third level
Fourth level
Fifth level
11/2/2013
6
11/2/2013
Click to edit Master text stylesSecond level
Third level
Fourth level
Fifth level
Click to edit Master title style
Click to edit Master text styles
Second level
Third level
Fourth level
Fifth level
11/2/2013
6
11/2/2013
Click to edit Master text stylesSecond level
Third level
Fourth level
Fifth level
11/2/2013