Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

Agile Development using Scrum

No description
by

Ryan Quellhorst

on 11 February 2015

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Agile Development using Scrum

Product Backlog
Sprint Backlog
Sprint 1
Increment 1
Feedback
Sprint Planning
Daily Scrum
Sprint Review
Sprint
Retrospective
Product Backlog
Sprint Backlog
Sprint 2
Increment 2
Feedback
Sprint Planning
Daily Scrum
Sprint Review
Sprint
Retrospective
Product Backlog
Sprint Backlog
Sprint 3
Increment 3
Sprint Planning
Daily Scrum
Sprint Review
Sprint
Retrospective
Feedback
Scrum Events and Artifacts
Sprint Planning objective:
The
Development Team
forecasts of the amount of work to be done this sprint and selects items from the Product Backlog.

Creation of the
sprint goal
(objective that will be met within the Sprint through the implementation of the Product Backlog).

Explanation by the Development Team to the Product Owner and Scrum Master on how it intends to work as a self-organizing team to accomplish the Sprint Goal and create the anticipated Increment.

The
time box is 8 hours
when the sprint is 4 weeks (a month). For shorter Sprints it is usually shorter.



Sprint Planning
Scrum Team
Product Owner
Scrum Master
Development Team
Agile Development using Scrum
By: Ryan Quellhorst
Scrum Theory
Empiricism
Agile Manifesto
The creators of Scrum, Jeff Sutherland and Ken Schwaber, and other developers were authors of the Agile Manifesto.













While this is not on the PSM I exam it helps to understand the thought process behind Scrum.
The Agile Manifesto
Transparency
Inspection
Adaption
Empiricism
- knowledge comes from experience and making decisions based on what is known. Scrum employs an iterative, incremental approach to optimize predictability and control risk.


Transparency
- Significant aspects of the process must be visible to those responsible for the outcome.

Inspection
- Frequent examination of Scrum artifacts and progress toward a Sprint Goal to detect undesirable variances.

Adaptation
- If one or more aspects of a process deviate outside acceptable limits, and that the resulting product will be unacceptable, the process or the material being processed must be adjusted.


Empiricism
Empirical Process Control

Scrum:
A
framework
within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value.

The Scrum framework consists of Scrum Teams and their associated roles, events, artifacts, and rules.
Each component within the framework serves a specific purpose and is essential to Scrum’s success and usage.

What is Scrum?
Scrum.org is the institution that administers the PSM exam.

Founded by Ken Schwaber, one of the founding members of Scurm, in 2009.

 Provides all of the tools and resources needed by Scrum practitioners and experts in agility to deliver value using Scrum. 

A link to the latest Scrum guide is on their website.

Open Assessment is available to Scrum.org members (free membership).

Very active forum full of Scrum Masters who’ve taken the exam, are a part of a Scrum team, and some are teaching the Scrum framework.



Scrum.org
80 Questions
60 minutes to complete
Multiple choice and true/false questions
85% to pass
$100 per attempt
Administered online

You have roughly 45 seconds per question (The test goes by very fast).

You can miss 12 questions and pass.

Many of the questions test your understanding of Scrum and can’t be answered by just rote learning the material.

Many questions will drop you into a situation and ask how you’d handle it using the Scrum framework.

PSM I Exam
PSM I Exam Screen
Timebox
Counts Down
Previous Button
Returns you to the previous question
Slow way of reviewing the test
Questions/Answers
Next Button
Sends you to the next question
Bookmark Button
Sends you to the bookmark screen
Quickest way of reviewing the test
Bookmark Checkbox
Allows you to mark the question for further review later

PSM I Exam Screen
Question Number
Is hyperlinked to the question.
Click the number and it’ll take you to the question.
Bookmark Checkmark
Indicates questions that you bookmarked.
Disappears when you uncheck the bookmark checkbox on the question screen.
On questions where you’re asked to give more than one answer (e.g. select 2 responses) if an answer is selected but not all answers that were asked for were selected the answer square will still show solid blue.
Answer Square
Indicates questions that you’ve answered.
Solid blue squares indicate that the question has an answer
Blue outline means that the question does not have an answer selected.
Which statement best describes Scrum? 

A. A complete methodology that defines how to develop software.

B. A cookbook that defines best practices for software development.

