6 posts tagged with "Goals"

From: 28/11/2022

To: 18/12/2022

Scrum Master: João Reis Product Owner: João Farias

Developers: Artur Romão, Mariana Rosa, Ricardo Rodriguez

Sprint Planning​

These sprint will be the final sprint.

User story:

• As Alexandre, I want to store CCTV footage of the intrusion, so that I can use that information as legal proof and serve it to the client (13 story points)

• As Alexandre, I want to know my clients information, so that I can be in contact with them whenever I need. (3 story points)

The goals will be:

• Connect everything (AWS) and deploy them;
• More focus on documentation;
• Fix some bugs;

Story Points Estimated: 16

Sprint Review​

This sprint was the best until this point. The team worked really well to delivery to the stakeholders what they wanted. The stakeholders gave a positive review.

Story Points Delivered: 16

Sprint Retrospective​

• What went well? The sprint itself, the team was really focused and motivated to delivery the User Stories

• What could be improved? Nothing.

• What went badly? A lot of AWS problems, in the next sprint we will try other solutions.

Burndown Chart​

From: 14/11/2022

To: 28/11/2022

Scrum Master: Ricardo Rodriguez

Product Owner: João Farias

Developers: Artur Romão, João Reis, Mariana Rosa

Sprint Planning​

In these sprint the group will focus on these two User Stories:

• As Alexandre, I want to be responsible for adding the cameras and sensors that were installed into the system so that a new client that wants to protect his new business can be satisfied. (2 points)

• As Teresa, I want to login in my account, so that I can access my dashboard (2 points)

• As Teresa, I want to store CCTV footage of the intrusion, so that I can use that information as legal proof the moment I make a complaint to the police. (2 points)

• As Teresa, I want the light and sound alarms to be automatically triggered, if an intrusion is detected, so that I can keep my business safe and avoid robberies. (2 points)

In the fourth sprint we were expecting to complete the following user story from the previous sprint: "As Teresa, I want to be notified when an intrusion occurs in my business, so that I can allow myself to be more comfortable and feel safe about my investment."

To do so we need to have this Sprint Goals:

• IDP Login
• Add properties, cameras, sensors on the dashboard Client and Manager UI
• Trigger these equipments in case of intrusion
• Deploy Microservices

Story Points Estimated: 8

Sprint Review​

This sprint was the best until this point. The team worked really well to delivery to the stakeholders what they wanted. The stakeholders gave a positive review.

Story Points Delivered: 8

Sprint Retrospective​

• What went well? The sprint itself, the team was really focused and motivated to delivery the User Stories

• What could be improved? Nothing.

• What went badly? A lot of AWS problems, in the next sprint we will try other solutions.

Burndown Chart​

From: 1/11/2022

To: 13/11/2022

Scrum Master: Mariana Rosa

Product Owner: Ricardo Rodriguez

Developers: Artur Romão, João Farias, João Reis

Sprint Planning​

In the third sprint we were expecting to complete the following user story from the previous sprint: "As Teresa, I want to be notified when an intrusion occurs in my business, so that I can allow myself to be more comfortable and feel safe about my investment." (5 points)

To do so we need to have this Sprint Goals:

• To Finish API Sites Management
• Store Intrusions in DataBase, when HDM detects it
• Intrusion API communicate with Notifications API, through API Gateway
• Intrusion API asks for video frames to camera API and this module answers through rabbit mq
• Intrusion API joins the received frames in a video and send it to AWS S3.

Story Points Estimated: 5

Sprint Review​

This sprint was not one of the bests, multiple reasons why. However, the fact that the API Sites Management was practically done was a great thing and the two API can already communicate and send video to AWS.

Story Points Delivered: 0

Sprint Retrospective​

• What went well? Important goals reached.

• What could be improved? Better time management.

• What went badly? The team had a lot of other work from other courses.

Burndown Chart​

From: 24/10/2022

To: 31/10/2022

Scrum Master: Artur Romão

Product Owner: Mariana Rosa

Developers: João Farias, João Reis, Ricardo Rodriguez

Sprint Planning​

In the third sprint we were expecting to achieve these goals:

• User story 1: As Teresa, I want to login in my account, so that I can access my dashboard; (3 points)
• User story 2: "As Teresa, I want to be notified when an intrusion occurs in my business, so that I can allow myself to be more comfortable and feel safe about my investment." (5 points)
• Focus more on the client side and backend;
• Communication flow between Camera API, Intrusion API and HDM;
• Client UI with access to create and login account (without IDP yet), check his intrusions and profile page.

Story Points Estimated: 8

Sprint Review​

Stakeholders appreciated that we were delivering user stories, however we need to be more efficient.

Story Points Delivered: 3

Sprint Retrospective​

• What went well? Client side pretty much developed.

• What could be improved? Even the work in the team.

• What went badly? Nothing serious.

Burndown Chart​

From: 17/10/2022

To: 24/10/2022

Scrum Master: João Reis

Product Owner: João Farias

Developers: Artur Romão, João Farias, Mariana Rosa

Sprint Planning​

In our second week of development, the actual first sprint, the goals are the following:

• User story: "As Teresa, I want to check on my property's information" (3 points)
• Develop client's frontend
• Build Site's Management API
• Connect the two modules in order to present information to client, such as, their properties, the intrusion's history and the devices present in their properties.

Story Points Estimated: 3

Sprint Review​

Although, frontend was developed successfully, unfortunately backend module wasn't. Our modulation suffered some changes during the sprint, and we had to modulate our backend module several times which made us lost a bit of time. However, 2 of 3 goals where accomplished and the user story was delivered.

Story Points Delivered: 3

Sprint Retrospective​

• What went well? We improved from the previous sprint by splitting the tasks into smaller ones and work towards one goal together

• What could be improved? More communication between the team, we had some problems because of that.

• What went badly? Nothing serious.

Burndown Chart​

From: 10/10/2022

To: 17/10/2022

Scrum Master: João Farias

Product Owner: João Reis

Developers: Artur Romão, Mariana Rosa, Ricardo Rodriguez

Sprint Planning​

In order to start our project, it is expectable to conclude the following sprint goals:

• Configure the GitHub organization and define the Git Workflow.
• Create User Stories, Personas
• Produce a functional frontend prototype for the sites management API with some working features.
• Define, document and test the most important endpoints of the intrusion management API.
• Implement the database for the sites management API.
• Implement CI/CD for at least one of the system modules.

Story Points: 0

Sprint Review​

After the sprint review, the stakeholders advise us to take "baby steps". Our goals were too general and difficult, we should focus on the user stories. Work in a vertical way, which means, every member of the team is focused on that goal and work in all the modules (Backend, Frontend, Testing, DevOps) to deliver user stories. 3 of the goals were accomplished.

Sprint Retrospective​

• What went well? We have all now to start working (user stories prioritized, documentation, frontend prototype and the Sites Management API)

• What could be improved? Less big goals.

• What went badly? For the next sprint, we will try to go more focused in something smaller.

Burndown Chart​