Scrum Framework
1. What is Scrum?
2. Scrum Artifacts
3. Scrum Team
4. Scrum Events
5. Actionable Advice
Agenda
What is Scrum
• Scrum is a project management framework in software
development.
• Scrum is one of the implementations of Agile.
• Scrum is widely and globally used because it is lightweight,
effective, and efficient.
What is Scrum?
Scrum can be used
Scrum can be used in various types of software projects.
1. Research & Development
2. Minimum Viable Product(MVP)
3. Cloud Computing Development
4. Web & mobile Development5. Product renewal
Scrum & Agile & Lean
Agile is an umbrella concept of software development, while Scrum, eXtreme
Programming, and Crystal are implementations.
IT Company Performance
• Project performance consists of 3
components: leadership,
management, and technology.
• Scrum covers leadership and
management to boost performance.
Scrum Theory
Scrum Theory
Scrum is founded on three core theories to be empiricism, lean, and
flexible.
• Transparency
• Inspection
• Adaptation
Transparency
• The Scrum Team is transparent through the artifacts and events. Features,
progress, and communication must be transparent to all who get involved in
the project.
• Transparency increases the value of the product because it leads to valuable
discussion.
• Transparency enables inspection. Inspection cannot be done without
transparency.
Inspection
• The Scrum Team constantly checks and shares the progress and goal to detect
the potential risks.
• Inspection is conducted through the five Scrum events: Sprint Planning, Daily
Scrum, Sprint Review, and Sprint Retrospective.
• Inspection enables adaptation. As a result of the inspection, the Scrum Team
can adapt to change.
Adaptation
• The Scrum Team is adaptable to be flexible and prevent deviation as a result
of the inspection.
• Adaptation is one of the critical characteristics of the Scrum Team in order to
meet the changeable market and customer requests.
• Adaptation prevents the common mistake that the software development team
creates unwanted products after spending a long time developing.
Scrum Values
Scrum Values
Focus : The Scrum Team focuses on the Sprint Goal to complete delivery.
Openness : The Scrum Team is open to communicating, sharing ,and helping.
Courage : The Scrum Team challenges the status quo to innovate.
Commitment : The Scrum Team is committed to the team.
Respect : The Scrum Team respect each other.
Scrum Artifacts
First, you must understand three core artifacts of Scrum
• Product Backlog
• Sprint Backlog
• Increment
Scrum Artifacts
Product Backlog
• is the most important artifact in Scrum because it describes everything of the
product: functions, requirements, enhancements, bug fixes, etc, and prioritizes
them.
• Is associated with one product. Even though multiple teams work for a single
product, the Product Backlog must be one.
• Exists and evolves as long as the product lives and evolves.
Product Backlog
Product Backlog contains the following items.
• User Story
• As a <person>, I would like to <what> so that <reason>
• As a e-commerce user, I would like to filter specific categories so that I
can search the product that I want to buy.
• Priority
• Acceptance Criteria
• Estimation
Product Backlog Template
Sprint Backlog
• Sprint Backlog is the set of Product Backlog Items selected to achieve for the
upcoming Sprint.
• The Development Team estimates to select based on the priority of the Product
Backlog and realistic forecast.
• Sprint Backlog is updated throughout the Sprint as the development progress.
Increment
Increment
• is the sum of all the Product Backlog items completed in all
previous Sprints.
• is created when the Product Backlog meets the definition of done
that is the common understanding of completion in the project.
• is releasable whenever the Product Owner wants to release.
Scrum Team
Scrum Roles
The Product Owner:
• is responsible for maximizing the value of the product by clarifying,
managing, and prioritizing the Product Backlog.
• ensures the Product Backlog is visible, transparent, and clear to all.
• is a one person, not a committee.
The Product Owner
Developers
• are responsible for creating increments throughout the Sprint.
• Plan for the Sprint by selecting the Sprint Backlog.
• Ensure the quality of the product by having a professional skills
and adhering to Definition of Done.
Developers
The Scrum Master:
• plays a key role in the team to establish the Scrum.
• removes impediments in the team so that the Scrum Team can
work smoothly and effectively.
• facilitates the Scrum Events to be positive, productive, and time-
boxed.
The Scrum Master
Scrum Events
Scrum Events are meetings that are held during the Sprint for smooth
communication, checking the progress, and achieving the Sprint goal.
• Sprint
• Sprint Planning
• Daily Scrum
• Sprint Review
• Sprint Retrospective
What are Scrum Events
The Sprint
The Sprint:
• is a fixed-length event that the Scrum Team works to make Increments.
• All Scrum Events: Sprint Planning, Daily Scrum, Sprint Review, and Sprint
Retrospective are held during the Sprint.
• must be less than a month, and the shorter the Sprint, the better because the
Scrum Team can generate more learning cycles.
The Sprint Planning
• During the Sprint Planning, The Scrum Team plans which Product Backlog
items they work on to complete at the end of the Sprint.
• The Scrum Team discusses to decide which Product Backlog items meet the
Product Vision and increase the product's value.
• The Sprint Planning is time-boxed, and The Scrum Team needs to discuss
three questions: why is this Sprint valuable, what can be done this Sprint, how
will the chosen work get done.
• During the Daily Scrum, the Scrum Team inspects the progress and
impediment, adapts the Sprint Backlog, and adjusts the upcoming plan.
• Daily Scrum is held every day and 15-minus timeboxed.
• Developers answer those three questions.
What I did yesterday.
What I will do today.
What impediments hold me back.
The Daily Scrum
• The purpose of the Sprint Review is to inspect the outcome that the Scrum
Team accomplished during the Sprint and discuss what they will do for the
next Sprint based on the outcome and changes of the environment.
• The Scrum Team demonstrates the outcome to key stakeholders during the
Sprint Review.
• Sprint Review is timeboxed to a maximum of four hours for a one-month
Sprint. If the Sprint is less than a month, Sprint Review is also shorter.
Sprint Review
• The purpose of the Sprint Retrospective is to share and discuss what they can do better
for future improvement based on the current Sprint.
• The topics can be anything as long as they improve to achieve better values such as
process, tools, technologies, communication, etc.
• As the result of the Sprint Retrospective, the Scrum Team picks up the most helpful
changes to create the Product Backlog to implement in the next Sprint.
Sprint Retrospective
Actionable Advice
You can implement Scrum:
1. Create Scrum Team and assign Scrum Master, Product Owner,
and Developers.
2. Create the Product Backlog.
3. Hold Scrum Event.
Actionable Advice
• If you want to transform your company's project into a Scrum
way, focus on training and educating the Scrum Master first
because she is the key person.
• If you want to be the Scrum Master, repeatedly read an official
Scrum Guide and try to implement the way it says.
Actionable Advice
❏ Scrum Guide Online
https://www.scrumguides.org/scrum-guide.html
❏ The Professional Product Owner
https://amzn.to/31OVCLp
❏ Scrum.org
https://www.scrum.org/
References
That’s all

