你真的搞懂了甚麼叫敏捷式開發?  David Ko
Self Introduction   III/ITRI/Trend Micro   Blog:     http://www.wretch.cc/b      log/kojenchieh   Host Scrum Community...
Agenda   Agile Introduction   How Agile Solve Problems   Agile Myths   Q&A
Agile Introduction
Common Problems   Unclear or Unstable Requirements   Too Long Tasks   Not Enough Time for Quality   No Project Visibil...
Agile Guru Gathering
Agile Is an Idea, Not a Process
Agile MethodsKanban         ScrumLean      Crystal Clear                          eXtreme       And More …                ...
Scrum
Scrum
Sprint
Extreme Programming
Kanban
Scrum v.s. XP v.s. Kanban v.s. CMMI
Why do We Need Agile?
It is not the strongest of the  species that survives, nor   the most intelligent, but      rather the one most     adapta...
How Agile Solve Problems
Unclear or Unstable Requirements   Misunderstand customer’s needs   Cannot response change quickly   Do a lot of unnece...
Review with Customers FrequentlyTesting       AnalysisCoding        Design     Iteration 1                            Test...
Adjust after Review or Change                change scope  Sprint 2                        Sprint 2  Feature 2-1          ...
Pareto Principle (80/20 Principle)   80% revenue come from 20% features
Too Long Tasks   No one knows his progress until done   The result could be unacceptable   Always handle in last minutes
Small Tasks, Quick Response
Small Test, Fast Feedback   TDD     Goal       Clean   code that works     Rules       Execution   time: 10 min
Integration Testing is not Unit Testing   What was I doing until now?        Test Program                         System ...
Parkinson’s Law   Work expands so as to    fill the time available    for its completion
Timeboxes Drive Intensity                               waterfallintensity            scrum                    time
Not Enough Time for Quality   No time to do testing   Break old features when implementing new one   No time to refine ...
Agile Is All About Feedback             Release Plan         months             Iteration Plan       weeks           Accep...
Ultimate Weapon                       Continuous     Make sure all old                       Integration    features still...
No Project Visibility   Only manager knows the progress   Cannot help each other in time   No idea about testing progress
Task Board
Daily Standup Meeting
Low Tech Testing Dashboard14-35           Low tech is high tech           Visualize your testing status      Update: 3/7...
Agile Myths
Agile Myths   No plan   No documentation   No delay   Mini-Waterfall is not Agile   Just Process only
Scrum Release Planning   Describe what features will be done in each sprint    http://www.scrum-institute.org/Release_Pla...
Scrum Sprint Planning   Describe what tasks will be done for each feature
Agile Myths   No plan   No documentation   No delay   Mini-Waterfall is not Agile   Just Process only
Communication Effectiveness    effective                                        Task board                                ...
Agile Myths   No plan   No documentation   No delay   Mini-Waterfall is not Agile   Just Process only
Agile is not Silver bullet
Agile is a Mirror
Agile Myths   No plan   No documentation   No delay   Mini-Waterfall is not Agile   Just Process only
Requirement              Design              Coding              Testing              DeploymentRequirementDesignCoding   ...
Fast Tracking is not AgileIteration 1   Coding 1          Iteration 2     Coding 2 + Fixing 1                           Te...
Deployment Testing   Coding   Design   Requirement              Deployment Testing   Coding   Design   Requirement        ...
Agile Myths   No plan   No documentation   No delay   Fast Tracking is not Agile   Just Process only
Self-organized Team
Cross Functional TeamDifferent Roles, Different Thinking, Different expertise
Multiple Skills
Agile Can Be Fun …           Classification 4/11/2012   53
It Can Hurt Too …            Classification 4/11/2012   54
LinSanity ….
Insanity
Q&A
High Moon Studios: A Portrait - Scrumhttp://www.youtube.com/watch?v=UT4giM9mxHk
你真的搞懂了甚麼叫敏捷式開發?
Upcoming SlideShare
Loading in...5
×

你真的搞懂了甚麼叫敏捷式開發?

1,705

Published on

Published in: Technology
1 Comment
28 Likes
Statistics
Notes
No Downloads
Views
Total Views
1,705
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
1
Likes
28
Embeds 0
No embeds

No notes for slide

