The document discusses the importance of embracing change in organizational practices, highlighting frameworks like Kotter's 8 Steps and the McKinsey 7S model for effective transformation. It emphasizes a mindset shift towards agility and continuous improvement, advocating for the integration of agile methodologies such as Scrum and Kanban in team operations. Additionally, it underlines the necessity for a supportive change culture that encourages participation and adapts to evolving needs.

1. Unleash Innovation
1

2. Who We Are
TSID
Technology System Integration Division
技術系統整合處

3. About the Speaker
3
Derek Chen
An agile practitioner who love to promote
agile practices, and has rich experiences in
Scrum, Kanban and Large Scale Scrum
M.S. of CS, NCTU TSMC Project Manager, TSID, IT
LINE TAIWAN Technical Program Manager
Trend Micro Senior DevOps Engineer

4. Agenda
Why embracing change?
How to change?
What has really changed?
4
01
02
03

5. Why Embracing Change?
5
01

6. Operation System
6

7. What Year This Organization Chart Come From?
7
Source: https://crossing.cw.com.tw/article/13891
這張圖來自於 1910 年，稱作
〈聯合太平洋暨南太平洋系統鐵
路公司組織結構圖〉

8. Which System Allow More Cars to Pass Through?
8
Signal Controlled Intersection
https://e-info.org.tw/node/234255
Roundabout
https://www.castanet.net/news/Behind-the-Wheel/195322/Lost-in-a-
roundabout

9. Widely Used ≠ Best Practice
9
Signal controlled
intersection
(311,000 in U.S.)
Efficiency Cost Ease of use
Safety
Roundabout
(300 in U.S.)
Drivers comply but
don’t think →
frequent collisions
Drivers must pay
attention → reduces
collision by 75%
Complicated system.
Not always able to
optimize traffic flow
Delays reduced
by 89%
Expensive to
install and
maintain
Annual cost
reduced by up to
$10,000
Needs extensive
tech support
Works during
power outages
Source: Aaron Dignan. (2019). Brave New Work: Are You Ready to Reinvent Your Organization?

10. If change is necessary,
perhaps we need to change
the way how we change
10

11. If You Are City
Designer, How Do
You Build a Park?
11
Source: https://unsplash.com/photos/SBiVq9eWEtQ

12. We May Build a Park on the Railway
12
Abandoned Railway
https://www.bigfang.tw/blog/post/high-line-park-nyc
High Line Park
https://read01.com/zh-sg/mz8MG4y.html#.Y01CrOxBz0o

13. 13
Success

14. 14
Past
On Time
On Quality
+ On Budget
——————
Success
Source: 徐伯峰. (2020). 十年敏捷路，談企業轉型經驗.

15. 15
Now
On Time
On Quality
+ On Budget
——————
?
Source: 徐伯峰. (2020). 十年敏捷路，談企業轉型經驗.
A COMMON cause of disaster in software development is that
the end product is precisely what the customer originally ordered.
In a world moving at Internet speed, a customer's objectives are
constantly being revised, so programmers have to be able to hit
a moving target. Is there any formula for coping with this sort of
unpredictability?
Agility Counts Sep 20th 2001

16. 16
Source: https://www.youtube.com/watch?v=un1T5nPMaJM

17. Maximizing Value, Not Output
17
Source: https://www.in-imago.com/en/4-values-of-agility-just-described

18. How To Change?
18
02

19. 19
Complicated vs. Complex

20. Which Is Complicated? Which Is Complex?
20
Car Engine
https://unsplash.com/photos/VurHDpO4VYI
Highway Interchange
http://www.dan-
sharkey.com/N498TH/archives/2010/06/flying_the_new_york_city_sfra.html

21. Organization Is Complicated or Complex?
21
Source: https://knowledge.insead.edu/family-business/four-simple-rules-succession-planning

22. 22
Change Model

