Скачать или смотреть Intro To Scrum | Agile Product Development Methodology

In this video we're going to discuss the scrum product development methodology.

Let us begin by discussing the two most important kind of product development methods out there/ waterfall and agile. Now in the waterfall as the name suggests all the parts of the product development process right from gathering requirements, planning, designing building, releasing and monitoring, all of this is done basically step by step and each of the step could probably take months. So, you finish all the requirement gathering for the product once and for all then you move to planning. You do the planning once and for all then you move to design. So basically, at each of these steps there is no scope of going back and changing the requirements once that process is complete. And each of these phases could typically take months to complete.  Well, whereas agile is a little more flexible where basically you do shorter cycles of this entire process right from planning to releasing and monitoring. And you can keep coming back to the planning phase and keep reiterating on your product as you go along.

Now there are two kinds of agile development methods which are really famous and extensively used out there. The first one is called scrum and the second one is Kanban.  But in this video, we are going to be discussing scrum.
Let's say you wanted to make an app. Now to make product X you basically need three kinds of people and teams on your side to make scrum work.  The first one is the product owner. The role of the product owner is to gather requirements from all possible stakeholders whether it's your users, customers, executives, other team members, anywhere at all. And each of these requirements is basically written as a user story. A user story is written as a user I want to be able to do this so that I can end up achieving something. Now all of these user stories are basically combined and put together in something called a product backlog. The next important team to make scrum work is the development team. Now these are your developers, your testers, basically anyone required to build the product. Lastly, the most important part of the scrum team is the scrum master. Often also known as a project manager in a lot of companies. Now this person’s role is to ensure that the entire process of scrum is being followed in the company. They monitor the progress; they make sure all the teams have everything they need to ship the product and basically, they ensure that everything runs extremely smoothly and we can stick to the deadlines that has been assigned.
The process starts with the product owner who picks stories from the product backlog which needs to go in the next release cycle.  This is called the release backlog. From here they prioritize the list of user stories into high medium and low. From here the team starts adding time estimates to each of the user stories. This gives an indication of how much time it is going to take the team to finish each user story. And overall this tells us how much time is going to be required to complete the next release cycle. Now the user stories from the release backlog is used to plan sprints during the sprint planning meeting. A sprint is essentially a short duration of time typically anywhere between one to four weeks where the development team picks a set of user stories that they can ship at the end of the sprint.
A burndown chart gives you a measure of the amount of work remaining in your current sprint. This is what the chart looks like. Now as the day progress every member in the team working in any of the user story use any software to start logging the amount of work remaining for their user story to compete at the end of each day. Now at the end of the day when all the developers have basically logged their work, you get to know the amount of work done. The slope of this graph typically known as the burndown velocity will tell you the average productivity of your team in a given day which can be used to estimate the completion date of all the user stories in the sprint. You can also use this on any day of the sprint to understand if your kind or ahead of schedule and if you are behind schedule it gives you an idea of what needs to be done to come back on schedule.
Stand-up meeting: which basically lasts for about 15 minutes where each member of the team talks about their progress from the previous meeting, the problems that they are stuck at and the plan for the day.  This is essentially used to track down any problem that's happening within the team which could affect the completion date and remove all the obstacles immediately. At the end of each sprint a sprint review meeting is done where the team basically shows the product owner all the user stories that have been completed. A sprint retrospective meeting is also used to see what are the challenges that was faced during the sprint and what can be done to improve the processes within the company.