贊 助 廠 商AgileCommunity.tw

Joy Chen ( 陳美瑛 )Sr. Director (Corp RD – SQA/SEPG)

趨勢科技的 Agile 之旅

AgileCommunity.tw

大綱

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

AgileCommunity.tw

趨勢科技 (Trend Micro)

陳怡樺CEO and Co-

Founder

員工人數5,330

營業額USD 1.2 Billion

創立於1998 年

營運據點超過 50 個國家

公司願景打造一個交換數位資訊零風險的世界

承諾開發、提供、並支援最靈活且自訂功能最強的網際網路安全解決方案，來對付網路上千變萬化的安全威脅。

• 3 人 5,330 人• 2 個國家 39 個國家• 1 個產品 超過 100 個產品• 0 元 10 億美金

AgileCommunity.tw

世界第一、台灣發光

2

All Others77.1%

Trend Micro22.9%

Source: Worldwide Endpoint Security2010-2014 Forecast and

2009 Vendor Shares, IDC

Trend Micro

Check Point

Blue Coat

Kaspersky

SafeNet

Websense

Fortinet

Sophos

SonicWALL*

Webroot*

200 400 600 800 1000

Source: 2011 © Quocirca Ltd.: Selected independent IT

security vendor revenues ($M, * = estimate)

AgileCommunity.tw

故事的源起 : 2007 年年底

導入的作法 (1)

AgileCommunity.tw

導入的結果

• 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

導入的作法 (2) - Agile Mentality

AgileCommunity.tw

Agile Mentality

Agile Software Development

Agile ProcessAgile Method

Agile Practice

Agile ........

當應用在軟體開發上

當實現在軟體開發的生命週期上(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

AgileCommunity.tw

Agile Mentality vs. Plan Driven

Project Team

Project Req. & Objective

Project Plan

Iteration I

Target Change

Change Plan

Iteration II

Plan Driven : An artillery to hit a fixed targetAgile Mentality : A missile to hit a moving target

AgileCommunity.tw

Moving TargetMoving Target

Uncertain situationUnclear objectiveBrand new knowledgeAs early as possible needs

Uncertain situationUnclear objectiveBrand new knowledgeAs early as possible needs

Agile PrinciplesAgile Principles

Agile TeamAgile Team

New working environmentTeam(s) working model Vision for team

New working environmentTeam(s) working model Vision for team

Agile ValueAgile Value

Individuals and interactions (I&I) Working software (WS)Customer collaboration (CC)Responding to change (RtC)

Individuals and interactions (I&I) Working software (WS)Customer collaboration (CC)Responding to change (RtC)

Progress TrackingProgress Tracking

Progress trackingSchedule control

Progress trackingSchedule control

Continuous Improvement

Continuous Improvement

Continuously improve

a certain capability,

practice or skill

Continuously improve

a certain capability,

practice or skill

Five Entry Points to Use Agile Mentality

AgileCommunity.tw

從苦頭中學習

• 牛肉在哪裡 ?

• 我們不幹了 !

• 送不出去的價值 !

AgileCommunity.tw

BetaBeta

HIEHIE

開發團隊開發團隊

送不出去的價值

產品行銷團隊產品行銷團隊

Customer Customer SatisfiedSatisfied

Agile value needs all teams (PM, PDG, HIE, Beta…)’s “mesh” (change for agile adoption) to realize

AgileCommunity.tw

成功案例的分享

04/13/23

AgileCommunity.tw

• Release 的時間不可延• 有十幾個需協調和整合的團隊• 跨三區研發團隊• 開發的軟體須同步支援二十多個語言

產品家族的專案需求

AgileCommunity.tw

希望經由 Agile 導入解決的問題

Schedule DrivenSchedule Driven

Late Change & Late Change & Late IntegrationLate IntegrationLow Project VisibilityLow Project Visibility

AgileCommunity.tw

遭遇的困難

• 組織分工 , 專案需求和成員能力 與 Agile Method 的衝突– QA/Developer vs. Agile team– 跨三區研發團隊– Release 的時間不可延 (Schedule Driven)

• 與十幾個團隊間的協調和整合問題– 不同的 PDLC (Schedule, Quality Criteria)– Change vs. Dependency

AgileCommunity.tw

Release PlanIterative Development Process

Closure

Phase

Deployment Phase

Iterative Iterative Development Development PhasePhase

ReleasePlanningPhase

BusinessExploration Phase

Iterative Development Phase

Iteration 1 Iteration 2 Iteration 3 Iteration 4 …… Iteration n

R 1 R 2 R 3

55 33

222211

22……

11 22 …… nn33IterationIteration

VV

VVVV

VVVV

VV

AgileCommunity.tw

• Team A RD • Team A QA

Gap: -61.2 hrsGap: -61.2 hrs

• Team B RD • Team B QA

Gap: -3.4 hoursGap: -3.4 hoursGap: +1.4 hoursGap: +1.4 hours

Gap: -0.4 hrsGap: -0.4 hrs

Aggregated Burn Down Chart (2/2)

AgileCommunity.tw

Customized Burn Down Chart to support team in different velocity and delivery date

Code Complete Day

BC tasks

AC tasks

AgileCommunity.tw

Risk Prediction by Iterative Burn Up Chart Monitor

Iteration 4 was pointed out with the risk of huge scope growth

AgileCommunity.tw

Thank You

AgileCommunity.tw

Lean StartupUnit of Progress: Validated Learning About Customers ($$$)

Problem: unknown

Solution: unknown

Hypotheses, Experiments,Insights

Data, Feedback,Insights

Customer Development

Agile Development

Steve Blank(still alive)

04/13/23 22Confidential | Copyright 2014 Trend Micro Inc.

AgileCommunity.tw

AgileCommunity.tw

各自表訴

高階主管 : 所有的問題都解決了

產品經理 : 隨時可修改

開發人員 : 不用寫文件

專案經理 : 不需要做計畫和預測