# Development Milestone ## What is it? The Development milestone is like building the first version of a new video game. The team works on creating the game's look and feel (Front-End Coding), making sure the game runs smoothly behind the scenes (Server-Side Coding), and setting up the rules and connections (Creating REST APIs, Technical Architecture Creation, Entity Relationship Creation). They also write down how everything works (Documenting Code) and make sure the game can be played on different devices (Deploying Code). Finally, they add special features like secure trading (Blockchain Coding). The end result is a playable version of the game, complete with instructions and special features (Code, Coding Documentation, API Library, Smart Contracts). ## Why is it valuable? The value of this milestone is huge for teams and products. For teams, it means they have a working version of their project that they can test and improve. It helps them see what works and what needs fixing. For products, it means they have something real to show to users and get feedback on, which is super important for making the final version even better. ## Who’s involved? {% hint style="info" %} 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](/agile-training-portal/agile-handbook/agile-teamwork/day-to-day-on-an-agile-team/daily-life-on-agile-teams.md)". {% endhint %} The following duties are involved in this milestone. These duties are performed by anyone who commits to them on a cross-functional team. 1. User experience design [duty](/project-portal/project-success-handbook/project-components/project-duties.md) 2. User experience writing [duty](/project-portal/project-success-handbook/project-components/project-duties.md) 3. User experience strategy [duty](/project-portal/project-success-handbook/project-components/project-duties.md) ## When does it happen in a project? The experience design milestone happens after teams iterate on the vision and scope milestone deliverables. Every time they perform a round of discovery, the experience design, 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. This will cause experience design deliverables to constantly shift and be worked on in a project that's working in the [Agile Ways of Work](/agile-training-portal/agile-handbook/agile-philosophies/agile-ways-of-work.md). ## What deliverables are involved? 1. UI designs 2. Component libraries 3. Design systems 4. Editorial style guides 5. Customer experience maps 6. Interaction design 7. Sitemaps ## Types of Projects That Complete the Milestone Here are the types of projects that complete the milestone. Click on each of them to learn more: {% content-ref url="/pages/rrL8axHWzeoFB472tkP9" %} [Web-Based Product Projects](/project-portal/project-success-handbook/project-types/web-based-product-projects.md) {% endcontent-ref %} ## Completing the Milestone Here's the section to learn how to complete the milestone: {% content-ref url="/pages/D7GBRewS06QdDd0FHru1" %} [Completing Experience Design Milestone](/project-portal/project-success-handbook/keys-to-project-success/completing-experience-design-milestone.md) {% endcontent-ref %} ## Dashboard Reference Here's all of the information associated with this milestone on the Milestones Dashboard. {% embed url="" %} ## Head to the Next Lesson --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://guide.techfleet.org/project-portal/project-success-handbook/project-components/project-milestones/development-milestone.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.