Due Date - The Root of All Evils
( How to Fail with Agile part II )
Kamon Treetampinij
@Korn4d

What is due date?
• Due date is the dead line put down to
the team by the upper management
• It is set by starting with ask for an
estimation then negotiate until get a
reasonable number (lowest)

There are 4 parameters in
Software development
• Scope (size)
• Time (due)
• Resources (man power)
• Quality (number of bugs)

There are 4 parameters in
Software development (2)
• Scope (size)
• Time (due)
• Resources (man power)
• Quality (number of bugs)

The Downfall of Agile Hitler
http://www.youtube.com/watch?v=l1wKO3rID9g

What happened to the project?
• Carryover stories
• Customer requirement is too complex
• Automated unit testing is harder than
expected

What happened to the tests?
• It has been removed since Iteration #3
(Why?)
• Because it they were failing

What’s wrong about asking only
senior dev to stay?
• It shows unevenness in the team. Some
people are more important and get more
tasks than the others

Why Hitler never know about
this in stand-up meeting?
• It shows stand-up meeting for them is just
a daily status report. Everyone afraid tell
the unpleasant news to the leader

What's the meaning of \"We tried
to keep up, but the pace was too
fast\"?
• The due date already put down to the
team and they now suffer with it

Meaning of \"It's not our fault.
Customer is making too many
changes”?
• The due date again, prepare for the
downfall

How about \"It's OK, we are
doing good at QA testing”?
• The QA is not part of the team. The
feedback never get to the dev in time.

Does Hitler still believe in Agile?
• Yes of course.
•How about you?

How can we get rid of the due
date?
• No, I’m not gonna answer this.
• Let’s discuss!