user story and template

etc/user_stories/initial_story.md

@@ -0,0 +1,31 @@
+# [Feature Name]
+
+## **Persona**
+
+- **Name:** Sam
+- **Relevant Characteristics:** Freshman binghamton university student who just downloaded the app
+- **Behaviors & Attitudes:** Reasonably comfortable with a phone/google maps and have little to no experience/understanding of the bus systems in Binghamton
+- **Goal:** Go from home to somewhere else in binghamton and back again
+
+---
+
+## **User Story**
+
+As a **university student**
+I want **a way to figure out good routes with buses without memorizing every bus route/stop**
+so that **I can buy groceries, go to downtown and easily get to/from the university**
+
+---
+
+## **Acceptance Criteria**
+- A route to get from point A to point B which isn't obnoxiously slow is generated
+- said route is reliable
+- route is generated within seconds (10 seconds max if possible)
+
+---
+
+## **Notes**
+- route should be reasonably fast
+- route should have reasonably low amounts of walking
+- OCCT can sometimes drop the ball on live map info leading to suboptimal routing
+- furthermore it's possible OCCT or broome county service is temporarily canceled which can cause a route to be wrong

etc/user_stories/template.md

@@ -0,0 +1,25 @@
+# [Feature Name]
+
+## **Persona**
+- **Name:** [Fictional User Name]
+- **Relevant Characteristics:** [Background, role, experience level]
+- **Behaviors & Attitudes:** [How they use technology, frustrations, goals]
+- **Goal:** [What they want to achieve]
+
+---
+
+## **User Story**
+[Write the user story using one of the approved formats]
+
+---
+
+## **Acceptance Criteria**
+- [Define the success conditions for this feature]
+- [How will we know when this is done?]
+- [What must be functional before release?]
+
+---
+
+## **Notes**
+- [Any additional considerations or insights]
+- [Potential risks or challenges]