Proposed Project Planning Cycle
Below is the proposed roadmap we will use for the planning of DNA.
User stories will be gathered by those working in Production coordination. They should include the tasks the users need to complete and why. For example "As a blank I need to blank because/so I can blank"
More info and user stories can be found here: https://github.com/AcademySoftwareFoundation/dna/wiki/Note-Taking-Workflow-Breakdown#user-story-and-flow-without-dailies-notes-assistant
At this stage, we develop prototypes the satisfy the user stories. This helps us understand the user stories better and gives us an idea of the features and backend that will be needed. Most/All of the code may be throw away. The idea at this stage is to move fast and design an app that will help guide us in the system design and the ticket creation.
Example Wireframe: In the case blocks are used however this can also be screenshots from the prototypes
After we have a good idea of what the app will look like and the features we will be including, it is time to write the design document! This should include the following:
- Overall Goal for the project
- Descriptions of high level features
- Descriptions of existing systems that will be used
- Descriptions of systems that will need to be build
- How these systems will talk to each other
- The stack of each of these systems
- Data models if needed to describe how data passes between the systems and how it is stored
After the design doc is written and appropriate feedback is given, the work will be broken down. Leads can be designated for each of the higher level systems. Lead can then break down the work to build each of the higher level systems. Within tickets, the following should be included.
- Description of the task
- Acceptance criteria for the task
- Blocking work referenced and if supported, dependencies added.
- Links to any relevant code or documentation
