72 lines
1.4 KiB
Markdown
72 lines
1.4 KiB
Markdown
# Sprint Meeting Notes
|
|
|
|
*note: replace anything surrounded by << >> and **remove** the << >>*
|
|
|
|
**Attended**: << record the team members in attendance (virtual counts as long as they are participating) >>
|
|
|
|
**DATE**: << meeting date >>
|
|
|
|
***
|
|
|
|
## Sprint 3 Review
|
|
|
|
### SRS Sections Updated
|
|
|
|
|
|
requirements
|
|
|
|
### User Story
|
|
|
|
arugably the initial story
|
|
|
|
### Sprint Requirements Attempted
|
|
|
|
- Archetecture Diagram Missing
|
|
|
|
### Completed Requirements
|
|
|
|
- Data format conversion for a single bus system
|
|
|
|
### Incomplete Requirements
|
|
|
|
The path from point to point is in the form of 3 stops instead of
|
|
|
|
### The summary of the entire project
|
|
|
|
<< A general overview of the entire project >>
|
|
|
|
***
|
|
|
|
## Sprint 4 Planning
|
|
|
|
## Requirements Flex
|
|
|
|
3/5 requirement flexes remaining
|
|
|
|
## Technical Debt
|
|
|
|
<< Any requirements from the previous sprint that are using a technical flex >>
|
|
|
|
### Requirement Target
|
|
|
|
<< The corresponding SRS requirement that our team will be complete in next sprint >>
|
|
|
|
### User Stories
|
|
|
|
<< Corresponding User Stories >>
|
|
|
|
### Planning
|
|
|
|
<< Our team's detailed plan to complete the sprint >>
|
|
|
|
### Action Items
|
|
|
|
<< A list of things that need to happen in our for our team to complete the sprint >>
|
|
|
|
### Issues and Risks
|
|
|
|
<< A list of potential obstacles that could keep us from completing the sprint and what's being done about them >>
|
|
|
|
### Team Work Assignments
|
|
|
|
<< A list of each team member and their works assignments for this sprint >>
|