{"id":2228,"date":"2022-02-07T11:07:40","date_gmt":"2022-02-07T11:07:40","guid":{"rendered":"https:\/\/dcss.in\/?p=2228"},"modified":"2022-02-07T12:02:26","modified_gmt":"2022-02-07T12:02:26","slug":"scrum-project-management","status":"publish","type":"post","link":"https:\/\/dcss.in\/index.php\/2022\/02\/07\/scrum-project-management\/","title":{"rendered":"SCRUM Project Management"},"content":{"rendered":"Reading Time: <\/span> 4<\/span> minutes<\/span><\/span>\n

Overview<\/h2>\n\n\n\n

Scrum project management methodology is a structure used for organizing and managing the moving parts of a project. Originally designed for use in software development, Scrum is now used by organizations and project managers across all disciplines. The methodology works well for smaller teams tackling projects with changing deliverables, unknown solutions, and frequent interaction with clients or end-users.<\/p>\n\n\n\n

Scrum is a framework that helps teams work together. Much like a rugby team (where it gets its name) training for the big game, scrum encourages teams to learn through experiences, self-organize while working on a problem, and reflect on their wins and losses to continuously improve. Scrum favors incremental and iterative phases of production to deliver functional products faster and with more frequency.<\/p>\n\n\n\n

Scrum is the perfect way to remove the tight controls of traditional project management and to liberate a team\u2019s creativity to address rapid client changing needs.<\/p><\/blockquote>\n\n\n\n

In addition to empowering teams to think creatively as they iterate, Scrum drives feature prioritization by organizing features and goals into deliverables that the team works on in two-week sprints. This way, the most important work gets done first. By contrast, Scrum simply provides a structure for delivery, but does not tell you how to do specific practices, leaving that to the team to determine. Below diagram shows the basic Scrum framework.<\/p>\n\n\n\n

The project begins with a clear vision provided by the business, and a set of product features in order of importance. These features are part of the product backlog, which is maintained by the customer or customer representative referred to as the Product Owner. A time box commonly referred to as an iteration or sprint, is the set amount of time that the team has to complete the features selected. Sprints are generally from one to four weeks in length, and that length is maintained throughout the life of the project so as to establish a cadence. The team selects items from the product backlog that it believes can be completed in the sprint, and creates a sprint backlog consisting of the features and tasks as part of the sprint-planning meeting.<\/p>\n\n\n\n

Once the team has committed to a sprint backlog, the task work begins. During this time in the sprint, the team is protected from interruptions and allowed to focus on meeting the sprint goal. No changes to the sprint backlog are allowed; however, the product backlog can be changed in preparation for the next sprint.<\/p>\n\n\n\n

During the sprint, the team checks in daily with each other in the form of a 15-minute meeting known as a scrum. The team stands in a circle and each member states what they did yesterday, what they plan to do today, and what is getting in their way. At the end of the sprint, the team demos the work they have completed to the stakeholders and gathers feedback that will affect what they work on in the next sprint. They also hold a retrospective to learn how to improve. This meeting is critical, as its focus is on the three pillars of Scrum: transparency, inspection, and adaptation.<\/p>\n\n\n\n

SCRUM Roles<\/h2>\n\n\n\n

There are only three roles in Scrum: ScrumMaster, Product Owner, and Team.<\/p>\n\n\n\n

ScrumMaster<\/strong><\/p>\n\n\n\n

is the keeper of the process, the advocate for the team, and the protector of the team. They remove obstacles, facilitate team communication, mediate discussions within the team and negotiate with those external to the team. Above all, they exist in service to the team.<\/p>\n\n\n\n

The Scrum Master helps the team apply the Scrum framework successfully. They ensure the team functions smoothly by reigning in overbearing product owners, minimizing distractions, and coaching the team on best practices.<\/p>\n\n\n\n

The Scrum Master also leads the daily Scrum meeting, which helps the team stay on task and on process.    A key difference between a Scrum master and a traditional project manager is that a Scrum master does not give step-by-step direction to the team. At the beginning of a project, the Scrum master and product owner meet to prioritize features and organize the sprint.<\/p>\n\n\n\n

Product Owner<\/strong><\/p>\n\n\n\n

represents the voice of the customer and has the authority to make decisions about the product. This person owns the product backlog and is responsible for communicating the vision to the team, and defining and prioritizing backlog items. The Product Owner works with the team on a daily basis to answer questions and provide product guidance.<\/p>\n\n\n\n