What are the key milestones you need to achieve in order to complete your project successfully?
Milestone 1: Solution Research and Product Summary Documentation (1 Month)
A: Milestone Outputs:
Feasibility research conducted to determine refined project timeline and general solution requirements. Product feature documentation outlining functional (UX/UI) and technical (backend/server) requirements to build the multi-track release functionality. This documentation will be leveraged as guidance in the next phase of UI design and the creation of the formal Product Requirements Document (PRD).
B: Acceptance Criteria:
Functional and technical overview documentation is created and made available for the project team.
C: Evidence of Milestone Completion:
Feature summary document (Google Doc, PDF).
Milestone 2: UI Design and Formal Product Requirements Document (1 Month)
A: Milestone Outputs:
Figma (or similar) UI wireframes and comprehensive designs and the feature’s Product Requirement Document (PRD), both of which will be utilized by the Product Delivery and Development teams to create development tickets and as a reference for Quality Management team members when reviewing and testing the to-be-developed feature.
B: Acceptance Criteria:
Designs and PRD are created and leverageable by Product, Development, and Quality teams for the next phase (i.e., development).
C: Evidence of Milestone Completion:
Figma files and PRD (Google Doc, PDF).
Milestone 3: Product Development (3 Months)
A: Milestone Outputs:
GitHub repository(ies) updated and feature code developed. Feature code deployed to the staging environment and ready to test on TestNet.
B: Acceptance Criteria:
Codebase and feature deployable to TestNet environment, developed to design and specification
C: Evidence of Milestone Completion:
Codebase accessible via GitHub
Milestone 4: Testing and Critical Bug Fixes (1 Month)
A: Milestone Outputs:
Feature QA and testing reports. Updated codebase with bug fixes and enhancements defined during the testing period.
B: Acceptance Criteria:
The codebase is tested and meets all requirements outlined in PRD and UI designs, all critical bugs have been resolved, and the feature is ready for Production/MainNet deployment.
C: Evidence of Milestone Completion:
Test case documentation (Google Sheet, PDF). Bug and enhancement report (Google Doc, PDF). Video of the creation of the multi-track release functionality (on TestNet) from within NEWM Studio demonstrating the feature prior to launch.
Final Milestone: Final Milestone | Closeout and Production Launch (1 Month)
A: Milestone Outputs:
Final close-out report.
Final closeout video.
Feature launched in NEWM Studio Production environment.
B: Acceptance Criteria:
Final close-out report.
Final closeout video.
The feature codebase is deployed to the Production/MainNet environment.
C: Evidence of Milestone Completion:
Final close-out report.
Final closeout video.
NEWM Studio Release Notes (Google Doc, PDF).