Article
Building a new product or a feature isn't that easy task, and having it succeed in the marketplace is even more of a challenge. Good products captivate target audience by addressing customer needs while simultaneously creating a business value that differentiates it from its competitors and Scrum helps. Hey guys, this is Archana from Eddie Rica and welcome you all to this introductory session on Scrum. But before we proceed any further, let's quickly go through today's agenda. So guys, we will begin this session by having a brief discussion on Agile methodology. Then we will move on to today's topic, which is Scrum.
We will discuss what Scrum has, a little bit about history of Scrum, different roles, events and artifacts involved in Scrum. And we will also discuss how Scrum process actually works in practical. And finally, we will conclude this session by having a brief discussion on Scrum board. So I hope agenda was clear to you guys. Let's get started. Then imagine that you're a part of a team which needs to create a new website, for example, an ecommerce website. You have an overwhelming amount of work to do.
You need to build a shopping cart, install an SSL certificate, create a product backlog, create a Facebook page, make a schedule, find a project manager and at least hundred other things that you haven't even thought of yet. Traditionally, most software project are managed using traditional waterfall model. Let's say you did too. Waterfall model is basically a linear model and it delivers all the deliverables at one goal and at the end of the project. It can be tedious and time consuming approach and because there is 0 visibility here and not much stress is put on client feedback, your product might not be what client exactly wanted.
Coming back to your product which is e-commerce website, the same thing happened. Everything is more expensive than you'd expected, your product quality could have been a lot better, you and your teammates are stressed out about deadlines and much more. Well, a simple solution for this is to adopt Agile methodology. Agile is an iterative approach to project management that builds software incrementally from the start of the project throughout the development life cycle. Well, it means that the timeline of the project here is fixed and it cannot be extended. While the timeline is fixed, the end products or you can say deliverables of the project are prioritized and delivered in two week cycle which are usually called as.
This agile approach introduces many benefits which are not possible in traditional waterfall development approach such as delivering high value features within short delivery cycles, improve the level of customer satisfaction, deliver high quality product and many more. And that is why agile is very popular and widely accepted method everywhere. Well, if you ask me, there are multiple approaches to implementing agile methodology. Though all these agile methodology technologies share same philosophy and many same characteristics and practices when it comes to implementation, each of these methodology has its own view of practice, terminology and tactics. As for today, we're going to discuss one of the popular agile methodology or framework you can say, which is Scrum framework.
Let's get started there. So Scrum is a lightweight agile project management framework that can be used to manage iterative and incremental projects of all types. You can think of it as a collection of roles, events, artifacts as in things rules used in combination to create iterative work products in less amount of time. So basically the concept here is to break large complex project into smaller ones, reviewing and adapting along the way. So with Scrub, you write fewer plans and do more in short iterations or cycles that we call sprints. You don't work on separate groups, but you work as one dedicated and committed team instead of working on a project.
With with distant deadline, you constantly deliver functioning products throughout the cycle. You don't use final evaluation, instead you receive continuous feedback from your customers and improvise your product. That's what I meant when I said reviewing and adopting along the way. So you get continuous feedback from your users and improvise your product based on that. So that's what Scrum is all about. It's a flexible way of working in rapidly changing world. So the Scrum is frequently used in IT projects. Most of the time the websites you visit, apps you use were made of Scrum.
Scrum began in software industry and has since spread to universities, military, automotive industry, as BI, to marketing agencies, construction crews and beyond. Anytime you're producing some sort of product, be the software or a simple e-mail campaign, Scrum can help you organize your team and get more work done in very less amount of time. But that still leaves a lot of questions about Scrum framework. What does the name Scrum mean? Why is scrum used and how exactly does it work? Well, the first step towards answering all these questions is to drill down a bit further into scrum's origin and history.
So the term scrum was first introduced by two professors in their 1986 Hardwood Business article where they described a rugby style approach to product development, one where a team moves forward while passing the ball back and forth. I'm sure you might have heard of the game rugby, right? That's what I meant to when I say rugby game here. So that's what they referred to and that's how Scrum came into existence. In the following year, software developers Ken and Jeff each implemented their own version of Scrum in their own companies, and in 1995 the two came together to present and define their version of Scrum, a developed strategy that evolved into Scrum framework that we used today.
After that, there have been many improvements to Scrum framework. We do have Scrum documentation, official Scrum documentation that you can refer to. So that's about the history of Scrum. Now to understand Scrum process, you have to got to know the people and the parts of the framework. So let's begin with the different roles that are involved in Scrum team. The Scrum framework is defined by three core roles, the Product Owner, the Scrum Master and the Development team. While the Product Owner is accountable for work the team is supposed to complete, whether to do it themselves or give it to other team members.
Product Owner not only focuses on the work which is to be completed, but he also manages business and market requirements. The main role of Project Owner is to motivate the team to align them with the goal and the vision of the project. Remember that Product Owner is always a single person and not a committee. While Product Owner can take input from others but when it comes to major making major decisions, ultimately the Product Owner is responsible alone for that. Next up we have Scrum Master. Scrum Master is the team's resident facilitator, responsible for helping all the team members follow Scrum's theories, rules, and practices.
They make sure that the Scrum Team has whatever it needs to complete their work, like removing roadblocks that are holding up the progress, organizing meetings, dealing with challenges and bottlenecks. Last up, we have Development Team. The Development team is exactly what it sounds like, the people working together to deliver product. So despite the development title Scrum software background, keep in mind that the products developed using Scrum can be anything. So, development teams are given the freedom to organize themselves and manage their own work to maximize the team's efficiency and effectiveness. So these are the three important rules which are involved in Scrum team.
What do we have here? We have Product Owner who is responsible for keeping the team in track. Then you have Scrum Master who keeps reminding the team about Scrum policies, rules and practices. Finally, you have a development team who are responsible for developing the project. Next up, we have the things in Scrum Product, or you can say the Scrum artifacts. 1 hefty title, but the concept is really simple. Artifacts are basically just physical records that provide project details. Scrum artifacts include product backlogs, print backlog, and product increments. Let's quickly go through each of them.
First up, we have product backlog. The product backlog is basically is an ordered list of tasks and requirements the final product actually needs. It is evolving and is never complete. The product owner overseas the product backlog, including how it's made available to the team, it's content, how it's ordered, and everything, literally everything. So the product owner and the rest of the team work together to review the product backlog and make adjustments whenever necessary as product requirements keep changing throughout the life cycle. So like I said, Agile is an iterative approach, so is Scrum.
So the product owner and the rest of the team keep updating product backlog according to the requirements that keep changing during different iterations. So for each item in the product backlog, you should add some additional information like the description, the order as in the priority order within which the whole backlog is listed, the estimate time and the value it has in the business. Apart from this, you can add many other things. Anyway, Next up we have Sprint backlog. Sprint backlog is a list of items from the product backlog that need to be worked on during a Sprint. So team members sign up for task in the Sprint backlog based on their skills and priorities.
So as the Sprint evolves, it is possible that slight changes to the Sprint backlog might occur. A new understanding of the feature the team is walking on could mean that something is added to or removed from the Sprint backlog. So the Sprint backlog is a real time picture of the walk that team currently plans to complete during a Sprint. Well, if it seems too much theory, don't worry about it. When we discuss how the scrum process actually walked, you'll understand what a Sprint backlog is. Moving on, we have something called burn down charts.
A burn down chart is a graphical representation of amount of estimated remaining walk. Typically the chart will feature the amount of remaining walk, perhaps usually in ours, on the vertical axis with time along the horizontal axis. So when using a burn down chart, remember that if the chart is deviating from the expected remaining estimates, this is only a pointer. You still need to investigate and understand the cause before you actually can draw any conclusion. Next up we have something called product increment. A product increment is the sum of product walk completed during a Sprint combined with all the walk completed during previous sprints.
So basically in other words, product increment is the new code which has been written to enhance the features or usability of your product. So when you add a new set of code to your Sprint, this new code has to combine with existing code to work well. If your new features work well on their own but break some existing feature in your product, your product increment is not potentially shippable. So that's it guys. With this, we have covered all the key terms that you might come across in Scrum framework. Well, if you are confused from all these terms, do not worry about them.
You will be able to understand them very easily and use them when you adopt Scrum methodology. So Next up we have the Scrum process, as in we're going to discuss how the Scrum process actually works. Very simple, just few steps. So the entire scrum process starts with the product owner. So he's the person who represents the final users best interest and has the authority to save what goes into the final product. This product owner creates a product backlog, which is a list of tasks and requirements the final product needs. The important part is that the backlog, that is the product backlog must be prioritized and that's the job of the product owner.
Just a simple example, Let's say if I were to create a scrum design to design A car, items like must have an engine would be top of my list because without an engine, car wouldn't run, must be painted red would be my last priority. Or it could be a last in my product list because painting a car is anything which you can do later. So it's not of a much priority. So that's how you make a list as in you organize all the items in your list based on priority. So the first step is the Product Owner creates a Product Backlog.
Now the team which is the Product Owner and the Scrum Team get together for Sprint Planning, which is when the entire team decides together what to work on from the Product Backlog list. So a Sprint basically is a predetermined timeline within which the team completes set of tasks from the backlog. The length of this time depends on the needs of the team, but usually two weeks is pretty typical. At the beginning of the Sprint, the developers and the Product Owner agree on the items from the Product Backlog which they will complete during that Sprint. This subset of items from the Product Backlog which they have extracted to complete in that particular Sprint is what we call the Sprint Track Lock.
So the Scrum Team isn't just sitting there with blinders on because they get together every day to communicate the progress and issues. This meeting is what we call Daily Scrum and it is overseen by the Scrum Master, whose job is to keep everyone on the efficient path. So during the Daily Scrum, each Development team member expresses what task he accomplished since the last meeting, what he is planning to complete until the next meeting, and whether there are any impediment or obstacles on his task while he's completing them. The Scrum Master, who is basically like the coach on the field with the Scrum team, removes distractions and ensures that the Daily Scrum meeting is completed within 15 minute time box.
So basically during a Sprint. So develop a project to have their Daily Scrum meeting where the disk is everything. That's what the second step is all about at the end of the Sprint. Sprint Review meeting is organized by the Product Owner. All the stakeholders and the Scrum Team attends the Sprint Review meeting. During the Sprint Review meeting, the Development Team demonstrate what they have completed since last Sprint and the Product Owner gives information about what is remaining on the Product Backlog and estimated time to complete the project if needed. So remember guys, at the end of the Sprint.
The team should have a functional piece of something to show their work. The important thing is that product must actually work at the end of each Sprint. So that's what I meant. How agile is different from traditional waterfall approach. Unlike in waterfall approach where you have final product at the end, in Scrum which is a agile methodology, you have a properly functioning product at the end of every Sprint. Moving on, after the Sprint review meeting, the development team gathers up in Sprint Retrospective meeting. During the Sprint Retrospective meeting, team discusses what they have done good and what they could have done much better.
Maybe it's a tech limitation holding them back or maybe one team member is overloaded with task. The team decides how to fix these problems with the intent of improving their efficiency on how they do their work. Theoretically, the team should be more efficient and produce more work with each new cycle and they try to achieve that and discuss on how to achieve that in the Sprint Retrospective. So the entire cycle starts with the Sprint Planning and ends with the Sprint review. Or you can say Sprint Retrospective until either the deadline has been reached, the budget is exhausted, or the product owner is satisfied, satisfied with the final product, whichever comes first.
So after Sprint Retrospectives, the cycle again begins to have certain other things which are left out in the product backlog. They are put to the Sprint backlog again, the scrum meeting, the Scrum owner comes and pushes up the spirits of everyone in the team. Then you have another product, another addition to the product, and then you have Sprint Retrospective. The cycle repeats until the deadline has been reached, or the budget is exhausted, or the Product Owner is satisfied with the final product, whichever comes first. So that's it guys. In a nutshell, that is how Scrum works.
An important principle in Scrum is the idea of transparency. All team members involved should be aware of what everyone else is working on, progress being made, and what the team is trying to accomplish. And that's why making things visible for all to see is very important in Scrum process. A big piece of this is Scrum Board. This is place where you can organize your backlog as well as the tasks that are being worked on in the current Sprint and their progress. Scrumboards can be as simple as a whiteboard with sticky notes for each task, or it can be as complicated as a specialized software with charts and task tracking features and all that.
Well, it literally depends on what you want to do and how you want to do it. Well, that's it guys. With this we have come to the end of the session. So guys, as you can see, learning basics is pretty easy in Scrum. The hardest part is learning the key terms involved and staying true to the rules and the guidelines that make Scrum work. With Scrum, you're not creating more work for yourself. Instead, you're being more efficient with your time so that you can spend less time at the office and more time with the people and the things you love.
So if you are tired of your current methodologies of project management, why not give Scrum a shot? Thank you guys. If you have any doubts or any queries or if you have anything to discuss, please do put them in the comment section below and we will get back to you as soon as possible. And if you have liked the session, please do click on the like button and I'll meet you in the next session with another interesting video on scrum. Thank you guys. I hope you have enjoyed listening to this video, please be kind enough to like it and you can comment any of your doubts and queries and we will reply them at the earliest.
Do look out for more videos in our playlist and subscribe to Eddie Rica channel to learn more. Happy learning.