There is an interesting relationship between having predictable estimates for project management and using a thorough definition of done. Achieving the full definition of done for a feature or release (often called being done-done) is surprisingly difficult. You may have heard the anecdotal rule of thumb that it takes 80% of the time to achieve [...]
Posts Tagged ‘schedule’
There are several strategies for producing software releases. One approach is to release by schedule – the software ships on a fixed date defined well in advance. Another method is to release based on budget – the work stops once the money available is exhausted. I believe, however, that the best strategy in general is [...]
My article on Understanding Project Schedules discussed four factors of project schedules: time, resources, scope, and quality. Time is often the factor of greatest interest to project stakeholders such as customers or management. They often ask when the project will be finished. I refer to this as elapsed time – the passage of days on [...]
