Sprint 3 Planning Meeting - (Meeting 10)

Date: 15-Oct-2019

Photo

Sprint 2 Retrospective - (Meeting 9)

Date: 11-Oct-2019

Photo

Sprint 2 Review (Meeting 8)

Date: 11-Oct-2019

Photo

Preparing to Sprint 2 Review (Meeting 7)

Date: 11-Oct-2019

Photo

Sprint 1 Review meeting (Meeting 6)

Date: 1-Oct-2019

Photo

Feedback from the PO

The feature in first priority is a search box, but we did some work not in the highest priority. we can simulate other things and get the first priority done. If there is nothing deliverable done in a sprint, that's fine but just let the PO know.

What we learned from Jim on this review meeting

• The main purpose of sprint meeting is to get feedback from PO

  • Show PO the product, ask him questions and let him talk.
  • Get feedback on what we have done

• Don't surprise the PO. Update with Peter promptly and tell the truth

• Purpose of this project: This is not about making SERLER, it's about learning how to work together/make decisions. Make mistakes and learn.

• Sprint goal need to be precise

• The Agile way:

  • implement a minimum product first and deliver something more in each sprint
  • value working product than document
  • think deeper

• For the incoming sprint:

  • Estimate how much can be committed. The final marking is primarily based on how much you delivered among you committed.
  • use data you got from the last sprint
  • unit test
    • understand how to do testing
    • testing is as important as coding
    • testing as documentation.

Sprint 1 retrospective meeting (Meeting 5)

Photo

Preparation to Sprint 1 Retrospective (Meeting 4)

Date: 27/09/2019

Agenda

1. Check what has done
2. Prepare the plan of presentation

Photo

Meeting 3

Date: 26/09/2019

It was an incomplete meeting. Only Chris and Oleg attended. The discussion was mostly dedicated to architectural aspects.

Meeting 2

Date: 10/09/2019

Agenda

1. Complete the Team Agreement
2. Documenting the work on the projects
3. User Stories workflow from gathering to implementation
4. Check and discussion of the state of pre sprint tasks
5. Timetable / Roadmap

Result of the meeting

• The Team Agreement is finished. We have detailed discussed all the points and defined the whole workflow. The Team Agreement is uploaded to the Wiki.
• We have defined the face-to-face meeting schedule. Meeting on the day before sprint review, meeting on the day of sprint review. Discussion every week after the lecture on Tuesday.
• As a system for collecting artefacts and documenting the work on the project, we will use the GitHub Wiki. All the documents have to be stored there.
• We have decided to move from Facebook Messenger to Slack for communication.
• All discussions of the tasks have to be open on Asana in task-related conversations. For other questions, we will use Slack.
• User Stories workflow has been defined. All team members will place new stories in Backlog individually. Task allocation to sprints has to be done only in collaboration. All priority must be got from the product owner. Assigning the task can be accomplished individually.
• We will use Asana task coloured tags to indicate priority.
• It was allocated responsibilities for pre sprint tasks. Also, all the deadlines were defined.
• We have realised that the road map of the project is slightly controversial. It needs to discuss with Jim.

It needs to be done

• All members need to set up Slack
• Develop a priority tag colour scheme for tasks on Asana. Place the scheme to the Wiki.
• Ask Jim about tasks in the backlog. Can we move them to sprints or we have to copy.
• Create the timetable page on the Wiki.

Our current task list on Asana

We are preparing to Sprint 1

The starting point of Asana project

Date: 07/09/2019

Team: Yellow Spotted Lizard (Team 9)
Project: SERLER-Lizard
Link: https://app.asana.com/0/1136831484934843/list

The first meeting

Date: 23/08/2019

Meet: Yellow Spotted Lizard (Team 9)