What is the SCRUM methodology and how does it work IN REAL LIFE? | SCRUM explained

What is the SCRUM methodology and how does it work IN REAL LIFE? | SCRUM explained

scrum red cross backlog grooming all of these are words that everyone in the technology business has heard of but what exactly is scrum and is it as complicated as it feels to be in this video i’m gonna explain what happens in real life and how you can adhere to this ground philosophy and take the best out of it even if things don’t play out exactly by the book [Music] if we turn to the source of all knowledge the almighty wikipedia here is the definition it provides scrum is a framework utilizing an agile mindset for developing delivering and sustaining products in a complex environment it’s an excellent way to put it but if you dive a little deeper into the theory of what a scrum process should be like and what it entails you’re gonna feel like you’re bombarded with specific ways to do things and fix processes this can feel daunting in real life things aren’t always done in the ideal way you expect but it doesn’t mean you don’t need to learn the basics as pablo picasso said learn the rules like a pro so you can break them like an artist as a part of my software agency i’ve built countless products for silicon valley startups and global businesses and almost all of these products have used the scrum philosophy here are the high level concepts of scrum simplified to use in real life concept number one grooming the backlog a product manager along with the other members of the team has to maintain an ongoing list of tasks that need to be done in order to build or improve a product these tasks can be as simple as changing the text on the button somewhere or as complex as building new modules altogether the requirements on the high level come from whoever is the stakeholder of the product this ongoing list of tasks is called a product backlog think of it as a laundry list of everything that needs to be done of course it’s not possible for the development team to go through each and every task and complete all of them in just a single sprint so it’s important to maintain the product backlog in a way that a the priority is clear the product manager has to go through the list of tasks and prioritize them basically just by dragging the most important items to the top but of course you can’t prioritize something unless you have at least a high level understanding of the amount of effort it implies which brings us to b the items are broken down into smaller pieces the common format is the user story which is an informal way of describing functionality that goes something like this as an admin of the system i can invite other users and grant them different access rights so that they can moderate the content a user story is basically defining the functionality in a way that the future user of this functionality will experience it don’t sweat about the particular way you describe a feature but the most important thing is this it has to be small enough so that the amount of the necessary effort is clear at a glance it’s important because in many ways it will influence the priority after all if something takes 30 minutes of work you will probably want to get it done but if something takes a month you might want to de-prioritize it in other words it should be clear which tasks require little bandwidth but can have a big impact right now concept number two this print what’s a sprint a sprint is an iteration as simple as that a sprint is an iteration that delivers a working update of the product a sprint shouldn’t be too long because it decreases flexibility but shouldn’t be too sure because the update should be tangible a sprint planning session is when the broader direction that we discussed initially is refined further what you do during a planning session is you take items from the backlog that’s why it has to be prioritized broken down and clean you assess the items with the team and based on your capacity you decide what is the set of things you will take on in the next iteration the assessment can be done in story points but if you feel like that’s one more concept you need to understand feel free to assess it just in hours that is how much time it’s gonna take an engineer to implement it for example a user story can be worth one hour eight hours etc oftentimes people confuse grooming and planning the difference is that in a grooming session you maintain and replenish the backlog while in the planning session you decide which are the items you will take on next if you’re new in my channel welcome i post videos like that every single week so consider subscribing to always be up to date i try to navigate the technology business become smarter every day and share my experience as i go now back to our real life scrum story one of the most important tenets of scrum is that once a sprint has been planned it cannot be changed it’s a small iteration so that you can be flexible in the grand scheme of things but within it it’s a fixed scope in a sprint you have to let your team work without distractions so that they don’t have to worry about quick fixes ever-changing priorities urgent changes and stuff like that concept number three the daily stand-up call it’s a quick meeting which demands the presence of every single one of the team members in this meeting everyone answers the following three questions hey what did i do yesterday b what do i plan to do today c is anything blocking me in the course of sprint problems are discussed on the go and new ideas are noted in the backlog remember even if you come up with something brilliant the scope of the sprint cannot be changed you just put it in the backlog and don’t distract anyone the main goal of the daily stand-up call is to make sure that everyone is on the same page and problems do not linger till the very end of the sprint if there is a blocker for someone for example the server wasn’t set up properly so the engineer can’t proceed with the task it’s the responsibility of the manager to unblock this person so that this chrome scope will be met in today’s reality software engineering teams are often spread out between time zones it can be hard to have a call every single day when one part of the team is in california one more part is in india someone is in europe and someone else happens to be in australia a life hack i can recommend is having text standups instead of calls you can dedicate a specific slack channel to the daily updates so that it’s kept separate from the main discussion the process is absolutely the same but people are leaving notes in the text form which means the meeting can happen asynchronously and nobody has to get up at 5am to wait while someone else reconnects the headphones for the fifth time so how long do sprints last it’s usually recommended that sprints last anywhere between two and four weeks this varies from company to company and from product to product i sometimes like even more aggressive one-week sprints at the very outset of development where the product is still very small and many things aren’t clear it just helps to reset tasks a bit more often when the product has become more mature you will probably want to switch to 2-week sprints i don’t recommend having sprints that last more than 2 weeks for 2 main reasons first a 4-week sprint is simply too long and you won’t have the flexibility you need second have you heard of parkinson’s law it says that work expands so as to feel the time available for its completion we’re all guilty of procrastination and i think that a sprint that’s too long doesn’t force the team to stay focused concept number four the sprint review this is with the whole development team along with the other stakeholders sits down together and analyzes the work that has been done during this sprint the team analyzes what was done on time and what took more time than expected and how to avoid similar problems in future iterations the main focus of sprint review is to continue the forward moving momentum you need to keep up the morale morality team and assure the stakeholders of the team’s capability that’s the high level overview of scrum i didn’t mention the fibonacci scale the planning poker the retrospective the ethics but my goal with this video was to show you how to take advantage of this excellent technique in an environment where normal mortal people are involved you don’t have to be a scrum nerd in order to take the best of what it has to offer the most important thing is the mentality what is it that you hate about the scrum process please let me know in the comments down below and don’t forget to subscribe to my channel see ya [Music]
rn

What is the SCRUM methodology and how does it work IN REAL LIFE? | SCRUM explained

rn

Share this post

Leave a Reply

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