If you are estimating things at increments like "a month" then you need to break things down into smaller chunks that are deliverable. The key part is continuo

If you are estimating things at increments like "a month" then you need to break things down into smaller chunks that are deliverable. The key part is continuous delivery - even if nobody uses the small addition or you need to put a feature flag in that "turns it on" at some point in the future. If you get into the practice of continuous delivery, which means a dev can ship something into production anytime they need to (with approvals, code review, etc.) then it becomes a more fluid process. Take building a To Do app. It might take a month to deliver the whole thing, right? What if you broke it down into smaller chunks like: * Showing a static list of open items * Clicking an item marks it complete in UI * Save state to a database * Archiving items If each of those 4 were shippable to production with tests, etc. then you can incrementally build the system. It may sound like extra work but once you automate away the builds, running tests, and deploys you can respond much quicker to changes.