development reading-list

Scope creep is inevitable. A project starts with a small mandate and ends with an enormous, uncontrolled scope. What was a small change is now a complete rewrite. It's easier to visualize scope creep with software projects — you can easily see the number of services or areas of code that a change touches. And it's sometimes easier to measure (which changes aren't in the critical path of the goal feature or product?). But it happens in almost every project. I don't think it can be eliminated entirely, but understanding the sources and the consequences might help limit its reach.

continue reading on blog.matt-rickard.com

⚠️ This post links to an external website. ⚠️

You might also like:

If this post was enjoyable or useful for you, please share it! If you have comments, questions, or feedback, you can email my personal email. To get new posts, subscribe use the RSS feed.