CodeYourFuture / CodeYourFuture/launch_module_planning
Review the current briefing process
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
**Background**
We have an incomplete Final Project Proposal form that doesn't give us enough information on this can or cannot be a good briefing for our Launch projects.
Challenge: We need to remember that many organisations don't have anyone technical, so the briefing cannot have purely technical questions. However, we need to understand if it is a full-stack development, for example.
**Tasks**
- [ ] Read the current [Final Projects Proposal form](https://docs.google.com/forms/d/e/1FAIpQLSf5n0Eigrw2RPOq9jVaVa7rHuMduRYhnwVTDQdKckLnU_rDzg/viewform)
- [ ] Identify must-have information for a new briefing proposal form
- [ ] Create a new form
- [ ] Test it with some organisation and existent briefings
- [ ] Update Curriculum
- [ ] Add it to Launch Canvas
- [ ] Retire the old form
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading the linked Final Projects Proposal form and reviewing existing briefings. Identify the must-have information, including accessible questions for non-technical organisations and enough detail to classify the work. Done means a tested new form is created, the Curriculum and Launch Canvas are updated, and the old form is retired.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100