Scrum Master Essentials
The Development Team should wait until the Product Backlog is 100% planned to start developing the project?
false
How many events are there in a Scrum Project?
five
A detail plan
is a breakdown of a Product Backlog item into detailed tasks needed to be done in order to create the item. Each task might have estimates, dependencies, and similar information to make tracking possible.
An Increment
is a potentially releasable product
Scaled Scrum
It might be required to have more team members for larger projects. In that case, we can use multiple teams for a single product, and it will be called scaled Scrum. Scaled Scrum should follow the whole Scrum framework nevertheless.
If an item is not considered "Done"
It would not be part of the Increment and it would not be demonstrated to the customer at the Sprint Review; it will be returned to the Product Backlog and if it's still at the top (after reprioritization), it will be selected for the next Sprint.
Sprint Time boxes:
Most companies use Sprint time boxes of 2 to 4 weeks. If we use Sprints longer than one calendar month, it will be likely for the unapplied changes to become large enough to create problems. This will increase the complexity and risk.
An Increment
is a sum of all Product Backlog items completed so far in a project and this Increment keeps getting bigger after each Sprint. You can think of it as different versions of a software; each time with more features.
An Increment
is developed in each Sprint
Are Scrum Masters equivalent to traditional project managers?
it is not true, because the Scrum Master responsibilities are very different than a traditional project manager.
Increments
may or may not be actually released (put into use), but should always be potentially releasable.
The Product Backlog would be
ordered in a way that facilitates setting Sprint Goals
The Scrum Goal
provides guidance to the Development Team on why it is building the Increment.
In order to maximize productivity, all of the Scrum events must be
time- boxed. It helps everyone focus on the real problems, instead of going into too much unnecessary detail.
Each Development Team member is responsible for all the outputs created in the Development Team, even though each of them might be focused on a specific set of tasks.
true
If there is a need to change team members, then this change should not happen during a Sprint. There will be a short-term decrease in productivity when the composition of the team changes.
true
It is highly recommended for members of the Development Team to work full-time in a single project, to stay focused and agile
true
Obstacles are not discussed in the meeting. If someone has a solution or concern, s/he should mention it after the Daily Scrum
true
Sprint Planning is a time-boxed meeting, usually fixed to 8 hours for a one month Sprint, or shorter for Sprints of less than a month. All three roles should attend this meeting.
true
The Daily Scrum is a 15-minute meeting for the Development Team to inspect the work since the last meeting, and synchronize their work and plan for the next 24 hours. It must be held daily.
true
The Sprint Goal should not change
true
The composition of the Development Team should not change so often.
true
The information gathered through Daily Scrums would be useful for updating the board, but the updating is not done during the Daily Scrum.
true
Task
When the items to deliver are selected and the Sprint Goal is agreed, it is time to plan how they will deliver the items into a "Done" product Increment and realize the Sprint Goal. This is the last element of the Sprint Backlog: tasks.
There's one Scrum Master role per team in scaled Scrum. However, a single person can be the Scrum Master of more than one team.
true
Sprint is a time-boxed event, which means
we should fix its duration at the beginning of the project and not change it frequently or occasionally. Sprints are fixed for one month or less.
It is possible for a single person to be both Scrum Master, and a member of the Development Team?
yes although this is not recommended. Being a Scrum Master of a project might not occupy 100% of the time of a person; in this case, the best solution is to assign that same person as the Scrum Master in more than one project, rather than making them a member of the Development Team.
There's only one Product Owner, even in scaled Scrum?
yes because it is very hard to manage value otherwise.
The Sprint Backlog consists of the following:
1. The Sprint Goal 2. Selected items from the Product Backlog, to be delivered through the Sprint 3. A detailed plan for turning the selected items into "Done" Increment of the product and to realize the Sprint Goal
Scrum is mostly effective when there are
3 to 9 Development Team members. For large projects, we can use a scaled model with multiple Scrum Teams.
Sprint Retrospective
After the Sprint Review and just before the Sprint is over, the Development Team holds an internal meeting to review the Sprint (lessons learned) and use it to improve the process in the next Sprint.
Sprint Review
Before the end of the Sprint, the Development Team presents (demonstrates) the outcome of the Sprint to the customer and receives feedback.
Can a Sprint be cancelled?
Even though Sprint Backlog items are frozen and do not change, the Product Owner has the authority to cancel a Sprint. This can happen when the Sprit Goal becomes obsolete, due to changes in the Product Backlog, strategies, approach, market, etc.
They area experts that are responsible for delivering backlog items, and managing their own efforts.
Development Team
They deliver the final product of the project in step by step Increments, as defined in the Product Backlog. They always work in a product-based way.
Development Team
They should be cross-functional; being capable of doing the A to Z of the creation of each Product Backlog item.
Development Team
They should be self-organized; find their own way instead of receiving orders. They should be aligned with the goal of the project instead of working blindly
Development Team
Who is responsible for a task that might be assigned to a single member throughout the Sprint
Development Team
During the Daily Scrum, each member of the Development Team should answer these three questions:
During the Daily Scrum, each member of the Development Team should answer these three questions:
In Scrum of Scrums Daily Meeting
Each representative answers the three standard questions, plus this: what dependencies will your team have with other teams?
Scrum of Scrums event
In scaled Scrum when Development Teams are done with their Daily Scrums, each will send a representative to a higher-level daily meeting called Scrum of Scrums
Sprint
Is a container for the four other events, development effort, and the maintenance of the Product Backlog.
time-box
Is a fixed period of time ( a predefined maximum duration of time) in which we freeze the target and work with full focus on certain tasks or objectives.
What is the Sprint Goal?
Is an objective that should be met within the Sprint through the implementation of the Product Backlog.
Sprint Planning
Is the first event inside a Sprint. The Scrum Team plans the items they are going to deliver in the Sprint and the way they will deliver them.
We can change the items of the Sprint Backlog after the Sprint is started?
No, we do not change the items of the Sprint Backlog after the Sprint is started and the plans are set.
All task are planing into Spring Planing event?
Not all tasks are planned in this event; having a detailed plan for the first few days is enough. The Development Team can prepare detailed plans for the rest of the work later on.
Is a prioritized list of items (usually user stories) that the client expects from the project; this is the main planning tool in Scrum.
Product Backlog
The Product Owner is responsible for the
Product Backlog
Each project needs a business oriented person, aimed at maximizing the value of the product and the work of the Development Team. In Scrum, this person is called:
Product Owner
He/She can organize the items will be sorted based on their value, so the higher they are on the list, the sooner they will be developed by the Development Team.
Product Owner
He/She can rank each Product Backlog item based on its return on investment, as well as any other factor they find suitable for the business point of view of the project.
Product Owner
He/She might delegate some of her/his responsibilities (such as preparing the list of items for the Product Backlog) to the Development Team, but stays accountable for them.
Product Owner
This role belongs to one person. There can be a committee to handle the responsibilities of this role, but in such a case, there should be one person representing this committee and we call this one person the:
Product Owner
To make sure that each Product Backlog item is easy to understand for the Scrum Team, and other stakeholders, t is also the responsibility of:
Product Owner
A Scrum Team consists of the following three roles:
Product Owner Scrum Master Development Team
He/She a management position, which manages the Scrum process, rather than the Scrum Team. S/he is a servant-leader for the Scrum Team.
Scrum Master
He/She are who fully understand Scrum, and help the Scrum Team by coaching them, and ensuring that all Scrum processes are implemented correctly.
Scrum Master
He/She help the Product Owners, by helping or consulting them on finding techniques, communicating information, and facilitating related events.
Scrum Master
S/he should also help those outside the Scrum Team understand the appropriate interactions with the Scrum Team to maximize the value created by the Scrum Team.
Scrum Master
S/he usually leads the organization in its effort to adopt Scrum.
Scrum Master
Who creates the Sprint Goal?
Scrum Team
Scrum allows more specific titles, such as designer, tester, quality inspector, and team leader;
Scrum does not allow this! All members should have the same role, and the same title: Development Team member. If you give them different titles or roles, they will focus on their own specific role in the project instead, and they might not pay enough attention to the final product which is necessary for agile projects
Scrum Team has two essential characteristics:
Self-organized and Cross-functional
The scope of the Sprint, which is made up of the items selected from the Product Backlog, might need to have more details through the Sprint. These details should be aligned with the
Sprint Goal
Daily Scrum
The Development Team starts working on the objectives of the Sprint as soon as Sprint Planning is completed. During the Sprint, the Development Team holds a daily meeting (normally 15 minutes) to coordinate the work for the next 24 hours.
Meaning of Cross-functional
The Scrum Team has all the expertise and competencies needed to get the job done without any help from outside the team.
Meaning of self-organized
The Scrum Team manages its own efforts rather than being managed or directed by others. In traditional methods, management efforts are separated and centralized; a subset of the project team is responsible for project management and others are only responsible for specialist activities. HOWEVER, MANAGEMENT AND SPECIALIST EFFORTS ARE NOT SEPARATED IN SCRUM.
A company needs to adapt to scrum framework to use this?
The customer should understand and adopt the Scrum framework too, as the relation between the customer and the performing organization and the way we deliver the project completely changes when we switch to the Scrum framework.
When a Sprint is cancelled
The items that are "Done" will be reviewed and accepted, and the rest of the items (not started or partly complete) will be put back into the Product Backlog to be done in the future.
What happens to project management responsibilities?
The project management responsibilities are distributed among the three roles of Scrum and there is no centralized project management in Scrum.
Who is the project manager?
There is no such role in Scrum; and none of the 3 roles of Scrum act as a traditional project manager.
