This document discusses how traditional project management approaches can fall short for complex work, and introduces Agile product development using Scrum as a framework. It explains that Scrum focuses on maximizing business value through collaborative customer engagement and empirical process improvement over comprehensive planning. Scrum is presented as a practical method for complex work where needs may change, using short development cycles called sprints to iteratively deliver working software or products.

1. Agile Product Development
How traditional project management fall short
@ScrumWay | @ScrumWayAsia
http://www.scrumway.co
http://www.scrumway.asia

2. How many of you know about Agile?

3. How many of you are Agile?

4. You need to be Agile because the
market have told you so

5. “... In the past, Man has been first. In
the future, the system must be first ...
the first object of any good system
must be that of developing first-class
men; and under systematic
management the best man rises to the
top more certainly and more rapidly
than ever before”
Frederick Taylor’s Scientific Management

6. Knowledge workers is a new breed of
employees who employ their knowledge
and brainpower, instead of their hands,
as a mean to income.
-- Peter Drucker (1960)

7. You don’t manage
knowledge workers!

8. Bureaucracy has prevented
many individuals to perform
at their best

9. Waterfall model is “risky and
invites failure” because it
leaves testing until the end
-- Dr. Winston W. Royce

10. Agile Manifesto
We are uncovering better ways of developing software by
doing it and helping others do it.
Through this work we have come to value:
• Individuals and interactions over processes and tools
• Working software over comprehensive documentation
• Customer collaboration over contract negotiation
• Responding to change over following a plan
That is, while there is value in the items on the right, we
value the items on the left more.

11. Agile is not for all type of projects

12. A project is a temporary endeavour undertaken
to create a unique a product or service

13. Agile focuses on products
not projects

14. Agile focuses on maximizing
business value

15. Fixed Scope Time Quality
Traditional Agile
Variable Quality Scope Time
Quality defines business value

16. On time and on budget is
irrelevant

17. Quality is the only relevant
measurement

18. Delighting the customer is
the ultimate goal

19. ... and this comes through
collaboration with the customer

20. Agile focuses on people
over processes

21. The Days of "Manager
Knows Best" Are Ending
-- Sujai Hajela, Vice President at Cisco
http://blogs.hbr.org/cs/2012/02/why_the_days_of_manager_knows.html

22. Agile guides, it doesn’t
manage

23. Agile coach is the servant
leader for the team

24. ... so the team can think by
themselves and reach their
maximum potential

25. Agile is not about tools (or PERT
charts, Gantt charts, etc)

26. It’s about high-bandwidth
communication and interaction

27. At first Agile doesn’t seem to
make sense

28. Insanity: doing the same thing
over and over again and
expecting different results.
-- Albert Einstein

29. It forces your brain muscle to
think differently

30. When you change the way
you look at things, the
things you look at change
-- Max Planck

31. From holistic to empirical

32. It is a mistake to look too
far ahead. Only one link in
the chain of destiny can be
handled at a time
-- Winston Churchill

33. From activity driven to
value driven

34. Analysis
1 2 3
4 5 6 Development
1 2 3
4 5 6 Testing
1 2 3
4 5 6
One activity in each phase to cover all features

35. Sprint #1 Sprint #2 Sprint #3
Analysis Analysis Analysis
1 3 5
Development Development Development
2 4 6
Testing Testing Testing
All activities in each Sprint to deliver
complete product increment

36. From command & control
to facilitate & empower

37. Never tell people how to
do things. Tell them what
to do and they will surprise
you with their ingenuity.
-- George Smith Patton Jr.

38. From hierarchies of
individuals to team

39. The modern organization
cannot be an organization of
“boss” and “subordinate”: it
must be organized as a
team of “associates”
-- Peter Drucker

41. But wait ...

42. PMBoK is a body of knowledge
Generally Accepted Project Management Knowledge and Practice

43. It never tells you how to do
Project Management

44. It tells you what happens in
Project Management

45. It never even tells you what
project life cycle to use

46. Dynamic
Systems
Crystal Clear
Development
Scrum Method
eXtreme Programming
Feature Driven
Development Adaptive

47. 85% of Agile companies
use Scrum

48. It is typical to adopt the defined
(theoritical) modeling approach when
the underlying mechanisms by which a
process operates are reasonably
understood.
When the process is too complicated
for the defined approach, the empirical
approach is the appropriate choice.
-- B.A. Ogunnaike and W.H. Ray

49. Scrum is used for complex work
in which it is impossible to
predict everything that will occur
-- Ken Schwaber

50. Complexity + Unpredictability

51. The new new product development game
-- H. Takeuchi and I. Nonaka

52. Project Management Process Groups

53. Project Management Process Groups
Initiation Planning Executing Controlling Closing
Working on Sign off,
Roadmap Release
Release release Daily testing Release
definition Planning
backlog Retrospective
Sprint Review,
Sprint Sprint Working on
Sprint Daily testing Sprint
Planning Planning features
Retrospective
Morning Daily standup Working on Peer review, Update
Daily work
coffee/tea meeting tasks Daily builds taskboard

54. Input Tools/Techniques Output
• Product increment
• ReleaseBacklog • Expertjudgment • Next release ideas
Release • Team Members • Product analysis • Point of improvements
• Sponsorship • Cost/benefit analysis
• Product increment
• Sprint
Backlog • Expertjudgment • Next Sprint ideas
Sprint • Team Members • Product analysis • Point of improvements
• Sponsorship • Cost/benefit analysis
Daily • Daily
commitments • Pair
programming • Work completed
• Impediments removal
• Impediments • Continuous Integration
work

56. Scrum will tell you the HOW

58. Scrum is only a framework

59. It can be used in any
organization

60. ... when your mindset is
ready to accept changes

62. Agile is a mindset not a skillset

63. Agile is a mindset, defined by
values, guided by principles,
expressed through practices.

64. Join the bandwagon
http://groups.google.com/group/scrum-indonesia
http://facebook.com/idscrum
@idscrum

65. SCRUM ON!