Scrum and Scrum metric

Scrum is an agile methodology that provides a framework for planning, organizing, communicating, committing, and tracking work over time. It helps them deliver value early and continuously by breaking down large projects into manageable pieces (called "sprints"), which can be completed within a few weeks or months.

The Scrum Process Relies On The Following Three Principles:

• A cross-functional team of self-organizing specialists works together closely throughout the entire life cycle of a product or service.

• A time-boxed iterative approach to managing work with regular opportunities for feedback and course correction.

• An emphasis on working software as the primary measure of progress.

Elements Of Scrum

• Product backlog - A product backlog is a list of potential features, enhancements, and improvements that can be added to an already existing product. Many companies have a backlog because it's difficult to predict what will happen in the future. The purpose of having a product backlog is for managers to prioritise and rank items on the list to decide when they should be implemented into the company's products.

• Sprint backlog- The sprint backlog is a vital tool for the scrum team to use when planning and executing work. The sprint backlog lists all of the tasks that need to be completed and helps everyone on the team stay informed about what needs to get done.

• Product increment- Product increment is a term that refers to the process of adding new features and enhancements to an existing product. Incremental updates can be made in two ways: making small changes between releases or releasing smaller versions more frequently.

Scrum Team

A scrum team is a group of people dedicated to achieving an objective within a specific time frame. The work is divided into sprints, each with its timeline and goals. Within these sprints, the work required for the project is broken down into tasks and carefully planned by all scrum team members. Scrum teams are self-manageable and cross-functional instead of following a structural hierarchy. Each team member is essential and together has the skills and contributes to accomplishing a project. The following are the different roles in the Scrum team:

• Product owner- A product owner is a crucial person in the scrum team. They are responsible for ensuring that the needs of customers and users are met by creating products that generate revenue or reduce costs. The product owner's role is to provide direction for what should be built, which should be implemented first, and prioritize work among backlogs.

• Development team- They are responsible for developing and implementing the product that meets the customer's needs, which is different from the traditional view in which developers write code according to specifications. The members of this team are often called developers or engineers. They typically work in small groups, with one or more programmers to design and implement the feature set requested by the product owner and other stakeholders.

• Scrum Master- The Scrum Master is responsible for ensuring that the team (and their process) stays on track. This person will help to ensure that the team has everything they need to be successful and productive. They are also in charge of removing any obstacles or problems that might get in the way of success. The role of a Scrum Master can vary depending on the needs of the project or company. In some cases, they are responsible for leading specific projects. In contrast, in others, they may be part of an organization's leadership team responsible for ensuring that all teams work together efficiently to meet goals faster than ever before.

Application Of Scrum

The scrum process relies on the following three principles:

• A cross-functional team of self-organizing specialists works together closely throughout the entire life cycle of a product or service.

• A time-boxed iterative approach to managing work with regular opportunities for feedback and course correction.

• An emphasis on working software as the primary measure of progress.

Elements Of Scrum

• Product backlog - A product backlog is a list of potential features, enhancements, and improvements that can be added to an already existing product. Many companies have a backlog because it's difficult to predict what will happen in the future. The purpose of having a product backlog is for managers to prioritise and rank items on the list to decide when they should be implemented into the company's products.

• Sprint backlog- The sprint backlog is a vital tool for the scrum team to use when planning and executing work. The sprint backlog lists all of the tasks that need to be completed and helps everyone on the team stay informed about what needs to get done.

• Product increment- Product increment is a term that refers to the process of adding new features and enhancements to an existing product. Incremental updates can be made in two ways: making small changes between releases or releasing smaller versions more frequently.

Scrum Team

A scrum team is a group of people dedicated to achieving an objective within a specific time frame. The work is divided into sprints, each with its timeline and goals. Within these sprints, the work required for the project is broken down into tasks and carefully planned by all scrum team members. Scrum teams are self-manageable and cross-functional instead of following a structural hierarchy. Each team member is essential and together has the skills and contributes to accomplishing a project. The following are the different roles in the Scrum team:

• Product owner- A product owner is a crucial person in the scrum team. They are responsible for ensuring that the needs of customers and users are met by creating products that generate revenue or reduce costs. The product owner's role is to provide direction for what should be built, which should be implemented first, and prioritize work among backlogs.

• Development team- They are responsible for developing and implementing the product that meets the customer's needs, which is different from the traditional view in which developers write code according to specifications. The members of this team are often called developers or engineers. They typically work in small groups, with one or more programmers to design and implement the feature set requested by the product owner and other stakeholders.

• Scrum Master- The Scrum Master is responsible for ensuring that the team (and their process) stays on track. This person will help to ensure that the team has everything they need to be successful and productive. They are also in charge of removing any obstacles or problems that might get in the way of success. The role of a Scrum Master can vary depending on the needs of the project or company. In some cases, they are responsible for leading specific projects. In contrast, in others, they may be part of an organization's leadership team responsible for ensuring that all teams work together efficiently to meet goals faster than ever before.

Application Of Scrum

• Sprint planning meeting- The meeting is held at the beginning of each sprint to discuss the tasks that need to be completed. The product owneprioritizeses the items that need to be completed, and the team determines what actions (i.e., how) will be taken to implement the tasks. Deadlines are set and reviewed to ensure the team has sufficient time to complete the tasks requested in the sprint. Lower priority features go back to the product backlog to ensure the workload is enough to obtain the team's commitment if the group is not committed.

• Track progress- Once the sprint meeting is completed and the team begins to work on their tasks, their progress is tracked using tools like a burn down chart and task board. The task board consists of columns like to do, do, done. Teams will move their tasks across the board and have their meetings regularly to share the status and discuss any obstacles or issues. the burn-downtown chart consists of a trend line of work left to do in the sprint. The x-axis represents the number of days, and the y-axis represents the number of hours for all tasks. As the days pass by, the number of hours left should trend down to zero.

• Sprint review- Once the sprint cycle is completed, the stakeholders join the sprint review meeting to see a demo and share feedback. The product owner incorporates any changes requested into the product backlog. Once the stakeholder review is completed, the team shares their feedback on what went wrong and suggests any changes that need to be done. The changes are documented and implemented throughout the next sprint.

• Release planning- Release planning is a method to do long-term planning that contains multiple sprints. The release planning meeting is conducted quarterly by the product owner. The goal of release planning is to provide visibility into what will be done and when it will be completed during the next period. The team determines what features need to be completed at the end of the sprint and estimate the time, and budget required to complete the tasks.

User Guide:

• The data of the sprint velocity chart in the summary tab lies in the main sheet of story points(delivered) and story points(committed) column.

• The data of the burndown chart lies in the tracker sheet, the chart goes down as the tasks get completed.

• The percentage completed pie chart shows the percentage of tasks completed shown in the status and % completed column

• The incomplete tasks donuts chart shows the pending tasks and their priority.

• The sprint duration is calculated from the difference between the start and end date. Any changes to be made in the sprint duration should be made by changing the start or end date.

• In the tracker sheet, the day in the completed column is calculated by taking the sum of the days in the timeline. The pending column is calculated by subtracting the estimated story points and completed tasks.

• The burndown is calculated by subtracting the total estimated story points and the total number of days to complete the tasks.