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.

The squad life - a recipe for self organising geospatial teams

654 views

Published on

Our future is an increasingly uncertain place, with consumer expectations and technology rapidly changing. The geospatial industry needs to be more adaptive, collaborative and creative if we want to ride the waves of disruption and deliver on our potential for growth.

Although national coordination is needed, we don't need to wait for it. We can all play our part in growing and developing the industry and the role geospatial plays in each of our domains.

This presentation presents a starter recipe for creating and empowering self organising geospatial teams in an agile and nimble way to improve the way we work and lead us to deliver more innovative geospatial products and services.

Published in: Leadership & Management
  • Hello! Get Your Professional Job-Winning Resume Here - Check our website! https://vk.cc/818RFv
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here

The squad life - a recipe for self organising geospatial teams

  1. 1. The Squad Life a recipe for self organising geospatial teams Elise McKenna @mappingmckenna
  2. 2. “Nothing endures but change”
  3. 3. “Nothing endures but change” 2045 - All of human intelligence combined Now
  4. 4. Agility: Delivering major pieces of work in smaller chunks, with quicker implementation;
  5. 5. From individual contributors and bureaucratic leadership
  6. 6. From individual contributors and bureaucratic leadership To teams of collaborators and distributed leadership
  7. 7. Data Analytics Infrastructure API’s Apps Consulting GEO
  8. 8. THE RECIPE for self organising geospatial teams
  9. 9. INGREDIENTS • No larger than a 2 pizza team • Everyone must be empowered to make decisions • Safe environment • Learning and growth mindsets
  10. 10. Set the common goal Work in smaller iterations Continuously improve Communicate and track progress METHOD <=QUARTERLY <=MONTHLY <=WEEKLY
  11. 11. 1/4LY OKR SETTING FORNIGHTLY SPRINT PLANNING MONTHLY RETROSPECTIVES DAILY STANDUP METHOD <=QUARTERLY <=MONTHLY <=WEEKLY SHOWCASES/ DEEPDIVES HACKTIME 155 60 120 60
  12. 12. EQUIPMENT Collaborative code version control Collaborative document control Collaborative task management git wiki tasks
  13. 13. DO WE NEED THIS RECIPE?
  14. 14. 43.2% 32.4% 18.9% We dont use agile 0 - 2 years 2 - 5 years 5 + years
  15. 15. 38% 27% 24% Fully remote Hybrid Flex team All onsite Other
  16. 16. DO WE NEED THIS RECIPE? 47%use sprints 46%use git “This shit works” “Agile as currently executed by most projects is an abomination” “biggest problem we face is the willingness of clients to understand the benefits of agile development” “What is agile?” 15% “Parts of the org use Agile techniques but not the geospatial section.” use design thinking
  17. 17. • 6-7 people on a team • Everyone can make decisions • Safe environment • Learning and growth mindsets INGREDIENTS • 1/4ly goal setting • 2-3 Weekly sprint planning • Daily standups • End of sprint retrospectives • Hacktime • Showcases METHOD EQUIPMENT • Github/bitbucket • Wiki/confluence • Trello/jira/taiga

×