Scrum framework

[Audio] Hello today we will be going over the scrum framework.

[Audio] So you may be thinking what is scrum. Scrum is a technique that teams utilize to help with self-organization when working towards common goals and it does this by using meeting, tools and different roles to get the job done. Much like a sports team practicing for a big match, scrum practices allow teams to self-manage, learn from experience, and adapt to change, and software teams also use this strategy to divide their team to better solve complex problems..

[Audio] There are certain principles and values that characterize scrum methodology.

[Audio] First up is transparency and what we mean by this is that teams will excel in an environment where everyone is aware of the challenges others might be experiencing and by having Regular face-to-face conversations between cross-functional team members and project owners prevent miscommunication..

[Audio] Next is reflection which can play a big part in this strategy because this is where the team look back at previous mistakes, challenges and problems in the hopes of learning from them and maybe using their solutions to help fix the problem the team is currently facing which also helps them to be more flexible when it comes to problem solving..

[Audio] The last one on the list is adaptation which is when team members can reprioritize tasks based on changing customer requirements. They decide which tasks to complete first and which to revisit in the future..

[Audio] So now let look at how it all works. Scrum is a framework that is easy to learn but difficult to become an expert in. The essence of scrum is a self-organizing team delivering customer value in a time-boxed period called a "sprint". Scrum defines artifacts, roles, and events associated with each "Sprint". Let's look at each of these in detail..

[Audio] Now lets look at what takes place during scrum events which are a set of sequential meetings that Scrum Teams perform regularly. Sprint - a sprint is the actual time period when the scrum team works together to finish an increment. Daily Scrum - a daily scrum is a short meeting in which team members check in and plan for the day. They report on work completed and voice any challenges in meeting sprint goals..

[Audio] So we now know what goes on during scrum events no lets meet the team.

[Audio] Product owners job is to focuses on ensuring the development team delivers the most value to the business while trying to understand and prioritize the changing needs of end users and customers. An effective product owner will do the following: Give the team clear guidance on which features to deliver next. Bridge the gap between what the business wants and what the team understands. Decide when and how frequently releases should happen..

[Audio] Next is the scrum leader or scrum master who is responsible for the teams effectiveness and their responsibility's are as followed Schedule the resources needed for each "sprint" Facilitate other sprint events and team meetings. Lead digital transformations within the team. Facilitate any team training when adopting new technologies. Communicate with external groups to solve any challenges the team might be facing as a whole..

[Audio] Last but not least is the scrum development team and they consist of testers, designers, UX specialists, Ops engineers, and developers. Each team member has a different skill set and cross-train one another, this means that no one person becomes a bottleneck in delivering work. Scrum development teams do the following: Work collaboratively to ensure a successful "sprint" completion Sustainable development practices Self-organize and approach their projects with an evident we attitude. Drive the planning and estimation for how much work they can complete for each "sprint".

[Audio] So earlier on we mentioned scrum tools be they actual name are scrum artifacts and they help to solve problems and manage projects. Scrum artifacts provide critical planning and task information to team members and stakeholders..

[Audio] Now lets look at product backlog which is basically the teams to-do list which will constantly change due to what the client wants and to any problems that appear during development and its down the project owner to stay on top of it so they can dish out tasks to the team or reprioritize tasks if needed..

[Audio] The next thing we need to cover is the sprint backlog which is a list of items that need to be completed by the development team in the current sprint cycle but before this happens the team need to choose a set of tasks form the product backlog but there is one thing the people need to be aware of is that a sprint backlog is flexible which means it can evolve and change as it goes on..

[Audio] So now you know about the sprint backlog so the last thing we are going to look at is the increment which is a step towards a goal or vision which means it's a usable end product from a sprint and so teams can adopt different methods to define and demonstrate their sprint goals but despite the flexibility, the fundamental sprint goal can't be compromised..

[Audio] Thank you for listening.. Thank you for listening to the presentation, time for the quiz!.

Sea of white umbrellas with one blue one in the crowd.

A close up view of a track and field lane in the dark.

Name one of the scrum values. Transparency Reflection Adaption.