Please enable JavaScript.
Coggle requires JavaScript to display documents.
Chapter 1 What is Scrum, A General Overview and A Little Bit of History…
Chapter 1 What is Scrum, A General Overview and A Little Bit of History about it
- There are three basic principles that come with the Scrum ideology including:
Adaptation
It’s important for your Scrum team to be able to adapt to all the different changes that this process is going to go through.
The customer may change their mind, the team may decide that they want to change up the way they will complete a task, and the Product Owner can make some changes to the Product Backlog.
-
Transparency
The Scrum ideology is all about seeing how things are and making sure that everyone on the team knows what is going on as well
Transparency is so important during every step of this process to ensure that everyone is held accountable.
- What is So Special about Scrum
The product is going to be built in a series of fixed-length iterations which are known as sprints that can give teams a framework for dealing with software on a regular cadence.
Milestones, which are also the end of a sprint, are going to come often. This helps you to feel like there is a tangible amount of progress with each cycle. This quick movement can make team members feel like they are meeting goals and can provide a form of energy to the work.
Short iterations in the Scrum framework are going to help reinforce the importance of good estimation and some fast feedback from tests will help you know if you are taking the right direction on the product or if you need to try something new.
Sprint planning: This is going to be a planning meeting that the whole team needs to attend. During this time, you need to determine what you and the team want to be able to complete in the coming sprint.
Daily stand-up: This is known as the daily Scrum. This is going to be a short meeting, about 15 minutes, where the software team can get together and sync up to know what to accomplish that day.
Sprint demo: This is a sharing meeting where the team can get together and show what they were able to ship that sprint.
Sprint retrospective: This is a review of what went well with the process and what didn’t go so well. You can use this information to ensure that the next sprint goes a bit better. :
During your sprint, some visual artifacts such as burndown charts and task boards will be visible to everyone on the team and can be some powerful motivators. They can show each person of the team how far everyone has come and can even be used to show off new work during the sprint demo to motivate people even more.
- Three Important Roles for Scrum Success
Product owner
These individuals need to focus on understanding all the market and business requirements and then will take this information and prioritize the work that needs to be done by the other groups
-
Keep in mind that the project manager and the product owner are not the same people. Product owners are not going to be in charge of managing how the program proceeds. Instead, the product owner is going to focus on making sure that the team is able to deliver the most value to the business. Also, the product owner needs to be just one person.
Development team
The Scrum team that will be the most effective is co-located, tight-knit, and between five to seven individuals. The team members need to have a different set of skills so that they can cross-train each other.
This ensures that there are more effectiveness and productivity in the team and ensures that one person doesn’t become bottlenecked with the process.
Scrum master
An effective Scrum master really understands what work the team is doing and can ensure that the team optimizes its deliver flow. As a facilitator in chief, they are going to be there to schedule the logistical and human resources, planning out sprints, stand-up, sprint review, and even the spring retrospective.
Part of the Scrum master’s job is to make sure that there aren’t any anti- patterns that start to show up. One that is pretty common with teams that are new to Scrum is when the team tries to change the scope of the sprint after the sprint has begun.
Scrum masters are sometimes thought of as the project managers, but these types of managers don’t have much of a place in the Scrum methodology. The Scrum team can often handle itself and will organize around their own work
In this process, neither the product owners, project managers, nor scrum masters are there to push work on the team. They will list out the work that needs to be done, help to direct some of the things that should happen during the sprint, and more.