Sprint Meeting Notes

note: replace anything surrounded by << >> and remove the << >>

Attended: Spencer Powell

DATE: << meeting date >>

Sprint 3 Review

SRS Sections Updated

requirements

User Story

arguably the initial story

Sprint Requirements Attempted

Archetecture Diagram completion

Completed Requirements

Client and server now share a language although the plumbing between them isn't setup yet
server now determine's stops for a "route" although those stops aren't related to the response given by /path due to them not considering bus directionality

Incomplete Requirements

Depends on how you interpret the requirements and completing them, ultimately it was determined that picking a somewhat useful route was a bigger requirement than expected however the naive algorithm which ignores bus directionality was implemented but not connected to the actual API due to being fundamentally unfit for purpose

The summary of the entire project

Things are almost coming toegether into a state where we can show something but getting useful functionality will probably be pushed back a few weeks

Sprint 4 Planning

Requirements Flex

3/5 requirement flexes remaining

Technical Debt

Requirement Target

Display routes or display routes (changed from text based simply giving back info retrieved from api to actually using google maps)
decide on representation of graph and graph representation of the bus systems and create nodes in the representation of the graph for the graph representation of the system

User Stories

Initial user story

Issues and Risks

Graph representation will probably need to be complicated

Team Work Assignments

Levi will setup the client to use google maps instead of just displaying text
Spencer will figure out the representation of the graph and graph representation of the system

1.9 KiB Raw Blame History