Tentative Milestone Scheduling

❗ This plan might change after the elicitation meeting ❗

Tentative Milestone Scheduling

Our app has 8 main features, described in detail in the Requirements Document. These feature will be implemented through three stages:

1. Interfaces

   • Design is completed
   • Endpoints are determined
   • UI components are outlined

2. Viable

   • The feature can be used in the app
   • Only partial functionality works
   • Still demonstrates the main purpose of the feature

3. Complete

   • All requirements for the feature are fully implemented
   • Feature is stable and ready for production use

---

Milestone Schedule

📌 2 October — Requirements Milestone

• After customer meeting:
  • Fix requirements after elicitations
  • Update other milestones accordingly
• Deliverables: Updated SRS, Updated Design Schemes

---

📌 21 October — Initial Release

(Team processes, repo, revised requirements, design, deployed basic app)

• Fix bugs from latest implementation
• Bug search for features 1.1, 1.3, 1.4
• Update frontend design according to new requirements
• Deliverables: Repo

Feature Progress:

• ✅ Complete: 1.1, 1.4, 1.7
• 🟡 Viable: 1.2, 1.3, 1.8
• 📝 Interfaces: 1.5, 1.6 (detailed design)

---

📌 25 November — MVP

(Main functionality implemented according to good development practices, repo up-to-date)

• Fix bugs from previous milestone
• Deliverables: Repo

Feature Progress:

• 🟡 Viable: 1.2, 1.5, 1.6 (interface)
• ✅ Complete: 1.3, 1.8

---

📌 16 December — Final Release

(Everything implemented & stable)

• Fix bugs from previous milestone
• Deliverables: Repo

Feature Progress:

• ✅ Complete: 1.2, 1.5, 1.6 (interface)

---