23. Kotter’s 8 Steps Change Model
23
1. Create urgency
4. Communicate the vision
2. Form a powerful coalition
3. Create vision for change
5. Empower action
6. Create quick wins
7. Build on the change
8. Make it stick
Engaging & enabling
the organization
Creating the climate
for change
Implementing &
sustaining for change
Source: https://www.cybermedian.com/fa/a-comprehensive-guide-to-kotters-8-step-model-of-change

24. McKinsey 7S Model
24
Source: https://www.edrawsoft.com/mckinsey-7s-model.html

25. Prosci Methodology
25
Source: https://www.prosci.com/resources/articles/prosci-methodology

26. Traditional Change Is an A to B Process
26
Source: https://www.allianztravelinsurance.com/travel/planning/pretrip-checklist.htm
Current
Process
Future
Process
Designed in advance

27. 27
Source: https://agilemanifesto.org

28. 28
Change Principles

29. Top-down Support,
Bottom-up Adoption
29
Source: https://unsplash.com/photos/iJ2IG8ckCpA

30. Management Support
• Provide Clear vision
• Empower the team
• Being willing to change direction
• Removing impediments
30
Source: https://lanaquera.com/estrategia-top-down-bottom-up

31. Employee Adoption
• Encourage participation and self-
organized
• Show transparency and gain trust
• Focus on continuous improvement
31
Source: https://lanaquera.com/estrategia-top-down-bottom-up

32. 32
Start Small, Think Big
Source: https://unsplash.com/photos/slk862vQQmE

33. Big Bang Approach Phased Approach
Team
Team
Team
Team
Team
SM
SM
SM
SM
SM
Team
Team
Team
Team
Team Team
Team
Team
No Agile Coach
Agile
Coach
Agile Coach supports and
grows Scrum Masters

34. 34
Pause Before Starting
Source: https://unsplash.com/photos/YxywelymVuE

35. Eliminate Ad-Hoc Meetings
• Establish meeting cadence for
your team
• A meeting should have a clear
purpose and agenda
• Daily standup helps avoid
other unnecessary meetings
35
Source: https://medium.com/@jojofree/three-great-reasons-to-hold-stand-up-meetings-in-the-office-2d9e9f7bbf6b

36. Ease the Burden on Your Front-Line Managers
36
Traditional manager takes on too much responsibility
• Product management, project management, technical decision, people management,
meeting facilitator and etc.
You may need to have new roles that focuses on different
aspects
• PO: Build the right thing
• Developer: Build the thing right
• SM: Build it fast
Source: https://innolution.com/essential-scrum/table-of-contents/chapter-2-scrum-framework

37. 37
Understanding
Resistance to Change
Source: https://unsplash.com/photos/WzfqobnrSVc

38. Satir Change Process
38
Source: https://www.ciopages.com/change-management-models/satir-change-model

39. Resistances to Agile Adoption
• Team has too many agile meetings
• It’s too transparent that everyone’s work can be seen on
task board
• People like to discuss deadline over priority
• We don’t know how to run Retrospectives

40. People can change, only
when it is meaningful to them
40

41. What Has Really Changed?
41
03

42. Apply Product Thinking
42
Source: https://www.linkedin.com/pulse/design-thinking-lean-startup-agile-pradeep-patel

43. Build DevOps Team
43
Source: https://www.yun88.com/news/659.html

44. Some Teams Use Scrum
44
Source: https://innolution.com/essential-scrum/table-of-contents/chapter-2-scrum-framework

45. Some Teams Use Kanban
45

46. Adopt Azure DevOps
Azure DevOps provides developer services for allowing teams to plan work,
collaborate on code development, and build and deploy applications
46
Source: https://www.telerik.com/blogs/microsoft-azure-devops-what-you-need-to-know

47. Closure
47

48. Summary
• Due to the definition of success is changed, we must change
mindset and embrace changes
• Make adjustments at any time according to change principles,
instead of following prescribed plan
• Apply product thinking, build DevOps team, use Scrum and Kanban,
adopt Azure DevOps
48

49. 49
Aaron Dignan. (2019). Brave New
Work: Are You Ready to Reinvent
Your Organization?

51. Q & A
51