Essentials of Scrum

  • 1.
  • 2.
    1. What isScrum? 2. Scrum Artifacts 3. Scrum Team 4. Scrum Events 5. Actionable Advice Agenda
  • 3.
  • 4.
    • Scrum isa project management framework in software development. • Scrum is one of the implementations of Agile. • Scrum is widely and globally used because it is lightweight, effective, and efficient. What is Scrum?
  • 5.
    Scrum can beused Scrum can be used in various types of software projects. 1. Research & Development 2. Minimum Viable Product(MVP) 3. Cloud Computing Development 4. Web & mobile Development5. Product renewal
  • 6.
    Scrum & Agile& Lean Agile is an umbrella concept of software development, while Scrum, eXtreme Programming, and Crystal are implementations.
  • 7.
    IT Company Performance •Project performance consists of 3 components: leadership, management, and technology. • Scrum covers leadership and management to boost performance.
  • 8.
  • 9.
    Scrum Theory Scrum isfounded on three core theories to be empiricism, lean, and flexible. • Transparency • Inspection • Adaptation
  • 10.
    Transparency • The ScrumTeam is transparent through the artifacts and events. Features, progress, and communication must be transparent to all who get involved in the project. • Transparency increases the value of the product because it leads to valuable discussion. • Transparency enables inspection. Inspection cannot be done without transparency.
  • 11.
    Inspection • The ScrumTeam constantly checks and shares the progress and goal to detect the potential risks. • Inspection is conducted through the five Scrum events: Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. • Inspection enables adaptation. As a result of the inspection, the Scrum Team can adapt to change.
  • 12.
    Adaptation • The ScrumTeam is adaptable to be flexible and prevent deviation as a result of the inspection. • Adaptation is one of the critical characteristics of the Scrum Team in order to meet the changeable market and customer requests. • Adaptation prevents the common mistake that the software development team creates unwanted products after spending a long time developing.
  • 13.
  • 14.
    Scrum Values Focus :The Scrum Team focuses on the Sprint Goal to complete delivery. Openness : The Scrum Team is open to communicating, sharing ,and helping. Courage : The Scrum Team challenges the status quo to innovate. Commitment : The Scrum Team is committed to the team. Respect : The Scrum Team respect each other.
  • 15.
  • 16.
    First, you mustunderstand three core artifacts of Scrum • Product Backlog • Sprint Backlog • Increment Scrum Artifacts
  • 17.
    Product Backlog • isthe most important artifact in Scrum because it describes everything of the product: functions, requirements, enhancements, bug fixes, etc, and prioritizes them. • Is associated with one product. Even though multiple teams work for a single product, the Product Backlog must be one. • Exists and evolves as long as the product lives and evolves. Product Backlog
  • 18.
    Product Backlog containsthe following items. • User Story • As a <person>, I would like to <what> so that <reason> • As a e-commerce user, I would like to filter specific categories so that I can search the product that I want to buy. • Priority • Acceptance Criteria • Estimation Product Backlog Template
  • 19.
    Sprint Backlog • SprintBacklog is the set of Product Backlog Items selected to achieve for the upcoming Sprint. • The Development Team estimates to select based on the priority of the Product Backlog and realistic forecast. • Sprint Backlog is updated throughout the Sprint as the development progress.
  • 20.
    Increment Increment • is thesum of all the Product Backlog items completed in all previous Sprints. • is created when the Product Backlog meets the definition of done that is the common understanding of completion in the project. • is releasable whenever the Product Owner wants to release.
  • 21.
  • 22.
  • 23.
    The Product Owner: •is responsible for maximizing the value of the product by clarifying, managing, and prioritizing the Product Backlog. • ensures the Product Backlog is visible, transparent, and clear to all. • is a one person, not a committee. The Product Owner
  • 24.
    Developers • are responsiblefor creating increments throughout the Sprint. • Plan for the Sprint by selecting the Sprint Backlog. • Ensure the quality of the product by having a professional skills and adhering to Definition of Done. Developers
  • 25.
    The Scrum Master: •plays a key role in the team to establish the Scrum. • removes impediments in the team so that the Scrum Team can work smoothly and effectively. • facilitates the Scrum Events to be positive, productive, and time- boxed. The Scrum Master
  • 26.
  • 27.
    Scrum Events aremeetings that are held during the Sprint for smooth communication, checking the progress, and achieving the Sprint goal. • Sprint • Sprint Planning • Daily Scrum • Sprint Review • Sprint Retrospective What are Scrum Events
  • 28.
    The Sprint The Sprint: •is a fixed-length event that the Scrum Team works to make Increments. • All Scrum Events: Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective are held during the Sprint. • must be less than a month, and the shorter the Sprint, the better because the Scrum Team can generate more learning cycles.
  • 29.
    The Sprint Planning •During the Sprint Planning, The Scrum Team plans which Product Backlog items they work on to complete at the end of the Sprint. • The Scrum Team discusses to decide which Product Backlog items meet the Product Vision and increase the product's value. • The Sprint Planning is time-boxed, and The Scrum Team needs to discuss three questions: why is this Sprint valuable, what can be done this Sprint, how will the chosen work get done.
  • 30.
    • During theDaily Scrum, the Scrum Team inspects the progress and impediment, adapts the Sprint Backlog, and adjusts the upcoming plan. • Daily Scrum is held every day and 15-minus timeboxed. • Developers answer those three questions. What I did yesterday. What I will do today. What impediments hold me back. The Daily Scrum
  • 31.
    • The purposeof the Sprint Review is to inspect the outcome that the Scrum Team accomplished during the Sprint and discuss what they will do for the next Sprint based on the outcome and changes of the environment. • The Scrum Team demonstrates the outcome to key stakeholders during the Sprint Review. • Sprint Review is timeboxed to a maximum of four hours for a one-month Sprint. If the Sprint is less than a month, Sprint Review is also shorter. Sprint Review
  • 32.
    • The purposeof the Sprint Retrospective is to share and discuss what they can do better for future improvement based on the current Sprint. • The topics can be anything as long as they improve to achieve better values such as process, tools, technologies, communication, etc. • As the result of the Sprint Retrospective, the Scrum Team picks up the most helpful changes to create the Product Backlog to implement in the next Sprint. Sprint Retrospective
  • 33.
  • 34.
    You can implementScrum: 1. Create Scrum Team and assign Scrum Master, Product Owner, and Developers. 2. Create the Product Backlog. 3. Hold Scrum Event. Actionable Advice
  • 35.
    • If youwant to transform your company's project into a Scrum way, focus on training and educating the Scrum Master first because she is the key person. • If you want to be the Scrum Master, repeatedly read an official Scrum Guide and try to implement the way it says. Actionable Advice
  • 36.
    ❏ Scrum GuideOnline https://www.scrumguides.org/scrum-guide.html ❏ The Professional Product Owner https://amzn.to/31OVCLp ❏ Scrum.org https://www.scrum.org/ References
  • 37.