Church Building Grants To Assist With New Construction, Additions, And Restor...
ScrumMaster Certification Course Agenda
1. 1
Certified ScrumMaster 2009
presented by
Montag, 15. Juni 2009
2. NOKIA - TEST
1. Do they deliver working software at the end
of each Sprint (less than 4 weeks) that is tested
at the feature level.
Montag, 15. Juni 2009
3. NOKIA - TEST
2. Do they do just enough specficiation before
starting a Sprint and is their Product Backlog
ready?
Montag, 15. Juni 2009
4. NOKIA - TEST
3. Do they have a Product Owner. A Product
Backlog? Is it estimated by the team?
Montag, 15. Juni 2009
5. NOKIA - TEST
4. Does the team have a burndown chart and
does the team know their velocity?
Montag, 15. Juni 2009
6. NOKIA - TEST
5. Is their team free from disruption during the
Sprint?
Montag, 15. Juni 2009
7. 7
GOAL: DELIVER A BROCHURE FOR THE EARTH TOURIST
BOARD LOCATED ON MARS
• Create cover art, brand, • Outline a “7 wonders of the
and/or logo world” expedition
• Define major topics for • Set prices for the tours
Martian tourism • Outline warning messages
• Describe “Art Interests in (gravity, oxygen, fungi,etc.)
Europe” tour • Suggest clothing options
• Describe a tour based on • Explain travel options to/
photosynthesis from Mars
Montag, 15. Juni 2009
8. “Equally responsible for the initiation of project with predefined
failure is management that insists upon having fixed
commitments from programming personnel prior to the latter’s
understanding what the commitment are for. Too frequently,
management does not realize that in asking the staff for “the
impossible”, the staff will feel the obligation to respond out of
respect, fear or misguided loyalty. Saying “no” to the boss
frequently requires courage, political and psychological wisdom,
and business maturity that comes with much experience.”
-- The Management of Computer Programming Projects" by
Charles Lecht. 1967
Montag, 15. Juni 2009
41. Concept of Psychological Safety Accountability for Meeting Demanding Goals
Demanding Goal
Low High
Learning secret #2
High Comfort Zone
Psychological
Zone
Safety
Low Apathy Zone Anxiety Zone
The competitive Imperative of Learning, Amy C Edmondson,
HBR, 7/8 2008, p. 60-66
Montag, 15. Juni 2009
42. Who goes to the
Retrospective?
Montag, 15. Juni 2009
47. “Regardless of what we discover, we
understand and truly believe: that
everyone did the best job they could,
given what they knew at the time, their
skills and abilities, the resources
available, and the situation at hand.”
-- Norman Kerth , Project Retrospectives
Montag, 15. Juni 2009
57. everybody
the team invites
secret #5
Montag, 15. Juni 2009
58. He/she makes it happen!
He/she needs to act!
secret #6
Montag, 15. Juni 2009
59. 59
Complexity / Empirical Management
Montag, 15. Juni 2009
60. 60
step factory enterprise
Montag, 15. Juni 2009
61. 61
Stacey and Complexity
unstable •Timebox
•Emergent
Emergent Requirements
Software
Time •Complexity
•Anarchy
stable
known Technology unknown
•You need boundaries!
Every Activity in Scrum is Timeboxed! http://www.plexusinstitute.org/
edgeware/archive/think/
main_aides3.html
Montag, 15. Juni 2009
62. 62
It is typical to adopt the defined (theoretical)
modeling approach when the underlying
mechanisms by which a process operates are
reasonably well understood.
Montag, 15. Juni 2009
63. When the process is too complicated for the
defined approach, the empirical approach is
the appropriate choice
Montag, 15. Juni 2009
66. 66
• The New New Product Development
Game, by Nonaka and Takeuchi
• Lean Management, Deming and Juran
• Iterative and incremental
development, Barry Boehm
• First Implemenations, Jeff Sutherland
agile foundation
Montag, 15. Juni 2009
67. HBR
J A N U A RY– F E B R U A RY 1 9 8 6
The rules of the game in new product
development are changing. Many
companies have discovered that it
takes more than the accepted basics
of high quality, low cost, and
The New New Product differentiation to excel in today’s
competitive market. It also takes
Development Game
speed and flexibility. This change is
Hirotaka Takeuchi and Ikujiro Nonaka
reflected in the emphasis companies
are placing on new products as a
source of new sales and profits. At
3M, for example, products less than
T five years old account for 25% of
he rules of the game in new product develop- would account for one-third of all profits in the 1980s,
ment are changing. Many companies have an increase from one-fifth in the 1970s.1
sales
discovered that it takes more than the ac- This new emphasis on speed and flexibility calls
cepted basics of high quality, low cost, and differen- for a different approach for managing new product
tiation to excel in today’s competitive market. It also development. The traditional sequential or “relay
takes speed and flexibility. race” approach to product development—exempli-
This change is reflected in the emphasis companies fied by the National Aeronautics and Space Admin-
are placing on new products as a source of new sales istration’s phased program planning (PPP) system—
and profits. At 3M, for example, products less than may conflict with the goals of maximum speed and
five years old account for 25% of sales. A 1981 survey flexibility. Instead, a holistic or “rugby” approach—
of 700 U.S. companies indicated that new products where a team tries to go the distance as a unit, passing
In today’s fast-paced, fiercely competitive world of com- Mr. Takeuchi is an associate professor and Mr. Nonaka,
mercial new product development, speed and flexibility a professor at Hitotsubashi University in Japan. Mr.
are essential. Companies are increasingly realizing that Takeuchi’s research has focused on marketing and global
the old, sequential approach to developing new products competition. Mr. Nonaka has published widely in Japan
simply won’t get the job done. Instead, companies in Japan on organizations, strategy, and marketing.
Montag, 15. Juni 2009
68. The Knowledge-Creating
Company
by Ikujiro Nonaka
Editor’s Note: This 1991
article helped popularize the
notion of “tacit” knowledge—
the valuable and highly
subjective insights and
intuitions that are difficult to
capture and share because
people carry them in their
heads.
Montag, 15. Juni 2009
69. Yahoo Chief Product Owner – “Scrum is faster, better,
cooler! It’s the way we first built software at Yahoo,
yet is scalable to large, distributed, and outsourced
teams.”
Montag, 15. Juni 2009
73. ScrumMaster
The Film Director -- He protects the team from all
distrubances. He is not part of the team. He
improves the productivity of the Scrum-Team and
controls the “inspect and adapt” cycles of Scrum . He
makes sure that the agile ideals are understood and
that they are respected by all stakeholders. He is not
responsible for the delivery of the product.
Montag, 15. Juni 2009
79. Product Owner
The Storywriter -- She drives the Product Owner from
the business point of view. She communicates a clear
vision of the product and she defines its main
characteristics. She also accepts the product at the end
of a Sprint. She makes sure that the team only works
on the most valuable Backlog Items. She has the same
goal as the team. She is responsible for the return on
investment.
Montag, 15. Juni 2009
84. Establish and
maintain
Releaseplan
Montag, 15. Juni 2009
85. The Team
The Actors -- They deliver the product and
they are responsible for the quality. They
work with End User, PO and Customers to
understand the business requirements. The
Teams performs its commitment
voluntarily. They work continuously with
the PO to define the strategic direction of
the project.
Montag, 15. Juni 2009
86. 86
Deliver
Deliver
Deliver
Montag, 15. Juni 2009
91. Customer
The Producer -- She requests the product.
She contracts the organization for
developing products. Typically these are
executive managers who by software
development from external software
development companies. In an internal
product development organization this is
the person who is responsible for approving
the budget for product development.
Montag, 15. Juni 2009
95. Manager
The Studio Boss -- Management is essential
in Scrum Organisations. It enables the Team to
work by building the right work environment
for Scrum Teams. Managers create structure
and stability. He also works with the
ScrumMaster to re-factor the structures of the
organization and guidelines when necessary.
Montag, 15. Juni 2009
96. Makes sure a
organizations
will survive in
case of failures
Ed Cutmil: Havard Business Review, 2008
Montag, 15. Juni 2009
98. End User
The Audience -- Can be played by a
lof to people. The End-User is the one
who knows the requirements and with
this knowledge he defines the product
by telling the team what he needs
from its functionality.
Montag, 15. Juni 2009
103. ScrumMaster works with
Product Owner to ensure the
Product Owner fulfills his job.
ScrumMaster coaches the
Product Owner and helps him
against outsides odds.
Montag, 15. Juni 2009
104. ScrumMaster works with the
Team to ensure that everyone
agrees what he had agreed to
do! Protects the Teams.
Removes impediments
Montag, 15. Juni 2009
105. Product Owner works with the
customer to ensure that he
meets her own return on
investment.
Customer will push the Product
Owner but she will keep her
interests in mind.
Montag, 15. Juni 2009
106. Team works with End User to
understand the needs of the
End-User. To write the
application according to
spezifications of the End-User
Montag, 15. Juni 2009
107. ScrumMaster works with the Manager to re-
factor guidelines and processes, to ensure the
Scrum-Teams gets what it needs.
Montag, 15. Juni 2009
108. Product Owner needs to know
what the market (the End User)
wants to have. He needs to
know the needs to be able to
prioritize the product Backlog
Montag, 15. Juni 2009
109. References
Agiles Projektmanagement mit Scrum, Ken Schwaber
Agile Software Development with Scrum, Ken Schwaber
Scrum and the Enterprise, Ken Schwaber
Scrum, Boris Gloger
Scrum, Roman Pichler
How Pixar Fosters Creativity, Ed Cutmill, HBR 2008
Kotter, What Leaders really do
Henry Mintzberg "The Manager's Job: Folklore and Fact"
Montag, 15. Juni 2009
110. Company in USA: Portal Company
5 Product Owners: News, Email,
Products, Security, Infrastructure
1 Scrum Development Team, 9
people
1 integrated product: Portal.
Montag, 15. Juni 2009
111. What kind of
problems do you get,
if the ScrumMaster is
part of the team?
Montag, 15. Juni 2009
112. 112
Exercise:
•What kind of impediments can you think
Impediment backlog of?
•Create a list of current impediments in
your organization
Timebox 5 min
Montag, 15. Juni 2009
114. 114
Purpose of planning?
What is planning?
What is estimation?
Why do we do planning?
Are you successful?
What is your biggest issue in planning?
Please discuss on your tables:
Timebox 10 min
Montag, 15. Juni 2009
115. 115
Planning is ...
Planning is the (psychological) process of
thinking about the activities required to create a
desired future on some scale. This thought
process is essential to the creation and
refinement of a plan, or integration of it with other
plans.
Planning is a dialogue.
Dia = through;
Logos = Word / Thinking
Montag, 15. Juni 2009
117. Finland
Denmark
USA
China
Austria
Canada
Brazil
France
UK
Germany
Italy
Country-Points
Slowakia
Montag, 15. Juni 2009
118. 118
The Product Backlog
• Emergent
• Deliverables, Stories, Functionality
Requirements
• Prioritized and Estimated
• More detailed on higher priority items
• Anyone can contribute
• Product owner is responsible for priority
• Maintained and posted visibly
• Business Plan
Montag, 15. Juni 2009