C. A framework within which complex products in complex environments are developed.

D. A defined and predictive process that conforms to the principles of Scientific Management.


Review Question #1
Upon what type of process control is Scrum based?

A. Empirical

B. Hybrid

C. Defined

D. Complex



Review Question #2
The three pillars of empirical process control are:

A. Respect For People, Kaizen, Eliminating Waste

B. Planning, Demonstration, Retrospective

C. Inspection, Transparency, Adaptation

D. Planning, Inspection, Adaptation

E. Transparency, Eliminating Waste, Kaizen




Review Question #3

1 Person
Full time or part time
Business Oriented
Only person responsible for the Product Backlog
Gather requirements from the stakeholders
May represent the desires of a committee
Ultimately, has the
final say in the product backlog


Product Owner

Responsibilities
Maximize the value of the product and the work of the Development Team.
Manage the Product Backlog.
Maximize the value of the product and the work of the Development Team.
Make sure the Development Team understands the items in the Product Backlog.


3 – 9 People

No titles and no sub-teams
Everyone on the team has the same title; developer.
There are no testers or QA group.
Individuals may have areas of expertise but accountability lies on the group.

Development Team

Self-organizing
– No one tells the Development Team how to turn Product Backlog into Increments of potentially releasable functionality.

Cross functional
– Everyone on the team has the necessary skills to turn product backlog items into a increment of functionality.

The Development Team should change very little.
There is a decrease in productivity when the team changes.

Only the Development Team can create an increment of “Done.”
No outside help is necessary for the Development Team to create and increment of functionality.

Development Team

Responsibilities
Turn the product backlog into increments of functionality that is potentially releasable and adhere to the definition of done.
Attend all of the Scrum events.

1 person

Full-time or part-time

Fully understand the Scrum framework.

Manages the Scrum framework, but doesn’t manage the team.

Works to maximize the value created by the Scrum team.

Scrum Master
Responsibilities
Lead and coach the Product Owner, Development Team, and organization on how to implement Scrum.
Make sure that the Scrum Team and organization follows the Scrum theory, practices, and rules and coaches when there are deviations from the framework.
Remove impediments to the Development Team’s progress.

Who is on the Scrum Team?
Select all answers that apply

A. Product Owner

B. Product Manager

C. QA Team

D. The CEO

E. Scrum Master

F. Development Team
Review Question #4
Who can remove a team member from the Development Team?

A. Product Owner

B. Development Team

C. Product Manager

D. Scrum Master

E. Human Resources (HR)
Review Question #5
The Development Team should have all the skills needed to:

A. Turn the Product Backlog items it selects into an increment of potentially shippable product functionality.

B. Complete the project as estimated when the date and cost are committed to the Product Owner.

C. Do all of the development work, but not the types of testing that require specialized testing, tools, and environments.

Review Question #6
Do Scrum Teams need a Product Owner and/or Scrum Master?

A. Yes, both positions are needed 100% of the time.

B. Yes, both positions are needed, but they can be part time.

C. The Product Owner can be replaced by a committee that manages the product backlog.

D. The Scrum Master is not needed. As soon as the team understands the Scrum framework and has proven it can work independently.

E. The Product Owner and Scrum Master are not needed, because they don’t contribute to the increment of functionality.
Review Question #7

Each event is
time boxed
which means every event has a
maximum duration
, but can be cut short if the purpose of the event has been achieved.

Every event is a formal opportunity to
inspect
and
adapt
.

The events create
regularity
and
minimize
the need for
meetings
not defined in Scrum

Scrum Events
Sprint objective - Creation of a
“Done”, useable,
and potentially
releasable
product increment.

The time box is 4 weeks (one month) or less.
The duration
should not change
during the sprint and should
rarely change
throughout the project

Sprints contain:
Sprint Planning
Daily Scrums
development work
Sprint Review
Sprint Retrospective

The Sprint
The next sprint begins
immediately
after the last sprint ends.

During the Sprint:
No changes are made that would endanger the Sprint Goal.
Quality goals do not decrease.
Scope may be clarified and re-negotiated between the Product Owner and Development Team as more is learned.

A sprint can be canceled by the
Product Owner
if the Sprint Goal becomes obsolete.

