Why do you assume that half the ppl work on one feature now??? You can easily stagger the process by retaining the same amount of ppl on the teams. You just stagger per team per feature. That way you do get the benefit of not having to jump between projects and get a better feature right out of the gate. That can save time.They halved the number of devs working on a feature, ie, doubling the workload of the remaining devs. Then doubled the period of which it is worked on, bringing it right back down where they started. There is no more time to work on a feature. It's the exact same amount of man-hours. The only way to get extra work out of this is to bend space-time.
I did indeed notice that. This doesn't fix it.
Look, how many months pass between features doesn't tell anything about the amount of work that is put into the feature, as it doesn't address whether there are 1, 2, 20, or 200 people working on it. So lets talk about man-hours and man-months.
If feature X takes 3 months with 10 people, that's about 5k man-hours. If you divide those 10 people to two 5 people teams that then work on features X and Y, but over 6 months instead, that's still 5k man-hours for feature X. You do not get any additional time, if 5k man-hours isn't enough to get that feature done, then it isn't enough just because you spread them over 6 months instead of 3.
They're still making the same amount of features over the same period of time. Only before this they made X, then Y, then Z. Now they make X with half the team and Y with the other half, but X gets released 3 months earlier and Z is started. That is, if you considered "all at once" a bad approach, this is then 'even more at once'.
Spending greater initial effort to reduce the amount of time required to fix a feature has nothing to do with staggered development. To spend greater initial effort, you'd need more man-hours, that is, you either need to hire more people or reduce the amount of work you're doing. Could be CIG is just using this 'staggered development' as a smokescreen to have few months to catch-up, spend greater initial effort for the next update and hope to get that ball rolling, but if they don't start to more accurately estimating the amount of work they can do for each patch and only promise the amount of features they can make with their man-hours, we'll be back here in no-time flat.
Or it won't, but it's better then having features that don't work and everybody being pissed off about it. It can help in the long run.
Let's say they had the 10 men teams working on features. Those teams spent 3 month each working on their own features. Some finished, some didn't, and had to spend time from the next 3 months on it. It would only make sense to allow them to spend 6 months, as they were already spending that time.
It doesn't half the amount the of ppl working on it.
As for how can we know how much time they spend on it, we can't know exactly. But we can see on the roadmap and the patch notes and weekly newsletters how they need more time for a lot of the features then 3 months.
We keep arguing the same point. They do Not get more time overall. That is true.
What you assume is that somehow they won't be making up any time lost by not having to jump between features, and not having to go back to features they were supposed to complete.
I say they might do. And that's the extra time.
Will this make things faster from our perspective? No. Actually it means an extra 3 months because of the staggering, as you can see by the SQ42 push back.
But it might make things more playable and enjoyable which is a win for us backers.