Sad -but-true story. I've worked with teams who consistently delivered reliable, useful, usable software time after time, and the customer just didn't notice.
The customer did notice teams who heroically put out fires with every release - fires that those teams had started.
So we learned to start fires. Add a couple of show-stopping bugs, or a Thread.sleep() in some performance-critical code, that could be removed in a heartbeat.
Software development's mostly about managing expectations.
True story.
Org has important business function - still manual, expensive, slow.
Two projects have failed to deliver solution.
Next attempt.
1 Team picks simple tech & finds key users to talk too.
2 Team, talking to users, realises the solution is framed wrong.
3 Team pivots to new approach.
4 Original need met
5 New needs identified
6 Solutions delivered frequently.
...
Users happy
No complaints
More dev...
No complaints
...
Result: Mgmnt offshores dev & makes team redundant.
Add comment