The Sprint
Daily Scrum objective
- Inspecting the work since the last Daily Scrum and forecasting the work that could be done before the next one.
Identifying what is/was helpful for the Development Team to reach its Sprint Goal.
Identifying impediments that might jeopardize the Sprint Goal.

The time box is 15 minutes.


The
Scrum Master
and the
Development team
are the only people allowed to participate in the Daily Scrum.

The Development Team is responsible conducting the Daily Scrum.

The Scrum Master ensures that the daily Scrum is occurs and is kept within the 15 minute time box.

Daily Scrum

Sprint Review objective:

Scrum Team and stakeholders collaborate about what was done in the Sprint.

Based on that and any changes to the Product Backlog during the Sprint, attendees collaborate on the next things that could be done to optimize value.

The time box is 4 hours
when the sprint is 4 weeks (a month). For shorter Sprints it is usually shorter.

Result of the Sprint Review:
A Revised Product Backlog that defines the probable Product Backlog items for the next Sprint.



Sprint Review

Sprint Retrospective objective:

Inspect how the last Sprint went with regards to people, relationships, process, and tools;

Identify and order the major items that went well and potential improvements; and,

Create a plan for implementing improvements to the way the Scrum Team does its work.

The
time box is 3 hours
when the sprint is 4 weeks (a month). For shorter Sprints it is usually shorter.

There aren’t many questions on the PSM I that cover the Sprint Retrospective
Sprint Retrospective
The time box for a Daily Scrum is? 

A. The same time of day every day.

B. Two minutes per person.

C. 4 hours.

D. 15 minutes.

E. 15 minutes for a 4 week sprint. For shorter Sprints it is usually shorter.

Review Question #8
Who determines the amount of work that is to be completed during the sprint? 

A. Scrum Master

B. Development Team

C. Product Owner

D. A and B

E. A and C

F. B and C

G. A, B, and C

Review Question #9
Which of the following is a topic for the Product Owner if the sprint is in progress?
 Select all answers that apply
 
A. Answer questions from the Development Team about items in the current Sprint.

B. Reorder the Product Backlog based on new market conditions.

C. Working together with the stakeholders.

D. Update the Sprint burndown chart.

E. Provide feedback.


Review Question #10
If the development team does not have all of the skills to accomplish the sprint goal, the Scrum Master should:

A. Cancel the sprint.

B. Cancel SCRUM.

C. Have the development team determine the definition of “Done” and work through the spring backlog.

D. None of the above

Review Question #11
The Scrum Master realizes that Product Owner attends all Daily Scrums and asks Team Members about their tasks and gives them directions for the following day. What should the Scrum Master do? 

A. It’s wrong, the Product Owner should not attend Daily Scrum.

B. It’s wrong, the Product Owner should not speak in the Daily Scrum.

C. It’s OK, the Product Owner is a part of the business and functions like a Project Manager in Scrum.  

D. It’s OK, it’s recommended for the Product Owner to give direction.


Review Question #12
The Development team does not see the benefit in Sprint Retrospective and are considering canceling the remainder Sprint Retrospectives. What action should the Scrum Master take?

A. Allow the Development Team to cancel the Sprint Retrospectives. Development Teams are structured and empowered by the organization to organize and manage their own work.

B. Allow the Development Team to cancel the Sprint Retrospectives. Development Teams are self-organizing. No one (not even the Scrum Master) tells the Development Team how to turn Product Backlog into increments of potentially releasable functionality.

C. Don’t allow the Development Team to cancel the Sprint Retrospectives. The Scrum Master’s role is to manage the Development Team and to make sure Scrum procedures are followed.

D. Don’t allow the Development Team to cancel the Sprint Retrospectives. Sprint Retrospectives are an integral part of Scrum that allows the team to inspect and adapt. The Scrum Master should coach the team to understand the purpose of the Sprint Retrospective.


Review Question #13
Product Backlog
: an ordered list of everything that might be needed in the product and is the single source of requirements for any changes to be made to the product.
The Product Backlog lists all features, functions, requirements, enhancements, and fixes that constitute the changes to be made to the product in future releases.
As feedback from the Scrum events is received the Product Backlog will change.
Changes in business requirements, market conditions, or technology may cause changes in the Product Backlog.

The
Product Owner
is responsible for the Product Backlog’s:
Content
Availability
Order

