The best part is when you fail to make the one day deadline (as do all of the other subsystems), and it gets pushed back a day, the PM then adds another week's worth of tasks to the list.
I worked on a project where management rejected engineering's plan to do 8 releases over 3 years, because "releases have a high associated cost" and "you shouldn't need more than 4 releases".
Time it took to do all the release paperwork and associated process: roughly 3 days, depending on which group you were int.
Number of actual releases in the first year because PM declared an urgent fix was needed in the field: 37.
Standard number of work days per year: 252
Number of days doing paperwork for releases that year: 111
My director thought I was kidding when I said that the project team spent 45% of the entire year doing nothing but release paperwork, until he looked at the release history.
Feed her an alarm clock so you can hear her coming. ⏰ Tick. Tock.
The best part is when you fail to make the one day deadline (as do all of the other subsystems), and it gets pushed back a day, the PM then adds another week's worth of tasks to the list.
I worked on a project where management rejected engineering's plan to do 8 releases over 3 years, because "releases have a high associated cost" and "you shouldn't need more than 4 releases".
Time it took to do all the release paperwork and associated process: roughly 3 days, depending on which group you were int.
Number of actual releases in the first year because PM declared an urgent fix was needed in the field: 37.
Standard number of work days per year: 252
Number of days doing paperwork for releases that year: 111
My director thought I was kidding when I said that the project team spent 45% of the entire year doing nothing but release paperwork, until he looked at the release history.