Strawberry 🍓
team-strawberry - https://agilesoftwarecourse.slack.com/archives/C01E62UHTSL
Davey Wilkie - Dev Team Member
Diah Nasution - Scrum Master, Dev Team Member
Remi Oldham - Dev Team Member
Shariq (Rick) Jamil - Product Owner, Dev Team Member
William Tang - Dev Team Member
Receipt Catcher
Receipt Catcher offers a peace of mind for your purchasing habit.
For anyone who wants to know exactly where their money is going, Receipt Catcher is a mobile application that keeps track of your purchases anytime anywhere.
Shopper who needs to keep track of receipts
Member of household/business interested in optimizing personal finance
Investor / venture capitalists
Developer building the Receipt Catcher application
Tressa Jamil, Shopper
| Name | Tressa Jamil |
|---|---|
| Role | Shopper |
| Age | 32 |
| Gender | Female |
| Education | BSc Elementary Education in Special Education |
| Work | Pastor |
| Location | Colorado Springs, CO |
| Goals | Store receipts digitally |
| Quickly find a receipt in order to make a product return | |
| Shop smarter | |
| Frustrations | Storing paper receipts |
| Finding the receipt for a particular purchase | |
| Impulsive purchases | |
| Going to the store without a plan | |
| Motivations | Making healthier choices for herself and her family |
| Being frugal | |
| Going to the grocery store with a well-curated shopping list |
https://miro.com/app/board/o9J_kg1b1Ck=/
We pretended as if we could only complete one story from the backlog and decided which story that would be. We continued this process with the rest of the stories in the backlog until the backlog was fully sorted and ordered. During this process we considered the value each story would bring to the stakeholders as well as dependencies between stories.
For each PBI it must have:
-
A size estimate
-
Summary of work to be done
-
Acceptance criteria
-
Prerequisites defined and completed
-
A title
We used Affinity Group Sizing to estimate the size of the stories and pointed them using the number sequence provided in the Miro Planning Poker tool. Everyone in the Strawberry team is a development team member so we were all involved in estimating.
Details of First Sprint can be found in PREVIOUSREADME.md file
Details of Second Sprint can be found in PREVIOUSREADME.md file
The forecast for the third sprint is 19 story points.
We forecasted 19 story points because: The team felt confident that they would be able to complete this number. Another consideration was that there was at least one story that was carried over from the previous sprint, which was almost completed.
Evidence can be found in the recording below starting at minute 02:00. a link
Evidence can be found in the recording below starting at minute 03:00. a link
Evidence can be found in the recording below starting at minute 16:00. a link
- Our Sprint Backlog is represented in a Kanban board in Miro.
- The URL to Miro is: https://miro.com/app/board/o9J_kg1b1Ck=/
- Richard helped set the board and by virtue of access should be able to view the URL above.
- We have a Sprint Burndown Chart located above the image of a Strawberry on our Miro board: https://miro.com/app/board/o9J_kg1b1Ck=/
- The x-axis represents dates of the sprint by day.
- The y-axis represents story points remaining to be done.
- A linear curve is present descending from left to right.
- The URL to the burndown chart is: https://miro.com/app/board/o9J_kg1b1Ck=/
- Richard helped set the board and by virtue of access should be able to view the URL above.