1 / 34

Utilize Agile Project Management for GIS Projects

Utilize Agile Project Management for GIS Projects. Jennifer Prather and Lana Tylka. Agenda. Proposing Agile Managing Agile Case Studies. Proposing Agile. When would you use Agile?. Waterfall. Staged Delivery. Agile. Several applications Prototypes expected.

ereginald
Télécharger la présentation

Utilize Agile Project Management for GIS Projects

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Utilize Agile Project Management for GIS Projects Jennifer Prather and Lana Tylka

  2. Agenda • Proposing Agile • Managing Agile • Case Studies

  3. Proposing Agile

  4. When would you use Agile? Waterfall Staged Delivery Agile • Several applications • Prototypes expected • Flexible scope, deliverables • One or several applications • Clear requirements • Fixed deliverables • Single application Scope, Technology, Contract • Any size or duration project • Medium or large size, mid to long duration • Small size, short duration project Size, Duration • Customer EXPECTS collaboration • Stable, experienced project team • Capacity, resources, and environment to support multiple releases • Limited capacity, resources, and environment • Frequent turnover on project team Capacity, Capabilities, Environment

  5. 4 2 3 1

  6. Pricing

  7. Big Picture Epics System Architecture Database Design Application Hardening Widget 1 Widget 2 Story Points 21 34 34 55 21

  8. Story Points 21 34 34 55 21 8 x Hours 168 272 272 440 168

  9. Pricing Sheet

  10. Project Work Breakdown Structure System Architecture Database Design Application Hardening Widget 1 Widget 2 5.1 User Story 1.1 User Story 2.1 User Story 3.1 User Story 4.1 User Story 5.2 User Story 1.2 User Story 2.2 User Story 3.2 User Story 4.2 User Story 2.3 User Story 3.3 User Story 4.3 User Story 3.4 User Story 4.4 User Story 4.5 User Story

  11. Managing Agile

  12. AGILE

  13. Development Cycle ScrumMaster Product Owner 2 - 4 Week Sprint Daily Scrum The team Product Backlog Sprint Planning Sprint Backlog Potentially Shippable Product Increment Stakeholders Retrospective

  14. As a [role], I can [feature] so that [benefit]

  15. As a field representative, I want to collect information offline so that data can be collected in remote locations.

  16. Product Backlog

  17. Wish List

  18. Sprint Backlog

  19. Sprint Backlog

  20. Sprint Backlog 4h 2h 4h 8h 2 days 3 days 1h 8h

  21. Managing Resources Plan B Plan Z Plan A 50% 50% 50% Your Project Sprint Sprint 50% 100% 100% 50% 50% 50% 50% 50% 50% 50% 100% 100% 75% 75% 75% 100% 100% 75%

  22. Keys to Successful Sprinting! Trusted Partnerships Communication Transparency Utilize Available Tools…

  23. Tools

  24. Using Trello

  25. Using GitHub

  26. Using TFS

  27. Case Studies Example Projects

  28. Case Study – Medium Scale ScrumMaster Product Owner Lead developer Analyst Daily Scrum The team 1 Week Sprint 12 developers 2 testers 1 PM Fluctuates as needed Product Backlog Sprint Backlog Sprint Planning Potentially Shippable Product Increment Stakeholders Retrospective Customer’s PM Internal PM

  29. Case Study – Medium Scale • Why Agile? • Customer was familiar with Agile and believed iterations was the best method to get to realize their end goal • Key Challenges / Lessons Learned • Stakeholders (customer) was an active participant with respects to the grooming of the product backlog and sprint planning events. • Team consisted of contractors from multiple companies who were all using their own version of Scrum • Utilization of multiple contractors created dependencies that had to be accounted for in Sprint Planning. • Hours were used for estimates to avoid an inconsistent Points experience • Monthly iterations, then bi-weekly, then weekly, then back to bi-weekly in order to get the right amount of feedback

  30. Release Manager Scrum of ScrumMaster Case Study - Large Scale Lead developer Analyst Scrum of Scrums Daily Scrum Daily Scrum Product Owner Scrum Master Scrum Master Scrum Master Product Owner Product Owner Developer Developer Analyst Developer Analyst Analyst 2 Week Sprint Daily Scrum The team Sprint Backlog The team The team ~7 developers 1 tester ~7 developers 1 tester ~7 developers 1 tester Sprint Backlog Product Backlog Sprint Planning Sprint Planning Sprint Planning Sprint Backlog Potentially Shippable Product Increment Retrospective Stakeholders Customer’s PM Project Manager

  31. Case Study – Large Scale • Why Agile? • Project was contractually required to follow the SAFe Agile Methodology. • Requirements were vague and customer recognized the benefit in iterative development to achieve the best results. • Key Challenges / Lessons Learned • Deployment into the customer’s footprint occurs at the end of the Release. • Large project team to manage. • Each Scrum Team was responsible for individual features. • Dependencies existed between scrum teams. • Stakeholders (customers) were only present during Stakeholder Reviews and were not active participants during the release planning events. • Disconnected environment meant that the customer could not test the features until the end of a release. • Bi-weekly demonstrations to “sell off” features and to show progress.

  32. Questions?

  33. Please take our Survey Your feedback allows us to help maintain high standards and to help presenters Find your event in the Esri Events App Find the session you want to review Scroll down to the bottom of the session Answer survey questions and submit

More Related