Project Requirements Template
Last updated: 12/8/21
This document is a fork of the Dev Guild Project Requirements structure. This document should help anyone both Scope + Execute a major project.
Ready for adjustments necessary to meet the Analytics Guild requirements.
Project Phases - Per deployment:
- Scoaping
- Meet with Stakeholders
- Find requirements
- Identify release details
- Marketing?
- Writing?
- Advertising?
- Identify MVP
- Prioritize requirements
- Trimming requirements as needed
- Estimate time efforts
- Ensure stakeholders and dev team have a shared understanding
- Present to guild for resources - degen/welcome mat
- Coordinator
- Devs
- BANK
- In Flight
- Break up functionality into github issues
- Code
- Demo
- For sanity check
- Hype opportunity
- QA
- On going
- Deploy
- Inform release team
- Present to stakeholders
- Gather feedback
- Bug fix
- If necessary iterate back to Scoaping
In development requirements:
- Coordinator/PM
- Expectations:
- Understand the project and technical requirements
- Hold and maintain at least weekly sync's
- With Agenda and Notes (standup
- Treat first part of meet as a standup (10 min) then followed by discussion
- Discussion could be refining backlog, setting priority, resolving challenges/blockers
- Understand dev talent resource allocation
- Manage backlog in Github with devs
- Communicate expectations to stakeholders and devs
- When project is cross guild, coordinate updates to notion page/board as needed
- Dev tasks don't need to be duplicated on notion as long as github project board is linked from notion
- Dev/Technical Lead
- Devs
- Expectations
- Technically capable
- Contribute time and effort to code the project
- Participate in the weekly sync's
- Share status
- Raise issues