Implementing Scrum Management

Instructor: Adam Nystrom

Adam is currently working on a Master's degree in Professional and Digital Media Writing.

Scrum management is a methodology designed to deliver software products faster and with a higher level of quality. This lesson will provide a guideline for implementing the scrum methodology.

Implementing Scrum Management Overview

Many scrum trainers promote scrum management as the next best thing since sliced bread... but is it really? The essence of Scrum is to eradicate the deficiencies in project delivery and increase the likelihood your end product will match clients' expectations. Scrum management is led by a scrum master, who is also known as a facilitator, instead of a project manager. Some people use the terms agile and scrum, interchangeably; however, scrum is one of the frameworks of agile. The four main objectives of scrum management are:

  1. deliver products to market at an accelerated pace
  2. significantly increasing the quality of the product
  3. promote teamwork
  4. encourage communication

In other words, the delivery of the product is expected to be much faster than the traditional waterfall methodology and the quality is expected to be higher because clients' will review the results periodically, instead of at the end. Additionally, by design, scrum methodology fosters teamwork as well as communication amongst the team.

Scrum Management Planning

The product owner kicks off the scrum management planning process by creating a product backlog, which is a document containing prioritized features or requirements. The features or requirements will be completed during the scrum sprints, which is a repeatable cycle to complete project work also known as an iterative process. Keeping in mind, scrum is design to deliver usable features to production within short periods.

The project team must extract the requirements from the product backlog and enter them into their sprint backlog. The project team will create all of the user stories (stories), which a breakdown of tasks, and then they estimate the stories. Enter all of the stories into the sprint backlog, which is a consolidation of user stories. During Sprint planning your team will identify and select the stories (tasks) targeted for completion in the next Sprint.

For example, the product owner wants you and your project team to develop software for a special student internship program. The software requirements consist of determining students' eligibility, creating a log for cancellations, and distributing notification letters to selected students. These three requirements are listed in the product owner's backlog and during sprint planning, your project team will select the highest priority requirement, which is to develop the requirement to determine students' eligibility. At this point, they will write stories (tasks) to select the eligible students and provide stories estimations. The stories and estimates will be placed in their sprint backlog,

Scrum Management Execution

Sprint iterations are repeated into the final product is completed. The scrum master and project team will identify the user stories and determine the number of stories for each sprint. There may be times where you didn't identify enough user stories for the current sprint; however, in this case project team members should select one or more user stories from the sprint backlog. When project teams are weak in performing sprint estimation, the stories in the sprints could be either over or under-estimated.

The scrum master monitors and tracks the status stories via burn down report, which shows the number of stories remaining to completed.

Scrum Management: Communication and Teamwork

A daily scrum is one of the most critical components of the scrum management process. This is where the project team communicates honestly and openly about the status of their active stories, roadblocks, and discuss project dependencies. Further, a few organizations will hold client demos, which the goal is to provide your clients with opportunities to provide feedback throughout the implementation, prior to migrating the program code to production.

To unlock this lesson you must be a Study.com Member.
Create your account

Register for a free trial

Are you a student or a teacher?
I am a teacher

Unlock Your Education

See for yourself why 30 million people use Study.com

Become a Study.com member and start learning now.
Become a Member  Back

Earning College Credit

Did you know… We have over 95 college courses that prepare you to earn credit by exam that is accepted by over 2,000 colleges and universities. You can test out of the first two years of college and save thousands off your degree. Anyone can earn credit-by-exam regardless of age or education level.

To learn more, visit our Earning Credit Page

Create an account to start this course today
Try it free for 5 days!
Create An Account