Sprint 1 - Review Notes:

[Nintails-TF]

From the Marking Rubrik, we are being marked on:

• Welcoming of customers and setting scene for the sprint review
• Overview of what will/will not be demonstrated in the sprint review
• Demonstration of new functionality
• Discussion of key events or problems that occurred during the sprint
• Present upcoming product backlog items
• Conclusion of the meeting

1. Welcoming of customers and setting scene for the sprint review

• Introduce our Front-End team (Kyle & Alba)
  • Worked on the website, using html & tailwind
• Introduce our Back-End team (Lewis & Lucca)
  • Worked on some API stuff with JS, as well as DevOps
• Introduce our API/DB team (Ben & Finnbar)
  • Worked on the database, as well as API using JS

2. Overview of what will / won't be demonstrated in the sprint review

• Discuss what we planned to take into sprint 1
• What has been completed, and will be demonstrated
• What has not been completed, and won't be demonstrated

3. Demonstration of new functionality

• Front End demonstration

  • show off website, with leafletJS and geo-location ability
  • show filters

• API demonstration

• Back End demonstration

4. Discussion of key events or problems that occurred during the sprint

• Sprint 1 - Retrospective #18
• Should have spent more time deciding what we were going to take into Sprint 1 before beginning development
• In Sprint 2, we will spend time doing T-Shirt sizes before we begin tackling issues
• Talk about sickness and show that because people where ill, we had to adapt our aprroach to 50:50 in person/remote. This highlights that we are adpatable and resilient to unforseen circumstances.

5. Present upcoming Product backlog items

• Making our project more accessable and making sure it abides by WCAG.
• logging into the database, making edits.
• We are going to include searching by street names as well as user location.
• POTENTIALLY some filtering options.

6. Conclusion of the meeting

• A summary of the above points
• What we're happy with in the Sprint
• Any changes to our plans for next Sprint
• What we're taking into the next Sprint

[Nintails-TF]

Summary of Alex's Client Meeting Notes:

• We don't want to pull the whole data set from our API to the front-end. Since this is expensive for API calls and will make the front end slow.
• NCR showed an interest in dynamically loading our data depending on the search radius, rather than showing all ATMs/Branches at once.
  • We could implement a default range (20 miles from location) then only show branches/ATMs in that radius
  • We could change our filter from 1-"everything" so that customers could still access the larger data set.
• Having a legend for our markers on the front-end would be nice too.

Summary of Mike's Client Meeting Notes:

• Focus more on the user stories and try to give a better overview of them. Talk about them more during the sprint review.
• Stick more to the user stories and focus on how you are bringing value to the client.

Front-end:

• We spoke alot about web app functionality, rather than value for the customer.
  • We want to focus on why the web app is useful to the customer rather than what the web app does.
• Our map front-end looked nice.
• The filter's weren't working - we shouldn't bring unfinished items into sprint reviews.
• Asking questions towards the client is really good - make sure to clarify things that are confusing and note things down.
• Dummy list shouldn't of been brought in, same as filters.
• Client asked what do the blue/grey dots mean, we could include a legend or talk about icons for branches/ATMs.
• Returning to the user story once more after we have introduced the front-end.

Back-end:

• When talking with some clients, they won't understand some of the terminlogy we used here. (e.g. microservices, DevOps, CORS, MERN, merge conflicts), etc.
  • We need to focus on how we can bring value to the customer.
    • Could be a good idea to focus on what the customer wants and how we can meet those wants.
  • We did talk about important stuff, but it was very developer to developer talk.
  • We talked about some reflective aspects of the team. This isn't ideal to do in the sprint review. As real companies wouldn't hire your team if it wasn't already high-performing, so just watch out to not do this.
  • Questions and feedback was good here but was very technical.
  • We impressed the NCR which is great work.

API / Database Team:

• Discussion was very technical about the implementation of our JSON into DB. Hosting our server using express, hosting options.
• Good idea to talk about redocly and swagger, but we just want to relate this a user story.
• Problems of not having routes from back-end is likely the result of not following user stories.

Product Backlog Refinement:

• Again we need to focus on value > functionality. We need to push the idea of why the things being implemented helps the client.
  • A good idea here is to bring up the full product backlog and the stories you want to take into the next sprint.
• It wasn't clear what user stories are being brought into next sprint.

Closing:

• Be careful when dealing your clients of things that went wrong - don't mention sprint problems - since that is a retrospective task.
• Push the value of what you are doing more.
• Try to talk with the clients more.
• We did impress the clients with what we have technically done.
• The sprint review was good, but could of been better. We got a little too technical at times.