It's widely believed that creep — changes to requirements that supposedly have been settled — is due to unclear requirements. This Advisor looks at project creep differently, enabling us to see that most creep involves requirements that should and could have been identified but weren’t, and that this happens so often that it’s a certainty rather than a risk.
Advisor
About The Author
Robin F. Goldsmith works with, trains, and coaches business and project professionals to get the right results right through business analysis/requirements, Proactive Software Quality Assurance (SQA)™, Proactive Testing™, Beyond the Textbook™ software acquisition, project management, process improvement, metrics, and REAL ROI™. Previously, he was a developer, systems programmer/database administrator/QA analyst, and project leader with the US… Read More
Don’t have a login?
Make one! It’s free and gives you access to all Cutter research.