Bonkic
Großmeister/in der Spiele
- Mitglied seit
- 06.09.2002
- Beiträge
- 37.669
- Reaktionspunkte
- 8.590
zurück zum thema:
squadron 42 - beta wurde um weitere 3 monate verschoben
cig begründet das mit einer umstrukturierung der entwicklung:
Staggering Dev FAQ
squadron 42 - beta wurde um weitere 3 monate verschoben
cig begründet das mit einer umstrukturierung der entwicklung:
Staggered Development is an approach that splits the various development teams between multiple delivery dates. This puts teams into a cadence whereby they are delivering larger features every couple of quarters instead of every quarter, but due to their staggered nature, you would still receive an update every quarter.
To oversimplify for clarity's sake, an example of this would be that half our dev team may be working on 3.7 features, tech, and content, while the other half would be working on 3.8. Once the team working on 3.7 delivers the patch, they would then transition to 3.9. Rinse and repeat.
Staggering the teams like this means 6-month cycles for development instead of 3, which means more time to ensure features are more complete with fewer bugs - all while still delivering quarterly patches.
What does this mean for Squadron 42?
Ultimately, this is a really good thing for Squadron 42 development as well. Both Star Citizen and Squadron 42 share a codebase and as features come online for both games, they will be in a more stable/playable state, reducing potential blockers that can hinder and slow down development. You will of course notice that our target Beta date for Squadron 42 has moved back by 12 weeks in today’s Roadmap update, but this is a necessary step as a result of changing the overall development cadence, which we expect will create positive results in the overall delivery and experience of Squadron 42.
Staggering Dev FAQ
Zuletzt bearbeitet: