This document provides an overview of three common software development models: Waterfall, Scrum, and Kanban. It defines the essence of each model, including that Waterfall involves long-term planning while Agile focuses on early feedback and minimal planning. Key aspects of each model are outlined, such as phases for Waterfall and roles for Scrum. A comparison table shows differences between the models in terms of task cycle time, feedback lead time, roles involved, and delivery risk. The document recommends Scrum as a personally preferred model.

1. Easy to Know
Software Development Models
Jordan Chung
2015

2. Agenda
• Essence (精髓)
• Models
• Differences 差異

3. Essence 精髓
• Water Fall : Stable
• Agile :
– Break the tasks into small increments with
minimal planning and do not directly involve long-
term planning.
– Get feedback as early as we can
白話文意思 : 早期發現  早期治療

4. Models
• Water Fall Model
• Scrum Model
• KanBan Model

5. Water Fall Model
Marketing
•Marketing Research
•Produce MKT Requests Doc
Customer
•Defines Requirements
Design
Product
Spec.
Implementation
Test PlanTest Strategy
Test Cycle
SQA
ENG
Quality
Criteria
Met
Defect
Resolution
Test Cycle Definition
• Alpha/Beta/FCS (GM)
•Entry/Exit Criteria
•Methods use
Needs
• Tools
•Hardware
•Software
Product Definition
• Select and staff product team
- Program Mgr
- Engineering Resources
- SQA Resources
- UI Resources
- Tech. Pubs Resources
•Develop schedule
•Design Revise
Customer Feedback
•Early access
•Beta Seed Program
Assess Feasibility
SHIP
Yes
No

6. Scrum Model
最精華的部分

7. KanBan Model
Development
限制 Work In Progress
For example, 2 days
Product Backlog Analysis
精神就是每次開發時間不要太長
Continuous Implement/Improvement
Done (Release)
Bug (continues improvement)
Visualize flow

8. 主要差異
• Task Cycle time
• Feedback Lead time
• Roles
• Flow Complexity
• Organization
• Delivery Risk

9. Comparisons Table
項目 Water fall Scrum KanBan
Task Cycle time 最長 中等 最短
Feedback Lead Time 最長 中等 最短
Roles 多 多 少
Flow Complexity 複雜 中等 簡單
Org. NA 中等組織
(至少有 PM, SM, RD …)
DevOps
(混合)
Delivery Risk 高 低 高
(如果分析做得不好)
PS: Personally prefer - Scrum

10. email: Jordan_Chung@hotmail.com