當導入敏捷一陣子後, 能否感受到敏捷為團隊帶來了什麼甜頭? 還是路途上總跌跌撞撞、滿身是傷? 敏捷是什麼? 敏捷不是什麼? 能做到什麼? 不能做到什麼? 該怎麼適時調整得到恰當的好處? 保健室座談會, 邀請大家聊聊(療療)敏捷導入過程中的甘苦辛酸, 並分享只要有心, 人人都可以是敏捷小護士。

1. 敏捷保健室與
敏捷小護士
William Tai @ Agile Tour Hsinchu
2015.11.28

2. Definition (1)
敏捷小護士
1. 組織裡對敏捷開發有興趣的人 (學習參與者)
2. 組織裡談到敏捷開發就會想到的那個人(隱性專家)
3. 組織裡明確指派得落實敏捷開發的那個人(推動工作)
4. 組織裡負擔敏捷開發成本且主要獲得益處的那個人 (Stakeholder)

3. Definition (2)
敏捷保健室
1. 組織裡對敏捷開發提供協助或規範治理方式的單位
2. 組織裡對軟體開發的諮詢單位
3. others?

4. 敏捷小護士的處境
1. 如何評估採用敏捷開發方式的好處, 如何開始敏捷轉型
2. 當一些團隊成員都已上過ScrumMaster課程, 但是大家回來使用
就是卡卡的, 該如何覺察現況病徵, 並調整成適當有用的做法?
3. 當一個Sprint走完, 每次Retrospective都問一些 Happy,
Unhappy, 但如何才能做有效的回顧與改善?
如果公司內有第三方單位, 能義務地協助您們, 有任何問
題可以問, 還可以請他們幫忙, 是不是一件很棒的事情?

5. 保健室 vs. 小護士
http://www.tbs.co.jp/masshiro2015/intro/comment.html http://image.shutterstock.com/z/stock-photo-wheaton-illinois-usa-september-two-
young-women-nurses-attend-to-a-fallen-soldier-while-315897617.jpg

6. About Me
Current
Trend Micro - PLS - Partner Integration Team
Previous
Trend Micro – PDG - SSEPG/SQA Team
(Software & Service Engineering Process Group/Software Quality Assurance)
Interest:
Lean Startup/Agile Transition/Continuous Delivery
Scaled Agile Framework (SAFe) Program Consultant
Email:
william@agilehacker.cc

7. The Steps of Process Improvement Team to Help
1. Build BELIEF
2. Find candidates (*)
3. Questionnaire design
4. Interview with team
representatives and get feedback
5. Define engagement points
6. Define team’s goal (short-term
and mid-term)
7. Define collaboration’s objective
8. Training before start
9. Observation and ask questions
10. Clarification
11. Host ceremony
12. Lesson-learned and improvement
Running Lean

8. Engagement
[Before Sprint]
◦ Identify Key Improvement Area
◦ Release Planning
[At Sprint Start]
◦ Planning Poker
◦ Plan Assessment
◦ Task-breakdown
◦ DoD
[In Sprint]
◦ Sync-up and Burndown chart
◦ Risk Assessment
• Schedule
• Quality
[At Sprint End]
1. Retrospective
2. Postmortem

9. Difficulties in Such Cooperation
1. Organization culture (Not mandatory as Top-down)
2. Hard to align to each team within a large product family
3. Hard to run agile together
4. Hard to clone the successful practices

10. http://www.scaledagileframework.com/

11. My Journey to Become 敏捷小護士

12. What's in a name? That which
we call a rose by any other
name would smell as sweet.
~ William Shakespeare

14. 1. Visibility
http://www.seomastering.com/seo-articales/ways-to-improve-your-visibility.php

15. 2. Taking Ownership
http://ryanjferrier.com/take-ownership/

16. 3. Collaborative Predictability
http://pic.chinadaily.com.cn/2015-07/17/content_21312222.htm

17. 4. Improving Quantitatively
http://www.sportscience.com.tw/article/79

18. Mindset
 1個目的
 2個態度
 3種角度
 5個階段
 8個步驟

19. 1個目的
創造團隊的商業價值
(*) http://www.books.com.tw/products/0010673295

20. 2個態度
Inspect and Adapt

21. 3種角度
Agile Coaching Competency Framework
http://www.agilecoachinginstitute.com/wp-content/uploads/2015/11/Developing-an-Internal-Agile-Coaching-Capability.pdf

22. Guide to Agile Practices
http://guide.agilealliance.org/subway.html

23. 5個階段
Agile Fluency
(*) http://martinfowler.com/articles/agileFluency.html

24. 8個步驟
8 Steps Process for Leading Change
(*) http://raconteur.net/business/8-steps-for-successful-change-management
An outcome of 30 years of
research, by Dr. John Kotter

25. Agile Development in Trend Micro
(*) http://www.ithome.com.tw/node/81246

26. 藏在趨勢科技的深厚內功
(*) http://www.mingsheng.com/tw/Start_Up/trendmicro-startup

27. Recap

28. Thank you