The
Development Team
is responsible for estimating the work for each product backlog attribute
Product Backlog
Product Backlog refinement
is the act of adding detail, estimates, and order to items in the Product Backlog.

This is an ongoing process in which the
Product Owner
and the
Development Team
collaborate on the details of Product Backlog items.

The Product Backlog
doesn’t have to be fully complete
before Sprint 1. There just has to be enough items for a complete sprint.

When
multiple Scrum teams
work on the same product there is only
one product backlog
.

Product Backlog
Sprint Backlog:
the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal.

The Sprint Backlog makes visible all of the work that the Development Team identifies as necessary to meet the Sprint Goal.

The Sprint Backlog is determined during the Sprint Planning.

The Development Team modifies the Sprint Backlog throughout the Sprint, and the Sprint Backlog emerges during the Sprint.

Only the
Development Team
can change its Sprint Backlog during a Sprint.


Sprint Backlog
Increment
- the sum of all the Product Backlog items completed during a Sprint and the value of the increments of all previous Sprints.

The increment must be “Done” which means it’s useable and meets the Scrum team’s definition of “Done.”

The Product Owner may or may not decide to release the increment, but it should be releasable.



Increment
“Done”
: a shared understanding of what it means for work to be complete, to ensure transparency.

Guides the Development Team in knowing how many Product Backlog items it can select during a Sprint Planning.

Each Increment is additive to all prior Increments and thoroughly tested, ensuring that all Increments work together.

For multiple Scrum Teams working on the system or product release all of the Scrum Teams must jointly define the definition of “Done.”
Definition of “Done”
Burn Down Chart
- shows the amount of remaining work
Release Burn Down
- measures remaining Product Backlog across the time of a release plan.
The Product Owner is responsible for updating the Release Burn Down.

Sprint Burn Down
: measures remaining Sprint Backlog items across the time of a Sprint.
Scrum Guide 2009 does not mention who is responsible for the Sprint Burn Down.
From the latest Guide (2013): The Development Team tracks this total work remaining at least for every Daily Scrum. The Development Team tracks these sums daily and projects the likelihood of achieving the Sprint Goal.

Burn Down charts are not in the latest Scrum Guide 2013, but do show up on the PSM I exam.
Monitoring Progress
Monitoring Progress
What happens to the definition of “Done” when multiple Development Teams are working on a single product? 

A. Each team defines its own “Done”, and communicates it with others so that everyone knows what it means when a team claims that they are Done with something.

B. Each team defines its own “Done”, in a way that the integration of their work results in a definition of “Done” that is potentially releasable.

C. They all use the same definition of “Done.” 

D. Any of the above answers, based on the nature of the project and the environment of the organization.


Review Question #14
Can the Scrum Team deliver only documentation at the end of the sprint if the Product Owner asks for it? 

A. Yes, As long as the documentation is a part of the Sprint Backlog and delivers value to the organization.

B. Yes, documentation is essential in recording the Scrum Team’s progress.

C. No, the purpose of a sprint is to produce a working increment on functionality.

D. No, documentation is not important in Scrum Teams and is not mentioned in the most recent Scrum Guide.



Review Question #15
Which best describes the Release Burn Down Chart?

A. The Release Burn Down shows the work remaining in the Product Backlog.

B. The Release Burn Down shows the work remaining in the Sprint Backlog.

C. The Release Burn Down shows the work completed in the Product Backlog.

D. The Release Burn Down shows the work completed in the Sprint Backlog.



Review Question #16
Read and understand the Scrum Guide (latest guide link on scrum.org).
Take the Open Assessment on scrum.org.
Some of the Open Assessment’s questions are in the PSM.
Take the Developer Assessment on scrum.org.
A different question bank than the Open Assessment. Some questions don’t apply, but going through this assessment allows you to see some different questions.
Watch Scrum Training Series Videos.
http://scrumtrainingseries.com/
Cartoon characters that guide you through the process and is full of info and quizzes.
Use the Scrum.org forums to ask questions and view messages.
There are a lot of really smart people discussing Scrum.
There are very deep discussions about the framework.
Read Scrum - A Pocket Guide (Best Practice)
It gets to the heart of why Scrum is setup the way it is
http://amzn.com/9087537204

PSM I Exam Study Tips
Full transcript