Upload
others
View
3
Download
0
Embed Size (px)
Citation preview
Tim Nolan, Collin County
2
Agile was coined in 2001 by software development leaders
Agile ManifestoAgile ManifestoIterative & IncrementalLight-weightPeople-based not plan-basedPopular Methodologies:
ScrumScrum, Extreme Programming (XP), Lean
3
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
4Source: AgileManifesto.org
1. Rapid delivery2. Welcome changes3. Working software is
delivered frequently4. Working software is the
principal measure of progress
5. Sustainable development6. Daily co-operation between
business and developers
7. Face-to-face conversation (Co-location)
8. Projects are built around motivated individuals, who should be trusted
9. Continuous attention to technical excellence and good design
10. Simplicity11. Self-organizing teams12. Regular adaptation
5Source: AgileManifesto.org
1.1. Rapid deliveryRapid delivery2.2. Welcome changesWelcome changes3. Working software is
delivered frequently4. Working software is the
principal measure of progress
5.5. Sustainable developmentSustainable development6.6. Daily coDaily co--operation between operation between
business and developersbusiness and developers
7.7. FaceFace--toto--face conversation (Coface conversation (Co--location)location)
8.8. Projects are built around Projects are built around motivated individuals, who motivated individuals, who should be trustedshould be trusted
9.9. Continuous attention to Continuous attention to technical excellence and good technical excellence and good designdesign
10.10. SimplicitySimplicity11. Self-organizing teams12.12. Regular adaptationRegular adaptation
6Source: AgileManifesto.org
7Source: IT-Xynergy.com
ROLESCEREMONIES
Product OwnerScrum MasterDevelopment Team
Sprint PlanningSprint ReviewSprint RetrospectiveDaily ScrumGrooming Session
8
ARTIFACTS
Product BacklogSprint BacklogSprint Burndown
9
10
What does this have to do with GIS?
RequirementsDesignImplementationTestingDeploymentMaintenance
Agile = rapid deliveryLoopy, not linearOften at the same time
11
12
PEOPLE OBJECTS
Prioritized To-Do listWall spaceSprint Info
Team nameDurationCeremonies
Index cardsTacks …can’t for get tacks
13
Identify rolesScrum MasterProduct OwnerScrum Team
Schedule CeremoniesDaily ScrumSprint PlanningSprint ReviewSprint RetrospectiveStory Grooming
14
15
April 2013
Mon Tue Wed Thu Fri 1 2 3 4 5
Sprint 02 Grooming
Sprint 01 Review Sprint 01 Retro
Sprint 02 Planning
Start Sprint 02
8 9 10 11 12
15 16 17 18 19
Sprint 03 Grooming
Sprint 02 Ends
Sprint 02 Review Sprint 02 Retro
Sprint 03 Planning
Start Sprint 03
22 23 24 25 26
29 30
Sprint 04 Grooming
Sprint 03 Ends
16
As a <role> I want <goal/desire> so that <value>
As a GIS’r, I want to use the city boundaries and roads to create the ESNs for the Service Arealayer so that our Service Area layer will be as accurate as possible.
17
Planning pokerFibonacci sequence
18
19
• Prioritize Backlog• Develop Stories/Tasks• Acceptance Criteria• Estimate Effort
20
What did I do yesterday?What am I doing today?What is in my way (impedences)?
21
Discuss Story StatusAcceptance Criteria MetClose/Split/Bounce Stories and TasksDemosQuick Meeting
22
Good, Bad, UglySprint Starfish
Keep doingStop doingStart doingMore ofLess of
Be Thorough
No Management or No Management or Customers!!!Customers!!!
23
24
Stories Too Big EpicsUndersizedIncompleteNot Enough CommitmentSprint vs Other Work
25
26
27
28
29
Not as smooth as expectedMany ways to do the same thingTrouble reaching consensusToo many Ad hoc requestsDifficult to planCultureDefinition of done
30
Don’t let perfection be the enemy of good“Next Sprint”Clear & Concise directionDaily praise & gratificationCompleting work dailyDaily progress
31
32
Tim Nolan, Collin [email protected]@plotboywww.linkedin.com/in/nolantim
youtube.com/watch?v=U__m4N7Ml30
Judas Priest Concert, Reunion Arena 1986