Scrum Meetings: An Introduction

This video is intended for people who are getting started with the Scrum framework and need a primer.  

Waterfall goes through a lengthy planning process followed by building the product and then testing the product, reviewing, and deploying the product. However, you might bring a wrong product to the market. The planning is often done and needs to be done again in certain cycles. When problems are encountered, there’s lots of backstepping and doing over. 

The process is broken up in scrum. We do just enough planning, building the minimum feature set. We build what is planned. Next, we test and review a small feature set and get it ready to ship, occurring the time of 1 to 3 weeks. It’s plan, build, test, review, completing the release. Then we end up with several releases called sprints. Eventually you end up with a shipping product more than waterfall.  

There are 3 key roles in scrum. The product owner defines the feature needed to the product. The scrum master protects the team, processes, and keeps things going. The team is full of developers, testers, writers, in what the product will look like. The team works to get the product done.  

In the product backlog, the team managers create some features, or priorities to get done. User stories are a way of describing a feature set that follows as a _____ I need ____ so that ____ which specifies the right detail, to estimate for the test. Burndown charts show the progress on the completion of tasks on the backlog, and it goes less as the product progresses.  

In sprint planning, the product owner, scrum master, and team meet to discuss stories and estimate sizes. The daily scrum is standup where the team discusses completions, works or blockers. The sprint review is when the team demonstrates the work and discusses how to improve the process. The product backlog says the features and ideas to the product, and the product owner brings into the team. Spring planning determines what goes to the next sprint. The sprint backlog consists of user stories based on the choices made in the planning. The spring is 1-3 weeks where the users complete the work. A daily scrum occurs to the sprint, and the outcome is a potentially shippable product, and a sprint review and retrospective meeting occurs, showcasing the work to the product owner, and have the team work on what they can do to improve their process. Repeat the workflow for each sprint.