The document provides an overview of key Scrum concepts including the Scrum framework, values, roles, events, artifacts and more. It discusses that Scrum is a lightweight framework that uses an empirical and iterative approach to manage complex problems. The Scrum values of commitment, focus, openness, respect and courage are explained. The roles of the Product Owner, Developers and Scrum Master are defined. Events like the Sprint, Sprint Planning, Daily Scrum, Sprint Review and Retrospective are summarized along with timebox guidelines. Product backlog, Sprint backlog and definition of done are also covered.
The document provides an overview of key Scrum concepts including the Scrum framework, values, roles, events, artifacts and more. It discusses that Scrum is a lightweight framework that uses an empirical and iterative approach to manage complex problems. The Scrum values of commitment, focus, openness, respect and courage are explained. The roles of the Product Owner, Developers and Scrum Master are defined. Events like the Sprint, Sprint Planning, Daily Scrum, Sprint Review and Retrospective are summarized along with timebox guidelines. Product backlog, Sprint backlog and definition of done are also covered.
The document provides an overview of key Scrum concepts including the Scrum framework, values, roles, events, artifacts and more. It discusses that Scrum is a lightweight framework that uses an empirical and iterative approach to manage complex problems. The Scrum values of commitment, focus, openness, respect and courage are explained. The roles of the Product Owner, Developers and Scrum Master are defined. Events like the Sprint, Sprint Planning, Daily Scrum, Sprint Review and Retrospective are summarized along with timebox guidelines. Product backlog, Sprint backlog and definition of done are also covered.
The document provides an overview of key Scrum concepts including the Scrum framework, values, roles, events, artifacts and more. It discusses that Scrum is a lightweight framework that uses an empirical and iterative approach to manage complex problems. The Scrum values of commitment, focus, openness, respect and courage are explained. The roles of the Product Owner, Developers and Scrum Master are defined. Events like the Sprint, Sprint Planning, Daily Scrum, Sprint Review and Retrospective are summarized along with timebox guidelines. Product backlog, Sprint backlog and definition of done are also covered.
Easy video course for the Professional Scrum Master I (PSMI) Assessment Based on Scrum guide 2020 SCRUM DEFINITION • The target of the scrum is to generate value: don’t forget that you need to look at value first; • Scrum isn’t a methodology. • Scrum is a lightweight framework for asses complex problems: if you don’t have complexity may be better to use other instruments, no? • Scrum asses this complexity through adaptive solutions.
Follow us on: www.pmguide.cloud
SCRUM THEORY 1 • Scrum is based on Empiricism and Lean Thinking; • Empiricism is about an experience-based approach ; • Lean Thinking is about preventing waste ; • Scrum is an iterative and incremental approach. This helps to prevent risk; in addition, this approach reflects Empiricism and Lean thinking;
Follow us on: www.pmguide.cloud
SCRUM THEORY 2 • The three pillars of empricism are: • Transparency is about making the work visible; • Inspection is about people who must inspect the work to detect a problem; Without transparency, you didn’t have an inspection; • Adaptation is about fixing the process or the output of the process if it is unacceptable.
Follow us on: www.pmguide.cloud
SCRUM VALUES 1 • The Five scrum value are: • Commitment is to the goal and to support each other in the team. We will look that Scrum is all about goals to achieve and self-organized teams that need to help each other. • Focus is about people who need to focus on the actual sprint looking at the goals of the scrum team. This is important because the work is organized by sprint and people need to achieve the target in the timeboxed sprint.
Follow us on: www.pmguide.cloud
SCRUM VALUES 2 • Openness is all about transparency (one of the three pillars of the scrum) and the agreement on the work to do between the team and all the stakeholders. • Respect is essential because Scrum work with a self- organized team, and this kind of teamwork well only if there is respect between each other. • Courage is about accomplishing the right thing. Maybe to find the right solution even if it’s not simple.
Follow us on: www.pmguide.cloud
GUIDO COLANGIULI
PSMI EASY - RECAP 2
Easy video course for the Professional Scrum Master I (PSMI) Assessment Based on Scrum guide 2020 SCRUM TEAM 1 • All people are equal, all roles fall under the Scrum Team; • The scrum team is fewer than ten people; • The Developers are equally accountable for every aspect of the sprint; • The product owner is the people committed to maximizing the value;
Follow us on: www.pmguide.cloud
SCRUM TEAM 2 • Only the product owner can change the product backlog; • If someone wants to change the product backlog need to convince the Product Owner. • The product owner is a person, not a committee; • The product owner can delegate some of his works, but he remains accountable for it;
Follow us on: www.pmguide.cloud
SCRUM TEAM 3 • The product owner is the only one who can cancel a sprint; • The Project manager doesn’t exist. The Scrum Master isn’t a project manager; • The Scrum Master is a servant leader accountable for the Scrum Team’s effectiveness; • The Scrum Master is a Coach and a Guide for all the teams and the organization.
Follow us on: www.pmguide.cloud
THANK YOU FOR WATCHING SEE YOU AT THE NEXT VIDEO
Follow us on: www.pmguide.cloud
GUIDO COLANGIULI
PSMI EASY - RECAP 3
Easy video course for the Professional Scrum Master I (PSMI) Assessment Based on Scrum guide 2020 THE SPRINT • The sprint is timeboxed at max one month or less; • When a Sprint end, another sprint start; • There isn’t a sprint 0; all the sprints have the same structure; • A sprint could be canceled if the Sprint Goal becomes obsolete; • Only the product owner can cancel a sprint.
Follow us on: www.pmguide.cloud
THE SPRINT PLANNING • The sprint planning is timeboxed at a max of 8 hours for a sprint of 1 month. For shorter sprints, you can have faster sprint planning; • The Sprint Goal, the Product Backlog items selected for the Sprint, plus the plan for delivering them are together referred to as the Sprint Backlog; • The event is for all the scrum team; • Only the Developers can choose how much work to do in the plan and how to do it.
Follow us on: www.pmguide.cloud
DAILY SCRUM • The daily scrum is a 15 minutes boxed event; • The daily scrum is for getting alignment on the work and fast decision; • The event is for the Developer, but the Product Owner and Scrum Master can join it.
Follow us on: www.pmguide.cloud
SPRINT REVIEW • Sprint Review is 4 hours boxed event for a one-month sprint; it can be shorter for the shorter sprint; • All the scrum team and the main stakeholder attend the Sprint Review; • The target is to foster empiricism by inspecting the work done.
Follow us on: www.pmguide.cloud
SPRINT RETROSPECTIVE • Sprint Retrospective is 3 hours boxed event for a one-month sprint; it can be shorter for the shorter sprint; • All the scrum team attends the Sprint Retrospective; • The target is to foster empiricism by inspecting the process.
Follow us on: www.pmguide.cloud
GUIDO COLANGIULI
PSMI EASY - RECAP 4
Easy video course for the Professional Scrum Master I (PSMI) Assessment Based on Scrum guide 2020 PRODUCT BACKLOG • The product backlog is the only source of truth; • The commitment of the product backlog is the Product Goal; • The product goal is a long terms target. • You can have only one product goal at a time
Follow us on: www.pmguide.cloud
PRODUCT BACKLOG 2 • The product backlog is an ordered queue of items; • Is the product owner responsible for ordering the product backlog; • An item can have different from; • The product backlog refinement is an ongoing activity; • One product has one product backlog and one product owner (but more different teams can work on it);
Follow us on: www.pmguide.cloud
SPRINT BACKLOG • The sprint backlog is the work needed to accomplish the sprint goals. The Sprint Backlog is composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), as well as an actionable plan for delivering the Increment (how). • The commitment of the sprint backlog is the sprint goal • The sprint goal provides flexibility to the developers
Follow us on: www.pmguide.cloud
INCREMENT • The increment need to meet the definition of done or it comes back in the backlog; • The commitment of the increment is the definition of done; • Every sprint we need at least one increment, but you can have more than one; • You don’t need to wait for the sprint review to release an increment; • If more than one team works together, all the teams need to have the same Dod.