Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Getting GIS Done Using the Scrum
Methodology
What was our problem?

•
•
•
•

Frustrated customers
Reactive staff
Requests getting lost
Little to no visibility into wha...
What was the cause?

•
•
•

Work lacked prioritization
Lack of resources (time, people,
money)
Not resolving the root of t...
What is Scrum?
Scrum
•

Scrum is an iterative and incremental agile
software development framework for managing
software projects and pro...
Scrum Characteristics
•
•
•
•

Agile process
Self-organizing teams
Projects progress in a series of sprints
Requirements a...
Roles
Roles
• Product Owner
•
•

•

Scrum Master

•
•
•

•

Represents or is the user or customer
1 voice, even if representing ...
Product Owner Needs…

•
•
•
•

A understanding of business goals
To have a vision on how tools support
business goals
To b...
Product Owner Responsibilities

•

Manage the ROI

• Measure the project against ROI
• Prioritize product backlog to maxim...
Scrum Master

•
•

Removes the barriers between
development and the product owner
Educates Product Owner about Scrum

• To...
Scrum Team

•
•
•

Typically 5-9 people
Ideally cross functional
Ideally full time
Scrum Process
Release Planning

• First meeting held by the Scrum Team
• Responsible for determining what work
needs to be accomplished ...
Product Backlog
Product Backlog

•
•
•

Scrum’s version of a requirements
document
List of desired work
Combination of…

• Story based wor...
Product Backlog Example
•

Contains
• General priorities
• Ranking 1 through X
• Estimates – imprecise
and rough, used for...
Sprint Planning
Sprint planning meeting
• Purpose of the Sprint Planning meeting

•

is to determine what work will be done in
the upcomin...
Team Commitment

•

The team selects the work to be
accomplished in a sprint

• Which items
• How many items

•

This is a...
Business Commitment

•

Business Commitment

• To leave priorities alone during a sprint
Sprints
Sprints
•
•
•
•
•

In Scrum, projects make progress with Sprints
Sprint are a set amount of time (2 week at DW)
Work is ma...
Example of a Sprint Burndown Chart
Daily Scrum meetings

•

Parameters

• Daily
• 15 minutes
• Answers
• What I did yesterday?
• What I plan to do today?
• D...
Sprint Review Meeting

•
•
•
•

Team presents what it accomplished
in the sprint
Usually in the form of a demo
Informal me...
Sprint Retrospective

•
•
•

Review of what is or is not working in
the process
Important when starting scrum
Participants...
GIS and Scrum
How does this fits with GIS?

•
•
•

GIS work is iterative
GIS is strong linked with technology
A GIS project is just that...
Contact
Jonathan Spitze
Manager of IT Geospatial Asset Management
Denver Water
303-628-6050
jonathan.spitze@denverwater.or...
2013 Enterprise Track, Getting GIS done using the Scrum Methodology Jonathan Spitze
2013 Enterprise Track, Getting GIS done using the Scrum Methodology Jonathan Spitze
2013 Enterprise Track, Getting GIS done using the Scrum Methodology Jonathan Spitze
Upcoming SlideShare
Loading in …5
×

2013 Enterprise Track, Getting GIS done using the Scrum Methodology Jonathan Spitze

514 views

Published on

We live in a world where limited resources is a constant battle. One of the biggest struggles is how to get work done and make sure that it brings the most value possible to our customer. Managing GIS work through Scrum provides a way to do this. In this presentation, I will explain the concepts around the Agile methodology and how it could be applied not only in the IT world, but to any GIS work that needs to be done.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

2013 Enterprise Track, Getting GIS done using the Scrum Methodology Jonathan Spitze

  1. 1. Getting GIS Done Using the Scrum Methodology
  2. 2. What was our problem? • • • • Frustrated customers Reactive staff Requests getting lost Little to no visibility into what staff was working on
  3. 3. What was the cause? • • • Work lacked prioritization Lack of resources (time, people, money) Not resolving the root of the problem
  4. 4. What is Scrum?
  5. 5. Scrum • Scrum is an iterative and incremental agile software development framework for managing software projects and product or application development.
  6. 6. Scrum Characteristics • • • • Agile process Self-organizing teams Projects progress in a series of sprints Requirements are captured as items in a product backlog
  7. 7. Roles
  8. 8. Roles • Product Owner • • • Scrum Master • • • • Represents or is the user or customer 1 voice, even if representing more than 1 person Represents management to the project Enforces Scrum values and practices Removes impediments to the team progress Scrum Team • Commits to doing the work
  9. 9. Product Owner Needs… • • • • A understanding of business goals To have a vision on how tools support business goals To be able to coordinate priorities amongst all users/departments Authority to make decisions on what is being implemented and when
  10. 10. Product Owner Responsibilities • Manage the ROI • Measure the project against ROI • Prioritize product backlog to maximize ROI • Calls for release • Decides when to call for an official release • Can shift a release forwards or backwards to maximize ROI • Establish a shared vision
  11. 11. Scrum Master • • Removes the barriers between development and the product owner Educates Product Owner about Scrum • To maximize ROI and meet project objectives • Improve productivity in any way possible
  12. 12. Scrum Team • • • Typically 5-9 people Ideally cross functional Ideally full time
  13. 13. Scrum Process
  14. 14. Release Planning • First meeting held by the Scrum Team • Responsible for determining what work needs to be accomplished for the project to be successful. • Determine level of effort
  15. 15. Product Backlog
  16. 16. Product Backlog • • • Scrum’s version of a requirements document List of desired work Combination of… • Story based work • The user can search… • Task based work • Improve exception handling on…
  17. 17. Product Backlog Example • Contains • General priorities • Ranking 1 through X • Estimates – imprecise and rough, used for assigning into sprints • • Allowed to grow and change as more is learned Prioritized by Product Owner
  18. 18. Sprint Planning
  19. 19. Sprint planning meeting • Purpose of the Sprint Planning meeting • is to determine what work will be done in the upcoming sprint 2 parts • • For two week sprints • • Prioritization and Planning no longer than 1/2 day for 2 week sprints Participants: • Product Owner, Scrum Master, and Team
  20. 20. Team Commitment • The team selects the work to be accomplished in a sprint • Which items • How many items • This is a team commitment, not an individual commitment
  21. 21. Business Commitment • Business Commitment • To leave priorities alone during a sprint
  22. 22. Sprints
  23. 23. Sprints • • • • • In Scrum, projects make progress with Sprints Sprint are a set amount of time (2 week at DW) Work is managed through the Sprint Backlog Progress is tracked through the use of a burn down chart During sprints, the team performs • • • • Analysis Design Code Test • Project is potentially releasable after every sprint
  24. 24. Example of a Sprint Burndown Chart
  25. 25. Daily Scrum meetings • Parameters • Daily • 15 minutes • Answers • What I did yesterday? • What I plan to do today? • Do I have any impediments? • Many times results in follow-up conversation among the team
  26. 26. Sprint Review Meeting • • • • Team presents what it accomplished in the sprint Usually in the form of a demo Informal meeting Participants • Users, Management, Product Owner, Other Developers, Scrum Master, Scrum Team
  27. 27. Sprint Retrospective • • • Review of what is or is not working in the process Important when starting scrum Participants • Scrum Master • Product Owner • Team
  28. 28. GIS and Scrum
  29. 29. How does this fits with GIS? • • • GIS work is iterative GIS is strong linked with technology A GIS project is just that….a project
  30. 30. Contact Jonathan Spitze Manager of IT Geospatial Asset Management Denver Water 303-628-6050 jonathan.spitze@denverwater.org

×