3 ms·
Well, this is some good advice. Another nice trick if you're under time pressure is to arrange the project so that you can deliver it in stages that partially
by GlennS 8y ago
Well, this is some good advice.
Another nice trick if you're under time pressure is to arrange the project so that you can deliver it in stages that partially meet the requirements, or even deliver something non-functional that people can play with while they wait.
This can keep the sales team rolling or customers happy for a while, buying you some time to write the program properly.
As a bonus, you might get earlier feedback if you're going in the wrong direction, in which case less time wasted.
(Obviously this approach isn't always possible. Many problems won't decompose nicely.)
- afarrell 8y agothis is where it becomes crucial to know why you're building the thing you're building. That way, you can often structure the project in phases according to your engineering judgement of the way those phases are built and the business value they enable. Then you can cut scope by postponing (or not doing) some of the phases. Ideally.