Agile product development

778
-1

Published on

Agile Product Development: How traditional project management fall short. This presentation was presented at PMI chapter Indonesia meeting.

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
778
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
129
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Tell about history of Scrum in Indonesia\nThank PMI Indonesia\n
  • \n
  • \n
  • \n
  • Traditional project management does not enable employees to self-actualize\n
  • \n
  • \n
  • Employees don’t leave companies because of the organization but because of their managers.\n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • Activity definition\nActivity sequencing\nActivity duration estimating\n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • Scrum provides the framework\n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • Agile product development

    1. 1. Agile Product DevelopmentHow traditional project management fall short@ScrumWay | @ScrumWayAsiahttp://www.scrumway.cohttp://www.scrumway.asia
    2. 2. How many of you know about Agile?
    3. 3. How many of you are Agile?
    4. 4. You need to be Agile because the market have told you so
    5. 5. “... In the past, Man has been first. Inthe future, the system must be first ...the first object of any good systemmust be that of developing first-classmen; and under systematicmanagement the best man rises to thetop more certainly and more rapidlythan ever before”Frederick Taylor’s Scientific Management
    6. 6. Knowledge workers is a new breed ofemployees who employ their knowledge and brainpower, instead of their hands, as a mean to income. -- Peter Drucker (1960)
    7. 7. You don’t manageknowledge workers!
    8. 8. Bureaucracy has preventedmany individuals to perform at their best
    9. 9. Waterfall model is “risky and invites failure” because it leaves testing until the end -- Dr. Winston W. Royce
    10. 10. Agile ManifestoWe are uncovering better ways of developing software bydoing 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 planThat is, while there is value in the items on the right, wevalue the items on the left more.
    11. 11. Agile is not for all type of projects
    12. 12. A project is a temporary endeavour undertaken to create a unique a product or service
    13. 13. Agile focuses on products not projects
    14. 14. Agile focuses on maximizing business value
    15. 15. Fixed Scope Time Quality Traditional AgileVariable Quality Scope Time Quality defines business value
    16. 16. On time and on budget is irrelevant
    17. 17. Quality is the only relevant measurement
    18. 18. Delighting the customer is the ultimate goal
    19. 19. ... and this comes throughcollaboration with the customer
    20. 20. Agile focuses on people over processes
    21. 21. The Days of "ManagerKnows Best" Are Ending -- Sujai Hajela, Vice President at Cisco http://blogs.hbr.org/cs/2012/02/why_the_days_of_manager_knows.html
    22. 22. Agile guides, it doesn’t manage
    23. 23. Agile coach is the servant leader for the team
    24. 24. ... so the team can think bythemselves and reach their maximum potential
    25. 25. Agile is not about tools (or PERT charts, Gantt charts, etc)
    26. 26. It’s about high-bandwidthcommunication and interaction
    27. 27. At first Agile doesn’t seem to make sense
    28. 28. Insanity: doing the same thing over and over again and expecting different results. -- Albert Einstein
    29. 29. It forces your brain muscle to think differently
    30. 30. When you change the way you look at things, thethings you look at change -- Max Planck
    31. 31. From holistic to empirical
    32. 32. It is a mistake to look too far ahead. Only one link inthe chain of destiny can be handled at a time -- Winston Churchill
    33. 33. From activity driven to value driven
    34. 34. Analysis1 2 34 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. 35. Sprint #1 Sprint #2 Sprint #3 Analysis Analysis Analysis 1 3 5Development Development Development 2 4 6 Testing Testing Testing All activities in each Sprint to deliver complete product increment
    36. 36. From command & control to facilitate & empower
    37. 37. Never tell people how to do things. Tell them whatto do and they will surprise you with their ingenuity. -- George Smith Patton Jr.
    38. 38. From hierarchies ofindividuals to team
    39. 39. The modern organizationcannot be an organization of “boss” and “subordinate”: it must be organized as a team of “associates” -- Peter Drucker
    40. 40. But wait ...
    41. 41. PMBoK is a body of knowledgeGenerally Accepted Project Management Knowledge and Practice
    42. 42. It never tells you how to do Project Management
    43. 43. It tells you what happens in Project Management
    44. 44. It never even tells you what project life cycle to use
    45. 45. Dynamic Systems Crystal Clear Development Scrum Method eXtreme ProgrammingFeature DrivenDevelopment Adaptive
    46. 46. 85% of Agile companies use Scrum
    47. 47. It is typical to adopt the defined (theoritical) modeling approach whenthe underlying mechanisms by which a process operates are reasonably understood. When the process is too complicatedfor the defined approach, the empirical approach is the appropriate choice. -- B.A. Ogunnaike and W.H. Ray
    48. 48. Scrum is used for complex work in which it is impossible topredict everything that will occur -- Ken Schwaber
    49. 49. Complexity + Unpredictability
    50. 50. The new new product development game -- H. Takeuchi and I. Nonaka
    51. 51. Project Management Process Groups
    52. 52. 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, UpdateDaily work coffee/tea meeting tasks Daily builds taskboard
    53. 53. Input Tools/Techniques Output • Product increment • ReleaseBacklog • Expertjudgment • Next release ideasRelease • Team Members • Product analysis • Point of improvements • Sponsorship • Cost/benefit analysis • Product increment • Sprint Backlog • Expertjudgment • Next Sprint ideasSprint • Team Members • Product analysis • Point of improvements • Sponsorship • Cost/benefit analysis Daily • Daily commitments • Pair programming • Work completed • Impediments removal • Impediments • Continuous Integration work
    54. 54. Scrum will tell you the HOW
    55. 55. Scrum is only a framework
    56. 56. It can be used in any organization
    57. 57. ... when your mindset isready to accept changes
    58. 58. Agile is a mindset not a skillset
    59. 59. Agile is a mindset, defined byvalues, guided by principles,expressed through practices.
    60. 60. Join the bandwagonhttp://groups.google.com/group/scrum-indonesiahttp://facebook.com/idscrum@idscrum
    61. 61. SCRUM ON!

    ×