[29/01/24] Sprint 1 - Video Feedback Summary:

[Nintails-TF]

Introduction:

Looking through github and seeing how things went and focussing on user stories, do the follow INVEST? Are the user stories ready basically.

Looking at the product backlog to see how things are being developed - proto-personsa, definitions of done, how we are measuring them.

Looking at sprint backlog and how tasks are progressing through the sprint.

How are we using github and combining agile methods with github features.

Issues:

• Mix of user stories and developement tasks, this is good to see.
• Good usage of milestones.
• Good at pointing out the flaws of swagger and going forward with redocly.
  • This is because swagger doesn't fit OpenAPI standards.

Wiki:

• For branches, it is recommended to name branches after user stories (link issue number), then to have sub-branches that implement features from these user stories.

Sprint backlog:

• This should be everything that has been done during sprint 1.
• We have a mix of stories and activities.
  • Usually, we want to seperate these technical issues and user stories, so that the sprint backlog only has user stories.
  • This is because it is hard to see what has/hasn't been done.
• Improve user stories to mention important aspects.
  • e.g. for As a startup company, I want to use a bank and ATM API, so I can aggregate ATM and bank branch data. #9 make it clear that documentation is progressing as the product is progressing.

Issue description:

• Very good, but make sure to turn "Implementing based on design" into a task.
• The product flow is good - since we have tasks we have to do, we can look at specifiy tasks which show us meaningful code.

PRs:

• Very good to have related issue numbers and the related user story within the PRs.
• Good to have code changes, testing and documentation.
• Really, really good work here.

Discussions:

• It is possible to create burn-down charts - it helps when estimating the amount of work that can be done.
• But these are used well, keep references issues and PRs inside of them too if they would help.

Product Backlog:

• The structure of the backlog is really good.
• We don't really need to use roadmaps, but they can help for bigger projects.

Daily Standup / Scrum Meeting:

• A good thing to do during scrum meetings, is to have the project board open so that everyone can see what is happening.
  • Pull up the backlog and relate to what user-story that is being worked on.
• To speed up scrum meeting, have scrum master ask - what did you do yestarday, what are you doing today and what challenges are you facing.
• It is good to see that people are talking to each other during the standup meetings.
  • Lots of teams "zombie scrum" it and just do standups because mangement tell them to do it. By talking with each other, you can get up to speed and help each other.
• It is good to help the group and try to aid others who are stuck.

Recap:

• We are in a good place.
• User stories are good - could be worthwhile to create proto-personas and add them to user-story issues.
• Amazing usage of github.
• Everything does line up with agile principles.
• Sprint and product backlog looks good.
• Sprint reviews would be a good area to hone.