This page covers how teams approach deliverables in an agile fashion compared to a waterfall fashion.
For any type of project, teams who live the Agile Ways of Work behave differently when building products and services. They interact with each other, build working results, collaborate with users to define needs, and respond to change. Learn more here in the Agile Handbook:
🎢Building MVP's and MMP's with AgileDifferent kinds of teamwork happens at the same time instead of in stages on an Agile team project. For instance, a team may start with drafting a vision before they start researching to use it as a grounding for research to test assumptions. After doing research they may iterate on the vision and the product definition while also iterating on designs.
The sooner teams deliver the work outcomes into the hands of users in the Agile project lifecycle, the sooner they will be able to validate if their direction is the right way to go.
Agile teams should never treat work as "final" or "done", but simply the "next version". If they are always performing discovery, they are always learning new things. If they are always learning new things they should always be shifting their scope and vision. Only they can decide whether, how, and when as a self-organized team.
Last updated