5️⃣Requirements Milestone

What is it?

Requirements milestone delivers the details that a UX designers, UX researchers, and developers need to deliver their work. They document who the feature is for, what user goals should be achieved, when in the product it should be offered, where in the product it should be offered, why it brings value, and how the logic should be handled. This enables teams to deliver work that's efficient and aligned to the vision.

Why is it valuable?

The value of this milestone is huge for teams and products because it sets a clear path for everyone to follow. It helps the team understand what they need to build and why, making sure they don't miss anything important. For the product or service, it ensures that it meets the needs of the users and stands out with a strong brand identity. This organized approach saves time and effort, leading to a successful and well-received result.

Who’s involved?

DID YOU KNOW?

Agile teams do not have specific departments! They all float across different duties. So, this means that a UX designer can perform discovery work, and play any other kinds of duties they desire. See how this works in the Agile Handbook's "Daily Life on Agile Teams".

The following duties are involved in this milestone. These duties are performed by anyone who commits to them on a cross-functional team.

Business analyst duty
Product owner duty

When does it happen in a project?

The requirements milestone happens at the beginning of a project and then teams iterate on the vision and scope deliverables constantly. Every time they perform a round of discovery, the vision, scope, and requirements evolve and need to be adjusted. Teams learn new things in research that shift their understanding of the problems they should be solving in MVP and MMP.