O slideshow foi denunciado.
Utilizamos seu perfil e dados de atividades no LinkedIn para personalizar e exibir anúncios mais relevantes. Altere suas preferências de anúncios quando desejar.

How to Organize Game Developers With Different Planning Needs

109 visualizações

Publicada em

Different skills have different needs when it comes to planning. For a coder it may make perfect sense to plan work in two-week sprints, but for an artist, an asset may take longer than two weeks to complete.

How do you allow different skills to plan the way that works best for them? Some studios may choose to open up for flexibility – do whatever you like! But that tends to cause issues with alignment and siloes of data, resulting in loss of vision. Lost vision in the sense that it is difficult to understand, but also — and maybe more importantly — the risk of losing the vision of what the game will be.

With the right approach, however, you can avoid these obstacles. Join backlog expert Johan Karlsson to learn:

-The balance of team autonomy and alignment.
-How to use the product backlog to align the project vision.
-How to use tools to support the flexibility you need.

Looking for a planning and backlog tool? You can try Hansoft for free.

Publicada em: Software
  • Seja o primeiro a comentar

  • Seja a primeira pessoa a gostar disto

How to Organize Game Developers With Different Planning Needs

  1. 1. Hansoft by Perforce © 2020 Perforce Software, Inc. How to Organize Game Developers With Different Planning Needs JOHAN KARLSSON | SEPTEMBER 2020 How to Organize Game Developers With Different Planning Needs Johan Karlsson | September 2020
  2. 2. perforce.com2 | © 2020 Perforce Software, Inc. Johan Karlsson jkarlsson@perforce.com Senior Consultant, Hansoft Perforce Software
  3. 3. 3 | Hansoft by Perforce © 2020 Perforce Software, Inc. perforce.com How to Organize Game Developers With Different Planning Needs 1 2 Planning: The balance of team autonomy and alignment. Organization: How to use the product backlog to align the project vision. 3 How to use tools to support the flexibility you need.
  4. 4. 4 | Hansoft by Perforce © 2020 Perforce Software, Inc. perforce.com • Goal — why will this game be fun to play? • What — technical tasks we need to achieve. • Who is going to do it? • How do we prioritize our work? • What are the risks and how do we handle yet unknown events? • How to verify and sets the limits around the quality of the game? • When, when… when?!? Why planning is critical to organization?
  5. 5. 5 | Hansoft by Perforce © 2020 Perforce Software, Inc. perforce.com How long did it take to build a feature? Timeline Developer: 1 week Player: 1 year
  6. 6. 6 | Hansoft by Perforce © 2020 Perforce Software, Inc. perforce.com How long does it take to build a feature? Designer Concept Artist QA Developer: 1 week Model Artist Audio Player: 1 year Dev
  7. 7. 7 | Hansoft by Perforce © 2020 Perforce Software, Inc. perforce.com You can keep things secret: announce as late as possible Designer Concept Artist QA Developer: 1 week Model Artist Audio Player Announce! Dev
  8. 8. 8 | Hansoft by Perforce © 2020 Perforce Software, Inc. perforce.com You can optimize the pipeline Designer Concept Artist QA Developer: 1 week Model Artist Audio Player Dev
  9. 9. 9 | Hansoft by Perforce © 2020 Perforce Software, Inc. perforce.com This webinar is about team alignment Designer Concept Artist QA Developer: 1 week Model Artist Audio Player It’s a Team Effort! Dev
  10. 10. 10 | Hansoft by Perforce © 2020 Perforce Software, Inc. perforce.com How complex are game dev projects? Simple Com plicated Anarchy Technology User stories Far from certain Close to certain Com plex Close to agreement Far from agreement
  11. 11. 11 | Hansoft by Perforce © 2020 Perforce Software, Inc. perforce.com Lean - Kanban • Handles both complex and complicated situations well. Plan-driven - Gantt • Typically focused on departmentalized teams. • Handles complicated parts of the plan well. Agile - SCRUM • Typically focused on feature teams. • Handles complex situations well. What planning approaches do we have available?
  12. 12. 12 | Hansoft by Perforce © 2020 Perforce Software, Inc. perforce.com SCRUM
  13. 13. 13 | Hansoft by Perforce © 2020 Perforce Software, Inc. perforce.com Gantt
  14. 14. 14 | Hansoft by Perforce © 2020 Perforce Software, Inc. perforce.com Kanban
  15. 15. 15 | Hansoft by Perforce © 2020 Perforce Software, Inc. perforce.com Hybrid Methods Content Team 3 Content Team 2 QA Team Feature Team 2 Feature Team 1 Content Team 3Studio Leadership Shared Goals Product Backlog Management Plan- driven Lean Agile Agile Scrum- ban Plan- driven Agile Lean
  16. 16. 16 | Hansoft by Perforce © 2020 Perforce Software, Inc. perforce.com Product Backlog Management in a nutshell for Alignment Demand Product Backlog Structure drives strategy & vision. Visibility & transparency for cross-team communication. Decision-making artifact maximizes work not done and sets limits.
  17. 17. 17 | Hansoft by Perforce © 2020 Perforce Software, Inc. perforce.com Putting it all together Product Backlog Content Team 1 Content Team 2 Feature Team 1 Demand
  18. 18. Questions? Thank You For Attending

×