Transcript of "你真的搞懂了甚麼叫敏捷式開發?"

  1. 1. 你真的搞懂了甚麼叫敏捷式開發? David Ko
  2. 2. Self Introduction III/ITRI/Trend Micro Blog:  http://www.wretch.cc/b log/kojenchieh Host Scrum Community in Taiwan in Facebook Scrum and XP from the Trenches - TC edition
  3. 3. Agenda Agile Introduction How Agile Solve Problems Agile Myths Q&A
  4. 4. Agile Introduction
  5. 5. Common Problems Unclear or Unstable Requirements Too Long Tasks Not Enough Time for Quality No Project Visibility Heavy Process
  6. 6. Agile Guru Gathering
  7. 7. Agile Is an Idea, Not a Process
  8. 8. Agile MethodsKanban ScrumLean Crystal Clear eXtreme And More … Programming Feature Driven Development
  9. 9. Scrum
  10. 10. Scrum
  11. 11. Sprint
  12. 12. Extreme Programming
  13. 13. Kanban
  14. 14. Scrum v.s. XP v.s. Kanban v.s. CMMI
  15. 15. Why do We Need Agile?
  16. 16. It is not the strongest of the species that survives, nor the most intelligent, but rather the one most adaptable to change Charles Darwin
  17. 17. How Agile Solve Problems
  18. 18. Unclear or Unstable Requirements Misunderstand customer’s needs Cannot response change quickly Do a lot of unnecessary features
  19. 19. Review with Customers FrequentlyTesting AnalysisCoding Design Iteration 1 Testing Analysis Coding Design
  20. 20. Adjust after Review or Change change scope Sprint 2 Sprint 2 Feature 2-1 Feature 2-3 Feature 2-2 Feature 2-4 Feature 2-3 Feature 2-5 Feature 1-1’ Refine original Feature 2-1 result Feature 2-2
  21. 21. Pareto Principle (80/20 Principle) 80% revenue come from 20% features
  22. 22. Too Long Tasks No one knows his progress until done The result could be unacceptable Always handle in last minutes
  23. 23. Small Tasks, Quick Response
  24. 24. Small Test, Fast Feedback TDD  Goal  Clean code that works  Rules  Execution time: 10 min
  25. 25. Integration Testing is not Unit Testing What was I doing until now? Test Program System under test
  26. 26. Parkinson’s Law Work expands so as to fill the time available for its completion
  27. 27. Timeboxes Drive Intensity waterfallintensity scrum time
  28. 28. Not Enough Time for Quality No time to do testing Break old features when implementing new one No time to refine old system
  29. 29. Agile Is All About Feedback Release Plan months Iteration Plan weeks Acceptance Test days Daily Scrum one day Continuous Integration hours Unit Testing hours Pair Programming minutes code seconds
  30. 30. Ultimate Weapon Continuous Make sure all old Integration features still work Refine oldDesign before implementationcoding Test Driven Refactoring Development
  31. 31. No Project Visibility Only manager knows the progress Cannot help each other in time No idea about testing progress
  32. 32. Task Board
  33. 33. Daily Standup Meeting
  34. 34. Low Tech Testing Dashboard14-35  Low tech is high tech  Visualize your testing status Update: 3/7, build 1121 Area Effort C Q Comments Add tree node High 1 #1341, #1442 Edit tree node Low 1+ Auto build broken Delete tree node Low 2 Drag tree node Start 3/14 0 Lab is ready Debug tool Blocked 1 Crash: #1121
  35. 35. Agile Myths
  36. 36. Agile Myths No plan No documentation No delay Mini-Waterfall is not Agile Just Process only
  37. 37. Scrum Release Planning Describe what features will be done in each sprint http://www.scrum-institute.org/Release_Planning.php
  38. 38. Scrum Sprint Planning Describe what tasks will be done for each feature
  39. 39. Agile Myths No plan No documentation No delay Mini-Waterfall is not Agile Just Process only
  40. 40. Communication Effectiveness effective Task board telephone (Question & Answer)Communicationeffectiveness Video recording E-mail High bandwidth Audio recording (No question-answer) Low Documentation bandwidth ineffective cold temperature of communication channel hot
  41. 41. Agile Myths No plan No documentation No delay Mini-Waterfall is not Agile Just Process only
  42. 42. Agile is not Silver bullet
  43. 43. Agile is a Mirror
  44. 44. Agile Myths No plan No documentation No delay Mini-Waterfall is not Agile Just Process only
  45. 45. Requirement Design Coding Testing DeploymentRequirementDesignCoding Agile is not Mini-WaterfallTestingDeployment
  46. 46. Fast Tracking is not AgileIteration 1 Coding 1 Iteration 2 Coding 2 + Fixing 1 Testing 1 Iteration 3 Coding 3 + Fixing 2 Testing 2 Iteration 4 Coding 4 + Fixing 3 Testing 3
  47. 47. Deployment Testing Coding Design Requirement Deployment Testing Coding Design Requirement Deployment Testing Coding Design RequirementIteration 1 Deployment Testing Coding Design Requirement Real Agile is … Deployment Testing Coding Design Requirement Deployment Testing Coding Design Requirement Deployment Testing Coding Design RequirementIteration 2 Deployment Testing Coding Design Requirement
  48. 48. Agile Myths No plan No documentation No delay Fast Tracking is not Agile Just Process only
  49. 49. Self-organized Team
  50. 50. Cross Functional TeamDifferent Roles, Different Thinking, Different expertise
  51. 51. Multiple Skills
  52. 52. Agile Can Be Fun … Classification 4/11/2012 53
  53. 53. It Can Hurt Too … Classification 4/11/2012 54
  54. 54. LinSanity ….
  55. 55. Insanity
  56. 56. Q&A
  57. 57. High Moon Studios: A Portrait - Scrumhttp://www.youtube.com/watch?v=UT4giM9mxHk

×