Task | Deliverables | Notes |
|---|
Kickoff | | |
Github repo | - project/<projectname> created (Dev Director)
| |
Project wiki | - Project wiki created (Dev Director)
| |
Epic | - Epic created for project (Dev Director)
| https://fioprotocol.atlassian.net/browse/BD-1719 |
Requirements, Design, and Scoping | | |
Kickoff meeting held with Product Manager to review requirements | | |
Complete FIP (if applicable) | -
FIP reviewed and moved to Accepted status
| N/A |
Complete functional / technical design | Design Draft should include a first draft of all elements outlined in the Development Spec. | |
Scoping | - Create project stories
- Estimate stories
| Each story should be unit of work that is deliverable in a 2 week sprint. An initial estimate should be included with every story. |
Design Review | | |
Design review | - Functional spec approved by architecture champions and team
| |
Finalize FIP | - FIP updated with any changes resulting from design review
| |
Development | | |
Scoping | - Create project stories
- Estimate stories
- Create project tracking wiki page (Dev Director)
| Each story should be unit of work that is deliverable in a 2 week sprint. An initial estimate should be included with every story. |
Development | - Ongoing scrum and progress checkpoints during development
| These will be scheduled by the development director |
Code complete | - Development branch created and initial merge completed
- fioprotocol/fio
- fioprotocol/fio.contract
- Code reviewed with dev team (thorough review of modified methods and files)
- Development Spec updated to reflect the details of the implementation
- Validate json for any new ABIs or ABIs that have been updated
| |
SDKs | - Stories created for any needed SDK updates (new getters or actions)
- SDK dev complete
- All SDK unit tests run cleanly
- fiosdk_typescript
- fiosdk_kotlin
| |
Unit Testing | | |
Unit testing | - fio.test enhanced with functional tests
- Tests run cleanly
- Functional tests well documented (in fio.test) and reviewed with team
| On project branch |
Performance testing | - First level performance testing results reviewed with architecture champions (can be performed on dev machine, try to uncover any obvious perf limits)
| On project branch |
System testing | - Tests passed to QA for system testing
| |
UAT | | |
Merge to develop and install on DEV | - Rebase feature branch and merge to develop for UAT testing
- Install release on DEV server
| |
Feature complete | - All bugs and outstanding items completed
- JS tests completed and run cleanly against DEV server
| Develop branch on DEV server |
| - Signoff from Product Management
| |
Release Plan | | |
Rollout planning | - Create rollout/release plan for this effort (added actions, removed actions, table migrations, order dependent detailed instructions on how to roll out these changes successfully. include all necessary MSIGs)
- Detailed instructions on how to verify that the rollout was performed successfully
- Review the rollout plan and verification with architecture and QA/Integration teams
| |
Devnet | | |
Devnet testing | - Work with QA/Integration to complete devnet testing
- Validate Devnet test results
| |
Testnet | | |
| | |
Test planning | - Work with release team to ensure correct Testnet rollout (addaction, setfee, contract updates, etc).
| See Release Milestone Checklist |
Testnet rollout verification | - Perform the Testnet rollout verification for the feature and report findings (add results to Dev Spec)
| |
Mainnet | | |
Test planning | - Work with release team to ensure correct Mainnet rollout (addaction, setfee, contract updates, etc).
| See Release Milestone Checklist |
Mainnet rollout verification | - Perform the Mainnet rollout verification for the feature and report findings (add results to Dev Spec)
| |