SCRUM

Scrum is an Agile project management methodology that allows for rapid development and
testing, especially within a small team. These teams are led by a Scrum master, whose main job
is to remove all obstacles to getting work done. Work is done in short cycles called sprints, and
the team meets daily to discuss current tasks and any roadblocks that need clearing. It I similar to
Rugby game

Scrum master
The Scrum master is also responsible for:
● Facilitating communication and collaboration among team members
● Ensuring the team remains focused on their goals
● Bridging the gap between Agile and Scrum practices
● Promoting a culture of continuous improvement
● Collaborating closely with the product owner

Agile Scrum methodology phases

The scrum models have 5 steps also called phases in scrum.

Step 1: Product Backlog Creation

In this step, the large items and functional details are transformed into epics and user stories. The
user stories are transformed from large items and are smaller which can be put in the product
backlog. The epics can also be included in the product backlog but cannot be included in the
sprint backlog without converting it to a user story. A typical user story example is as an admin I
want to add, modify, and delete the tasks for the users in the website. The following required
fields in the user stories are necessary.
● The user stories significance
 ● The initial estimate made during the meeting
● Demo of how to make the user stories into tasks

Step 2: Sprint planning and creating backlog

The sprint duration is very important so that the user stories are as small as possible. The typical
average sprint duration lasts about 2 weeks. If the sprint duration is small than the advantage is
that more customer feedback can be received and most of the errors and bugs can be addressed
earlier. If the sprint duration is long then it allows the developer to work thoroughly.
The next stage is to do the sprint backlog creation for which the scrum team must select the
important user stories and make them into smaller tasks. They need to plan on how to get the
task completed. Also, one important thing is to prioritize the necessary tasks. StarAgile conducts
CSM certification online training for the professionals aspiring to become a certified scrum
master.

Step 3: Working on sprint

The actual user stories are moved as small tasks in the sprint backlog where the actual work
starts. This is where the realization of the software application for example the website
development begins. To begin with, a task board also called a Kanban board is made with a lot of
cards is used. The cards specify the details about the tasks such as assignee, work details, due
date or the time duration, etc. The task board consists of the following columns "Product backlog
or the User stories", and the "To Do" lists, "Work In Progress" and then "Testing" and "Work
Done" columns.The cards can be moved from the left to right in the order of preference and
based on the completion. The task board is explained thoroughly in the Scrum master
certification training online at StarAgile institute. Instead of a physical chart, you can have the
digital chart prepared in the computer using the software such as Jira, Trello, Kanbanize,
Monday, etc
In this step the scrum meetings are important as it is done to track the progress status and who is
doing what status. The burndown chart is the output of this meeting as it provides the details
about how many tasks are completed and if there any issues or problems in completing the tasks
in the "Work In Progress" columns.

Step 4: Testing and Product Demonstration

The tasks completed are to be realized as a working product with full life cycle testing. The
testing cost can be minimized with the addition of QA or having fewer user stories, however, the
first one is the best possible solution. Every sprint that is completed must be demonstrated to the
customer for his acceptance and his viewpoint on the complete solution

Step 5: Retrospective and the next sprint planning

The result of this step is to discuss what went well and what can be improved for the next level.
Also, you need to discuss the lessons learned and the pitfalls of any particular issues or problems.
Then the next sprint planning has to be commenced based on the knowledge that we have for the
current processes and past projects. StarAgile conducts Certified scrum master online training for
the professionals.
Scrum Process
There are 3 groups of Scrum processes namely pregame, game, and post-game.

1) The first phase is the pregame phase which deals with the planning and architecture of the
project. The planning is done with the creation of the backlog and list of activities that must be
done for breaking down the epics into smaller user stories to make the product backlog. Also, the
user stories are made into tasks in the sprint backlog stage.

2) The game phase is the second phase in the scrum phases.

It is where the actual work is accomplished. Here each task assigned to the resource is started
and completed with the definition of done. There 4 steps to accomplish the tasks,
● Develop the sprint backlog and then start the development, testing and documenting
changes, etc
● Close the work status
● Conduct review meetings
● Make the changes required for the definition of the done.

3) The post-game phase is the last in the scrum phases.

● The development phase is ended and the products are prepared for the release. All the
necessary steps such as testing, integration, training, user documentation, and marketing
materials are released.

Scrum Principles for Project Success

1. Transparency
2. Inspection
3. Adaptation

1. Transparency
The first pillar of Scrum is transparency. This means that all aspects of the project — such as
progress, issues, and risks — should be visible and accessible to everyone involved.
Transparency is an important part of Scrum management, as it ensures that all members of the
team are on the same page throughout the project.
Transparency is achieved through the use of Scrum artifacts. This includes:

● Product backlog
● Sprint backlog
● Burndown chart
●
By making information transparent, the team can work more collaboratively and make better-
informed decisions. However, transparency isn’t just about providing access to information; this
information must also be accurate and up to date.
2. Inspection
The second pillar of Scrum is inspection. This involves regularly reviewing the progress of the
project, including the product increment delivered at the end of each sprint. By inspecting the
work done, the team can identify any issues and address them promptly. Inspection is also
important because it enables teams to:

● Verify the project is on track

● Learn from mistakes
● Make necessary improvements for the future
Inspection is not just a one-time event but a continuous process that occurs throughout the
project’s lifecycle. By regularly reviewing progress, the team can adapt to changing
circumstances and make adjustments to their approach as needed.

3. Adaptation
The third pillar of Scrum is adaptation. This means the team must be willing to make changes
based on the results of their inspections. By adapting their approach as necessary, the team can
continuously improve their processes and deliver better results. Adaptation is critical in Scrum
because it ensures the team is always working towards the most efficient and effective way of
delivering their product or service.
This process requires:
● A flexible mindset
● A willingness to experiment during each iteration
● Openness to feedback gathered during the daily Scrum
● A commitment to making changes based on what has been learned

Scrum Values for Project Teams

● Commitment: Members of the Scrum Team are devoted to finding the best solution through
continuous improvement and time-based tasks and goals.
● Courage: By posing direct, difficult questions, Scrum Teams demonstrate bravery. To find
the best answer, they have frank and open discussions.
● Respect: The Scrum process, the project managers, and each other are respected by the team
members. Within the team, this respectful culture fosters a sense of cooperation and mutual
support.
Scrum vs. Agile: Differences and similarities
Agile is a broad approach to project management that emphasizes flexibility, collaboration, and
continuous improvement. Scrum is one specific implementation of the Agile approach, focused
on delivering projects in short, iterative sprints.
One of the main differences between Scrum and Agile is that Scrum involves a more defined set
of roles, artifacts, and ceremonies than the broader Agile approach. Scrum also places a greater
emphasis on planning and tracking progress through the use of tools such as the sprint backlog
and burndown chart.
Despite these differences, Scrum and Agile share many similarities. Both approaches prioritize
collaboration, transparency, and continuous improvement. Both are designed to help teams work
more effectively together, and both are focused on delivering high-quality results in a timely
manner.