[2.7.1] Development Milestone Checklist
- Eric Butz
The milestone checklist tracks the development tasks that need to be completed prior to moving the Epic or story into a new status
|
| Tasks | Deliverables / Notifications |
|---|---|---|---|
Links |
|
|
|
Github repo | Excluded Included | Create bug/feature branch | |
Dev Epic | Excluded Included | Create epic to track development work (may be done by project manager) | |
Requirements, Design, and Scoping |
|
|
|
Meeting - Kickoff meeting | Excluded Included | Kickoff meeting held with Product Manager to review requirements | Met with team on 4/25/22 to review hotfix. |
Complete FIP (if applicable) | Excluded Included | FIP reviewed and moved to Accepted status |
|
Complete functional / technical design | Excluded Included | Development Spec Design draft complete and saved to Development Documents (Active) Design Draft should include a first draft of all elements outlined in the Development Spec. | Since this is a hotfix, the design is included in the Jira story. |
Scoping | Excluded Included | Create project stories for development for each of the remaining tasks that are included with the release 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 development story. | Development is already complete for this fix. |
Design Review |
|
|
|
Design review | Excluded Included | Functional spec approved by architecture champions and team |
|
Finalize FIP | Excluded Included | FIP updated with any changes resulting from design review |
|
Development |
|
|
|
Project management | Excluded Included | Maintain status in Epic Summary
| |
RAM bumps for new actions | Excluded Included | Determine RAM allocation for new actions and set RAM bump accordingly. This informationshould be added to the FIP. |
|
Fees for new actions | Excluded Included | Estimate initial fees for all actions. In cases where the action requires additional RAM, the fees should be correlated with the RAM estimates. This informationshould be added to the FIP. |
|
Update FIP (or development document) | Excluded Included | FIP / development spec updated to reflect the details of the implementation |
|
ABI validation | Excluded Included | Validate json for any new ABIs or ABIs that have been updated If deploying new contract, make sure ABI copy command is in fio.devtools contracts/build.sh |
|
Code review | Excluded Included | Code reviewed with dev team | |
Unit Testing |
|
|
|
Action and getter testing | Excluded Included | fio.test test branch created fio.test enhanced with initial action and getter tests Tests run cleanly | |
Performance testing | Excluded Included | First level performance testing results reviewed with architecture champions (can be performed on dev machine, try to uncover any obvious perf limits) |
|
Release Plan |
|
|
|
Msig deployment plan | Excluded Included | Create (or add to) wiki page in Releases directory to track any msigs needed to deploy the feature | |
System Testing |
|
|
|
System testing | Excluded Included | Tests passed to QA for system testing | |
UAT |
|
|
|
Merge to release or develop and install on DEV | Excluded Included | Rebase feature branch and merge to develop or feature branch for UAT testing Install release on DEV server This is a developer task to ensure that their feature or fix is on a publicly accessible DEV server so it can be reviewed by Product Management. This should be done after system testing is complete. | |
Feature complete | Excluded Included | All bugs and outstanding items completed Work with QA to confirm JS tests run cleanly against DEV server | |
Product signoff | Excluded Included | Signoff from Product Management This is feature or bug specific signoff from Product Management so is controlled by the lead developer. | |
Devnet |
|
|
|
Devnet testing | Excluded Included | Work with release engineer to fully test any new contracts and actions. | Devnet testing is tracked in the Release Milestone Checklist |
Testnet |
|
|
|
Test planning | Excluded Included | Work with release team to ensure correct Testnet rollout (addaction, setfee, contract updates, etc). | See Release Milestone Checklist |
Testnet rollout verification | Excluded Included | Perform the Testnet rollout verification for the feature and report findings (add results to Dev Spec) | |
Mainnet |
|
|
|
Test planning | Excluded Included | Work with release team to ensure correct Mainnet rollout (addaction, setfee, contract updates, etc). | See Release Milestone Checklist |
Mainnet rollout verification | Excluded Included | Perform the Mainnet rollout verification for the feature and report findings (add results to Dev Spec) |