Agile tour of Trend Micro, keynote speech slides of agile tour taipei 2014.

1. 趨勢科技的Agile之旅
Joy Chen (陳美瑛)
Sr. Director (Corp RD – SQA/SEPG)
AgileCommunity.tw 贊 助 廠 商

2. 大綱
• 故事的源起 - 如何開始的?
• 導入的作法與結果
• 從苦頭中學習 – 失敗的故事
• 成功案例的分享
• Q & A
AgileCommunity.tw

3. 趨勢科技 (Trend Micro)
陳怡樺
CEO and Co-Founder
AgileCommunity.tw
員工人數
5,330
營業額
USD 1.2
Billion
創立於
1998 年
營運據點
超過50 個國
家
公司願景
打造一個交換數位資
訊零風險的世界
承諾
開發、提供、並支援
最靈活且自訂功能最
強的網際網路安全解
決方案，來對付網路
上千變萬化的安全威
脅。
• 3 人 5,330 人
• 2 個國家 39 個國家
• 1 個產品 超過100 個產品
• 0 元 10 億美金

4. 世界第一、台灣發光
AgileCommunity.tw
2
All
Others
77.1%
Trend
Micro
22.9%
Source: Worldwide Endpoint Security
2010-2014 Forecast and
2009 Vendor Shares, IDC
Trend Micro
Check Point
Blue Coat
Kaspersky
SafeNet
Websense
Fortinet
Sophos
SonicWALL*
Webroot*
Source: 2011 © Quocirca Ltd.:
Selected independent IT
security vendor revenues ($M,
* = estimate)
200 400 600 800 1000

5. 故事的源起 : 2007年年底
AgileCommunity.tw
導入的作法 (1)

6. 導入的結果
• 2008年10個專案, 2009年增至49個, 其中7 個專案
是續用
• 這幾年維持40% ~ 60% Adoption Rate, 2013 是55%
• 兩個標準: Scrum like 和 IDP (Iterative Development
Process)
PS: (1) 2010年初調查結果
(2) Industry Data Source
– 3rd Annual Survey: 2008
“The State of Agile
Development”,
– 2,319 respondents from
80 countries
AgileCommunity.tw

7. 導入的作法 (2) - Agile Mentality
AgileCommunity.tw

8. Agile ........
AgileCommunity.tw
Agile Mentality
Agile Software
Development
Agile Process
Agile Method
Agile Practice
當應用在軟體
開發上
當實現在軟體
開發的生
命週期上
(PDLC)
一種能快速, 有效地適應和
應對改變的思惟,心態或者說
能力
以 Agile Manifesto (4 values + 12
principles) 為基礎的軟體開發方法
Method / process that support the agile
philosophy (4 value + 12 principles)
e.g. Scrum, eXtreme Programming
Practice derived from agile principles
e.g. Stand-up meetings, Sprint
Pair Programming

9. Agile Mentality vs. Plan Driven
Plan Driven : An artillery to hit a fixed target
Agile Mentality : A missile to hit a moving target
AgileCommunity.tw
Project Team
Project Req.
& Objective
Project
Plan
Iteration I
Target
Change
Change
Plan
Iteration II

10. Five Entry Points to Use Agile Mentality
MMoovviningg T Taarrggeett
Uncertain situation
Unclear objective
Brand new knowledge
As early as possible needs
Uncertain situation
Unclear objective
Brand new knowledge
As early as possible needs
Continuous
Improvement
Continuously improve
a certain capability,
practice or skill
AgileCommunity.tw
Individuals and interactions (I&I)
Working software (WS)
Customer collaboration (CC)
Responding to change (RtC)
AAggiliele P Prrininccipipleless
AAggiliele T Teeaamm
New working environment
Team(s) working model
Vision for team
New working environment
Team(s) working model
Vision for team
AAggiliele V Vaaluluee
Individuals and interactions (I&I)
Working software (WS)
Customer collaboration (CC)
Responding to change (RtC)
PPrrooggrreessss T Trraacckkiningg
Progress tracking
Schedule control
Progress tracking
Schedule control
Continuous
Improvement
Continuously improve
a certain capability,
practice or skill

11. 從苦頭中學習
• 牛肉在哪裡?
• 我們不幹了!
• 送不出去的價值!
AgileCommunity.tw

12. 送不出去的價值
Beta
HIE
AgileCommunity.tw
開發
團隊
產品行
銷團隊
CCuussttoommeerr
SSaattiissffiieedd
Agile value needs all teams (PM,
PDG, HIE, Beta…)’s “mesh” (change
for agile adoption) to realize

13. 成功案例的分享
AgileCommunity.tw
11/10/14

14. 產品家族的專案需求
• Release 的時間不可延
• 有十幾個需協調和整合的團隊
• 跨三區研發團隊
• 開發的軟體須同步支援二十多個語言
AgileCommunity.tw

15. 希望經由Agile導入解決的問題
SScchheedduullee DDrriivveenn
AgileCommunity.tw
LLaattee CChhaannggee &&
LLooww PPrroojjeecctt VViissiibbiilliittyy LLaattee IInntteeggrraattiioonn

16. 遭遇的困難
• 組織分工, 專案需求和成員能力 與Agile
Method的衝突
– QA/Developer vs. Agile team
– 跨三區研發團隊
– Release 的時間不可延 (Schedule Driven)
• 與十幾個團隊間的協調和整合問題
– 不同的PDLC (Schedule, Quality Criteria)
– Change vs. Dependency
AgileCommunity.tw

17. Release Plan
Iterative Development Process
IItteerraattiioonn 11 22 33 …… nn
11
22
AgileCommunity.tw
Closure
Phase
Deployment
Phase
IItteerraattiivvee
DDeevveellooppmmeenntt
PPhhaassee
Release
Planning
Phase
Business
Exploration
Phase
Iterative Development Phase
Iteration 1 Iteration 2 Iteration 3 Iteration 4 …… Iteration n
R 1 R 2 R 3
55
33
22
22…
…
VV
VVVV
VV
VV
VV

18. Aggregated Burn Down Chart (2/2)
• Team A RD • Team A QA
AgileCommunity.tw
GGaapp: :- 3-3.4.4 h hoouursrs GGaapp: :+ +11.4.4 h hoouursrs
GGaapp: :- 6-611.2.2 h hrsrs
• Team B RD • Team B QA
GGaapp: :- 0-0.4.4 h hrsrs

19. Customized Burn Down Chart to support
team in different velocity and delivery date
AgileCommunity.tw
Code Complete Day
BC
tasks
AC tasks

20. Risk Prediction by Iterative Burn Up Chart
Monitor
AgileCommunity.tw
Iteration 4 was
pointed out with
the risk of
huge scope
growth

21. AgileCommunity.tw
Thank You

22. Lean Startup
Unit of Progress: Validated Learning About Customers ($$$)
Problem: unknown
Solution: unknown
AgileCommunity.tw
Customer Development
Hypotheses, Experiments,
Insights
Data, Feedback,
Insights
Agile Development
Steve Blank
(still alive)
11/10/14 Confidential | Copyright 2014 Trend Micro Inc. 22

23. AgileCommunity.tw

24. 各自表訴
高階主管: 所有的問題都解決
了
AgileCommunity.tw
產品經理: 隨時可修改
開發人員: 不用寫文件
專案經理: 不需要做計畫和預測