Scrum Process Chart

Process Chart
Scrum Flow
Daily
Create Daily Standup
Release Schedule Deliverables Meeting
Release Planning Session
Sprint
1-6 weeks
Project Project Vision Prioritized Sprint Accepted

Business Case Statement Product Backlog Backlog Deliverables
Project Vision Sprint Planning Meeting Sprint Review Meeting
Meeting Retrospect Meeting
Scrum Phases and Processes
Review &
Initiate Plan & Estimate Implement Release
Retrospect
Create Project Create User Stories Create Deliverables Demonstrate and Ship Deliverables
Vision Validate Sprint
Identify Estimate User Conduct Daily Retrospect Sprint Retrospect Project

Scrum Master & Stories Standup
Stakeholder(s)
Form Scrum Team Commit User Groom Prioritized

Stories Product Backlog
Develop Epics Identify Tasks
Create Prioritized Estimate Tasks

Product Backlog
Conduct Release Create Sprint

Planning Backlog
© 2017 VMEdu, Inc. V4

SCRUM ON A PAGE
SCRUM PRINCIPLES ROLES ARTIFACTS MEETINGS
Empirical Process Control CORE: Project Vision Statement Project Vision Meeting
Scrum prescribes making decisions Explains the business need the Stakeholders meet to identify the business
based on observation and Product Owner project is intended to meet and context, business requirements, and stakeholder
experimentation rather than detailed should focus on the problem rather expectations in order to develop an effective
upfront planning. • Defines the Project Vision and Release Schedule than the solution. Project Vision Statement.
as the “Voice of the Customer”
• Defines customer requirements in the form of
Prioritized Product Backlog
1
Self-organization Epics/User Stories and clarifies these requirements 2 Release Planning Meeting
Scrum believes that today’s workers for team members 3
A prioritized list of requirements that, The purpose of this meeting it to develop a
4
have much more knowledge to offer • Prioritizes items on the Product Backlog according when turned into potentially shippable Release Plan which defines when various sets of
than just their technical expertise and to business value product functionality, will deliver the usable functionality or products will be delivered
that they deliver greater value when • Provides Acceptance/Done Criteria and inspects Project Vision. Owned by the Product to the customer.
self-organized. deliverable(s) to validate them Owner.
Sprint Planning Meeting

Collaboration Scrum Master Sprint Goal
The primary output of this meeting is the
In Scrum, product development is a • Ensures that Scrum processes are correctly Proposed by the Product Owner and Sprint Backlog. Task Planning and
shared value-creation process that followed by all Scrum Core Team members, accepted by the team, it is a one Task Estimation are accomplished during
needs all the stakeholders working and including the Product Owner sentence aim for the current Sprint. Sprint Planning. Time-boxed to 8 hours for a
interacting together to deliver the 1 month Sprint.
greatest value. • Ensures that an ideal project environment exists
for the Scrum Team to successfully complete
Sprints
Sprint Backlog
Daily Standup Meeting
3
2
A list of items the Scrum Team commits 1
Value-based Prioritization • Oversees Release Planning Sessions and

to execute in the upcoming Sprint.
convenes other meetings Short, daily meeting time-boxed to 15 minutes.
Delivering the greatest value in the Any risk mitigating activities are also Each Scrum Team member answers the following
• Acts as a servant-leader that helps motivate and
shortest amount of time requires included as tasks in the Sprint Backlog. three questions:
coach the team
prioritization and selection of what
• What have I done since the last meeting?
could be done from what should be
done. Scrum Team Impediment Log • What do I plan to do before the next me
Impediments or obstacles encountered • What impediments or obstacles (if any) am I
• Typically a small team of 6-10 members with no currently facing?
Time-boxing by the team should be formally recorded
further sub-division of teams
by the Scrum Master in an Impediment
Time is treated as a limiting constraint • Cross-functional and self-organizing, the Scrum Log.
and time-boxing is used as the rhythm Team enjoys complete autonomy during a Sprint Sprint Review Meeting
to which all stakeholders work and • Members are generalists across domains and
The Scrum Team presents the completed Sprint
contribute. specialists in at least on area Product Increment deliverables to the Product Owner who either
• Responsibility of the work lies with the whole team $ The potentially shippable deliverable accepts or rejects them based on the defined
Iterative Development of the team at the end of each Sprint Acceptance and Done Criteria. Time-boxed
that satisfies the Acceptance and to 4 hours for a 1 month Sprint.
The customer may not always be able to NON-CORE ROLE: Done Criteria.
define very concrete requirements.
The iterative model is more flexible in Retrospect Sprint Meeting
accommodating changing requirements.
Stakeholders Team members discuss what went well during
the previous Sprint and what did not go well,
• Customers the goal being to learn and make improvements
• Users in the Sprints to follow. Time-boxed to 4 hours
• Sponsors for a 1 month Sprint.
Vendors
Scrum Guidance Body
© 2017 VMEdu, Inc. v4

Scrum Process Chart

Uploaded by

Copyright:

Available Formats

Scrum Process Chart

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Scrum Process Chart

Uploaded by

Copyright:

Available Formats

Process Chart

Project Project Vision Prioritized Sprint Accepted

Scrum Phases and Processes

Identify Estimate User Conduct Daily Retrospect Sprint Retrospect Project

Form Scrum Team Commit User Groom Prioritized

Develop Epics Identify Tasks

Create Prioritized Estimate Tasks

Conduct Release Create Sprint

© 2017 VMEdu, Inc. V4

Sprint Planning Meeting

A list of items the Scrum Team commits 1

Value-based Prioritization • Oversees Release Planning Sessions and

© 2017 VMEdu, Inc. v4

You might also like