3 ms·
It’s not hard. Maintain a priority list. Always work on what is #1 priority. If #1 priority is blocked then work on #2 priority. Use the priority list to negoti
by mbrodersen 4y ago
It’s not hard. Maintain a priority list. Always work on what is #1 priority. If #1 priority is blocked then work on #2 priority. Use the priority list to negotiate with your stake holders. That’s it.
I have had a lot of success using this simple formula in my 30+ years career. Both as an individual developer and when managing small to large software teams. It’s simple. It works.
- AdieuToLogic 4y agoAgreed. It’s not hard. Maintain a priority list. Always work on what is #1 priority. If #1 priority is blocked then work on #2 priority. I've described this same approach as "risk driven development." Identify the highest risk to an effort's success, address it, then the next highest, etc. If, during this process, a newly discovered risk is identified as being more than what is currently being worked, put the new risk at the front of the queue and address it. This drives risk to 0, which drives the probability of success to 1. And as you succinctly stated: It’s simple. It works.
- pramodbiligiri 4y agoThere’s an old term called Spiral Model and an associated paper that puts Risk at the centre of software development decisions - https://en.m.wikipedia.org/wiki/Spiral_model https://en.m.wikipedia.org/wiki/Spiral_model