3 ms·
> What it usually boils down to on these projects is a spreadsheet written by an out-of-touch project manager who has to answer to a senior manager and pulls a
by blt 12y ago
> What it usually boils down to on these projects is a spreadsheet written by an out-of-touch project manager who has to answer to a senior manager and pulls a timeframe out of thin air. A lot of planning and documenting goes into filling about 2/3 of this timeframe, and then the last 1/3 is spent killing yourself trying to finish a shitload of work in a short time frame to meet the original estimate
This is an accurate description of my last job using Agile practices. This was a shrinkwrapped product too. No customer demanding estimates, in the midst of fundamental architecture changes, and people still trying to slice-n-dice blue-sky new product development into sprints and user stories. The estimates were a joke and quality suffered because people rushed to get stuff done for the 3 week sprint deadline. All because some manager wanted it. Fucking stupid.
- deleted 12y ago[deleted]
- Spearchucker 12y agoMaybe my years (I'm over 40). I tend to ask for estimates I didn't create, and call bullshit when I have to. People believe me, because I back my claim up with a lot of experience and anecdote. Also estimation and agile do work, if done with some forethought - I wrote about that here: https://www.wittenburg.co.uk/Entry.aspx?id=db2d81dc-c435-42ca-89a4-48273abd2cf9 https://www.wittenburg.co.uk/Entry.aspx?id=db2d81dc-c435-42c....