27. “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 Projectsquot; by Charles Lecht. 1967
37. 37
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.”
41. 41
Process Types
It is typical to adopt the defined (theoretical) modeling
approach when the underlying mechanisms by which
a process operates are reasonably well understood.
When the process is too complicated for the defined
approach, the empirical approach is the appropriate
choice.”
Process Dynamics, Modeling, and Control,
Ogunnaike and Ray, Oxford University Press, 1992
46. 44
Estimation Meeting
Preparation of Sprint Planning
Formal estimation
Spend at least two meetings
per Sprint
Estimate only Size not Time
=> Input for Release Planing
56. 46
Daily Scrum Meetings
• Daily 15 minute meeting
• Same place and time every day
• Meeting room
57. 46
Daily Scrum Meetings
• Daily 15 minute meeting
• Same place and time every day
• Meeting room
• Chickens and pigs
58. 46
Daily Scrum Meetings
• Daily 15 minute meeting
• Same place and time every day
• Meeting room
• Chickens and pigs
• Three questions
59. 46
Daily Scrum Meetings
• Daily 15 minute meeting
• Same place and time every day
• Meeting room
• Chickens and pigs
• Three questions
• What have you ACHIEVED since last meeting?
60. 46
Daily Scrum Meetings
• Daily 15 minute meeting
• Same place and time every day
• Meeting room
• Chickens and pigs
• Three questions
• What have you ACHIEVED since last meeting?
• What will you ACHIEVE before next meeting?
61. 46
Daily Scrum Meetings
• Daily 15 minute meeting
• Same place and time every day
• Meeting room
• Chickens and pigs
• Three questions
• What have you ACHIEVED since last meeting?
• What will you ACHIEVE before next meeting?
• What is in your way?
62. 46
Daily Scrum Meetings
• Daily 15 minute meeting
• Same place and time every day
• Meeting room
• Chickens and pigs
• Three questions
• What have you ACHIEVED since last meeting?
• What will you ACHIEVE before next meeting?
• What is in your way?
• Impediments and
63. 46
Daily Scrum Meetings
• Daily 15 minute meeting
• Same place and time every day
• Meeting room
• Chickens and pigs
• Three questions
• What have you ACHIEVED since last meeting?
• What will you ACHIEVE before next meeting?
• What is in your way?
• Impediments and
• Decisions
64. 46
Daily Scrum Meetings
• Daily 15 minute meeting
• Same place and time every day
• Meeting room
• Chickens and pigs
• Three questions
• What have you ACHIEVED since last meeting?
• What will you ACHIEVE before next meeting?
• What is in your way?
• Impediments and
• Decisions
68. 47
Sprint Review
When a Team member says “done,” what does that mean?
Done!
69. 47
Sprint Review
When a Team member says “done,” what does that mean?
Done! Code adheres to standards, is clean, has been re-factored, has been
unit tested, has been checked in, has been built, and has had a
suite of unit tests applied to it
70. 47
Sprint Review
When a Team member says “done,” what does that mean?
Done! Code adheres to standards, is clean, has been re-factored, has been
unit tested, has been checked in, has been built, and has had a
suite of unit tests applied to it
Development environment for this to happen requires source code
library, coding standards, automated build facility, and unit test
harness
71. 47
Sprint Review
When a Team member says “done,” what does that mean?
Done! Code adheres to standards, is clean, has been re-factored, has been
unit tested, has been checked in, has been built, and has had a
suite of unit tests applied to it
Development environment for this to happen requires source code
library, coding standards, automated build facility, and unit test
harness
72. 47
Sprint Review
When a Team member says “done,” what does that mean?
Done! Code adheres to standards, is clean, has been re-factored, has been
unit tested, has been checked in, has been built, and has had a
suite of unit tests applied to it
Development environment for this to happen requires source code
library, coding standards, automated build facility, and unit test
harness
76. 51
Running
30 days
Team builds functionality that includes
product backlog and meets Sprint goal
Team self-organizes to do work
Team conforms to existing standards and
conventions
Tracks progress
82. In 1967 I submitted a paper called quot;How Do Committees
Invent?quot; to the Harvard Business Review. HBR rejected it on the
grounds that I had not proved my thesis. I then submitted it to
Datamation, the major IT magazine at that time, which
published it April 1968.
Here is one form of the paper's thesis:
Conways Law Any organization that designs a
system (de ned broadly) will
produce a design whose structure is a
copy of the organization's
communication structure.
83. 58
Marketing Sales Kunde Dev. IT Kunde Kunde Kunde
P P P P P P
P
P P P
P
P P Product Owner
P
P
P P P P
Team Team Team Team Team
P
Team Team Team Team
P P P