5 ms·
When you keep stakeholders updated early, you force them to make hard decisions about their product so you know what to prioritize. It makes everyone focus on
by mobjack 7y ago
When you keep stakeholders updated early, you force them to make hard decisions about their product so you know what to prioritize.
It makes everyone focus on what is most important.
Are those features really necessary for the release? Can we change the requirements to accomplish the goal easier? Is it important enough that we should delay it?
Without a deadline, engineers waste time working on stuff that is fun and interesting to them and not the hard stuff that is needed to ship a product across the finish line.
I do that along with every other engineer I know. It is human nature.
- deleted 7y ago[deleted]
- spoondan 7y agoYou don’t need a deadline to establish priorities and ensure the team is focused on those priorities. Nor does a deadline actually prevent procrastination. We all have had homework due that we have rushed to finish because we were watching TV, playing games, out with friends, or whatever. So too with software engineering. Anyway, if you are using sprints, there actually are due dates. It’s just there are a lot of them occurring in rapid succession, and we don’t commit to what we’ll finish in the following due date until after the impending one.
- jasonpeacock 7y ago> Without a deadline, engineers waste time working on stuff that is fun and interesting to them and not the hard stuff that is needed to ship a product across the finish line. Why is the threat of a deadline required to ship product?