4 ms·
9) Letting the sales guys write the spec, in the form of a powerpoint. 10) taking estimates from development and lopping off a big chunk plus adding extra scop
by Joeri 9y ago
9) Letting the sales guys write the spec, in the form of a powerpoint.
10) taking estimates from development and lopping off a big chunk plus adding extra scope, because “I couldn’t sell the original estimate” and “this project will be a great reference, so we can take the hit”
11) doing agile in the sense of changing scope / direction constantly, but requiring complete timelines for project delivery to check planned vs actuals.
12) the perennial favorite: having multiple managers who are too busy to talk to each other but not too busy to give conflicting instructions.
- temporallobe 9y agoOh God #10. I currently work for a project manager like this. He asks for LOE, and he rejects it, saying there's no way it could take that long. Then we'll be halfway through development, then told that in a week we're gonna go to production because that's what he promised to the stakeholders. He basically lies is ass off about delivery dates, then blames the devs for not delivering on time.
- jakub_g 9y agoMost of the points above are very true, particularly 3,5,7,9,10,11 from my experience. Additionally: 13) POs and devs accepting feature requests that don't add value but add a lot of complexity 14) Team members who add negative velocity and lower morale of everyone else in the project (but typically are highly regarded by the management who dismiss any complaints) The core IMO is that most people (especially non-technical, but technical too) can not properly understand the complexity of a software project as it's not something tangible like a building or a bridge.