• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
你真的搞懂了甚麼叫敏捷式開發?
 

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

on

  • 1,253 views

 

Statistics

Views

Total Views
1,253
Views on SlideShare
1,253
Embed Views
0

Actions

Likes
19
Downloads
0
Comments
1

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel

11 of 1 previous next

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

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

    • 你真的搞懂了甚麼叫敏捷式開發? David Ko
    • 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
    • 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 Visibility Heavy Process
    • Agile Guru Gathering
    • Agile Is an Idea, Not a Process
    • Agile MethodsKanban ScrumLean Crystal Clear eXtreme And More … Programming Feature Driven Development
    • 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 adaptable to change Charles Darwin
    • How Agile Solve Problems
    • Unclear or Unstable Requirements Misunderstand customer’s needs Cannot response change quickly Do a lot of unnecessary features
    • Review with Customers FrequentlyTesting AnalysisCoding Design Iteration 1 Testing Analysis Coding Design
    • 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
    • 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 under test
    • 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 old system
    • 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
    • Ultimate Weapon Continuous Make sure all old Integration features still work Refine oldDesign before implementationcoding Test Driven Refactoring Development
    • 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, 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
    • 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_Planning.php
    • 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 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
    • 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 Agile is not Mini-WaterfallTestingDeployment
    • 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
    • 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
    • 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