Big news for anyone who glances at the Release View in the public roadmap: https://robertsspaceindustries.com/comm-link/transmission/18520-Roadmap-Roundup-February-2nd-2022
The salt on Spectrum is exactly what you’d expect: https://robertsspaceindustries.com/spectrum/community/SC/forum/3/thread/roadmap-roundup-february-2nd-2022
TL;DR CIG plan to only tell us what they are working on, and show progress, but they will no longer say what will be in future patches beyond the next patch, and will only show deliverables in the next patch once they are finished and committed. And apparently it‘s our fault for being so shouty when they move things around.
Edit: two things to add. In agile development, you don’t commit to delivering features more than one sprint out. You have a backlog of features (etc.) you want to add, and every sprint you ‘groom’ the backlog, estimate effort for tasks, decide how many tasks to do this sprint, that you are confident of completing. Obviously it’s much more complex than that but the idea of running agile development (as CIG and nearly all modern software developers do) and having committed deliverables in the medium-long term is self-contradictory. So from CIG’s perspective this is an entirely reasonable and rational change. I’m still sad to see it go, from a selfish point of view.
Plus, The Noobifier uploaded his take on it. I’m sure all the usual commentators will too - maybe have already.
The salt on Spectrum is exactly what you’d expect: https://robertsspaceindustries.com/spectrum/community/SC/forum/3/thread/roadmap-roundup-february-2nd-2022
TL;DR CIG plan to only tell us what they are working on, and show progress, but they will no longer say what will be in future patches beyond the next patch, and will only show deliverables in the next patch once they are finished and committed. And apparently it‘s our fault for being so shouty when they move things around.
Edit: two things to add. In agile development, you don’t commit to delivering features more than one sprint out. You have a backlog of features (etc.) you want to add, and every sprint you ‘groom’ the backlog, estimate effort for tasks, decide how many tasks to do this sprint, that you are confident of completing. Obviously it’s much more complex than that but the idea of running agile development (as CIG and nearly all modern software developers do) and having committed deliverables in the medium-long term is self-contradictory. So from CIG’s perspective this is an entirely reasonable and rational change. I’m still sad to see it go, from a selfish point of view.
Plus, The Noobifier uploaded his take on it. I’m sure all the usual commentators will too - maybe have already.
Last edited: