Project management methodologies involve some kind of estimates on the content of the project (i.e. scope) and effort/duration (i.e. schedule). Simple techniques like WBS (work breakdown structure) with Gantt Charts or more complex techniques like PERT (Program Evaluation and Review Technique) involve estimating the content and ultimately the duration or effort of each of the …
One of the questions that I and other #NoEstimates proponents hear quite often is: How can we make decisions on what projects we should do next, without considering the estimated time it takes to deliver a set of functionality? Although this is a valid question, I know there are many alternatives to the assumptions implicit …
The people that convinced us to never mix design with requirements may have wrecked more software projects and destroyed more value in the software industry than anyone else! Just think what happens when you separate requirements from design: You don’t validate assumptions to more than a very superficial level (the “I don’t care about the …
