scrum master & agile project management

Lightning Scrum Lesson to Take Note Of



Tutorial Index:

  • What is scrum and why it is effective?
  • The Scrum Master’s Role
  • The product owner’s role
  • Scrum in action
  • Transparency in Scrum
  • So how to validate things?

What is scrum and why it is effective?

Scrum is the base methodology in the Agile family. It is a highly collaborative, role based, iterative scrum master methodology for building software products that is focused on business value.  It supports a transparent development environment that enables high collaboration and validates the value added. It also helps us in managing costs and in defining problems at an early stage, thereby making it possible to provide the most potent solutions.

Scrum’s teaming, incremental deliveries, early tests, and feedback make it highly useful for building high quality software products, which schedule supports adjustment to change.

Scrum is the base methodology in the agile family, which is composed of three base roles that are designed to promote collaboration. The scrum team is basically composed of the scrum master, product owner, and the development team, which is set up to promote collaboration.

The Scrum Master’s Role

The scrum master is the owner of the scrum team artifacts. He facilitates at scrum meetings, removes impediments to the goal, or something that pulls the development down, and he makes sure that the development team has what it needs.

The product owner’s role

The product owner is another member of the team. He represents the business on the team and owns the product backlog artifact. He provides guidance to the team and prioritizes all work. It is great if the product owner can answer all questions. It is nice to think of the product owner as the client , a very special client that’s the first among equals and a member of the team that can negotiate the trade-offs when change needs to be done up to the current software product or project.

The Development team’s role

The team is in charge of building software products and in participating scrum meetings, as well as in sprint planning, daily scrum, and sprint retrospective.

Scrum in action

Scrum begins when the product owner manages a list of requirements called a product backlog. The requirements are written from the user’s perspective and are called user story requirements.

In scrum, developers implement the user stories in increments called sprints. Sprints are scheduled in time boxes typically 2-4 weeks. During each sprint the developers implement some of the user stories in the product backlog. The delivery of each sprint is a working subset of the product backlog called a product increment.

Before the sprint begins, the whole team gets together for a sprint planning meeting. At this the meeting of the product owner prioritizes the user stories to be implemented for the sprint. The whole team also estimates the prioritized user stories based on team resources, effort, and complexity, among others. The result is to agree on a sprint backlog that can be committed to for the time being.

Early testing and test coverage is a key advantage of the scrum. Testers can immediately cover user stories with test cases once the sprints are planned. Testers can begin testing once the product increment is released.

Transparency in Scrum

In scrum, transparency is vital. There are daily meetings where the development team members update their work status of the whole team. This is a scrum meeting called the daily stand up meeting or daily scrum meeting.

To maintain transparency, scrum has artifacts to constantly report progress. The task boast is a scrum artifact available to the whole team which is used to track the team’s user stories, tasks, defects, and other work items through the team’s work flow which are in the form of swim lanes.

Another key scrum artifact is the burn down chart, which allows for the continuous tracking of progress during the sprint. The burn down chart is also a trending tool where you can forecast current end dates based on current data. These charts are very simple yet highly functional.

The resulting product of the sprint is the product increment. Although the product increment is based on user stories, all applications layers are present in the product increment.

A facet of scrum is continuous improvement through sprint review or retrospective meetings. This is the meeting held after the recently concluded sprint where the product increment is demonstrated to the whole team. The whole team also reflects on the recently concluded sprint to identify items for improvement.

So how to validate things?

Member of the team comes up with ideas and eventually, the ideas are being implemented for the next sprint and the team will build on the succeeding product increment so the next product increment will include everything that was implemented in the previously concluded sprint and changes will be added as well as other items from the product backlog until the product grows incrementally until it is released to users.

Print Friendly
Share
This entry was posted in Blog, Tutorials. Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>