介紹敏捷精神以及實踐方法，附有實作範例

1. 敏捷開發心法
BRYAN YANG 2018

2. SOFTWARE DEVELOPMENT ISSUES
https://www.farreachinc.com/blog/far-reach/2017/03/23/scrum-posters-(free-downloads!)

3. BASIC WORKFLOW OF DEVELOPMENT
https://admhelp.microfocus.com/octane/en/latest/Online/Content/Flows/flow_SW_Development.htm

4. IN THE PAST...

5. https://interviewsteps.com/blogs/news/the-ultimate-list-of-141-project-manager-interview-questions

6. https://www.slideshare.net/IosifItkin/extent2017-independent-qa-in-agile

7. http://inmyownterms.com/3-things-you-need-to-be-a-good-terminology-project-manager/

8. http://www.nationalleasing.com/en/blog/entry/how-agile-development-can-help-your-business

10. WHAT IS AGILE?

11. 偉大的原則總是能產生行
動力，缺乏指導原則的實
踐反而經常被誤用．
Jim Highsmith
TEXT

12. MINDSET FIRST
https://www.linkedin.com/pulse/one-year-agile-teams-afrogleap-arthur-von-kriegenbergh/

14. https://www.farreachinc.com/blog/far-reach/2017/03/23/scrum-posters-(free-downloads!)

15. W

16. 敏捷原則
https://medium.com/文思不藏私/文思不藏私-敏捷宣言-12-原則-64ad7d592087

17. 敏捷原則
https://medium.com/文思不藏私/文思不藏私-敏捷宣言-12-原則-64ad7d592087

18. METHODOLOGIES
https://www.slideshare.net/AgileSparks/henrik-kniberg-essence-of-agile

19. https://www.agileconnection.com/article/marriage-lean-scrum-and-extreme-programming-xp

20. https://www.agileconnection.com/article/marriage-lean-scrum-and-extreme-programming-xp

21. HOW TO BE
AGILE?

23. EVERYONE IS A PIG
https://www.safaribooksonline.com/library/view/learning-agile/9781449363819/ch04.html

26. 1. SET CLEAR GOALS
2. PROVIDE IMMEDIATE
FEEDBACK
3. MAXIMIZE EFFICIENCY
4. ALLOW FOR
DISCOVERY
Jim Ramsey
TEXT

27. GET INTO FLOW
http://www.pamelarutledge.com/2012/08/29/the-positive-side-of-video-games-part-iii/?print=print

28. FEEDBACK LOOP
https://www.mindtools.com/pages/article/build-measure-learn.htm

29. RAPID ITERATION
https://community.dynamics.com/crm/b/microsoftdynamicscrmsolutions/archive/2015/12/02/agile-project-implemen

30. SCRUM FRAMEWORK
https://leankit.com/learn/agile/agile-development/

31. STOCHASTIC GRADIENT DESCENT
https://www.cegeka.com/en/solution-pages/agile-development

32. http://logicboost.com/whyagile.html

34. https://apiumtech.com/blog/agile-project-management-benefits/

35. DOCUMENTS
http://agilemodeling.com/essays/documentContinuously.htm

37. BUILD A SCRUM
TEAM

38. 在文化中適應了可預測性的人，會相信他們可
以預測未來，他們的工作就變成了藉著用暴力
法強迫人們跟資源讓那個未來發生。
而 SCRUM 的人相信當遇到複雜的、有創意的
工作，像是軟體開發，可預測性是不可能的。
Ken Schwaber
TEXT

39. SCRUM FRAMEWORK
http://www.crmsearch.com/agile-toolchain.php

40. SCRUM VALUES

41. http://www.xceleratepartners.com/blog/2013/10/1/agile-teams-self-organize-for-project-success

42. ROLES ON AGILE
http://nmp90.com/2017/06/essential-scrum-roles-product-owner-scrummaster-development-team-manager-5/

44. ROLES IN A SCRUM TEAM
https://www.scrum.org/resources/blog/how-do-3-scrum-roles-promote-self-organization

45. PRODUCT OWNER

46. The Product Owner is responsible for
maximizing the value of the product
and the work of the development
team.
Scrum Guide
TEXT

47. PRODUCT OWNER
https://dzone.com/articles/every-great-product-owner

49. http://www.romanpichler.com/blog/the-product-owner-responsibilities/

50. ALTERNATIVES 1
https://www.linkedin.com/pulse/scrum-weakness-product-owner-role-donald-ewart/

51. ALTERNATIVES 2

52. ALTERNATIVES 3

53. https://www.slideshare.net/NadavBenedek/product-management-scrum

54. https://www.slideshare.net/NadavBenedek/product-management-scrum

55. SCRUM
MASTER

57. SCRUM MASTER
https://dzone.com/articles/every-great-product-owner

58. https://www.scrumalliance.org/community/articles/2014/may/what-it-is-that-a-scrum-master-does-all-day-long

59. https://less.works/less/structure/scrummaster.html

60. https://www.infoq.com/news/2012/10/pm-scrum-master

62. TEAM MEMBERS
https://www.forbes.com/sites/stevedenning/2016/09/08/explaining-agile/#7480e4f9301b

63. https://www.netsolutions.com/insights/the-role-of-business-analysts-in-distributed-agile-projects/

64. TEAM STRUCTURES
https://www.targetprocess.com/articles/agile-software-development-process-90-months-of-evolution/

65. TYPES OF TEAMS
https://less.works/less/management/self-managing-teams.html

66. AGILE TO DEVOPS
https://bitbar.com/deep-dive-on-devops-in-mobile-app-testing/

68. AGILE TO CONTINUOUS DELIVER
https://www.slideshare.net/QASymphony/where-testers-qa-fit-in-the-story-of-devops

69. LET'S SCRUM

71. https://www.pinterest.com/pin/156218680808489058/

73. https://www.linkedin.com/pulse/all-scrum-swapnika-g/

74. https://www.slideshare.net/dj1arry/week-8-presentation-slide

75. https://www.slideshare.net/dj1arry/week-8-presentation-slide

76. https://andybacon.com/2016/08/25/sprint-schedule-template/

77. https://masterofproject.com/blog/135498/scrum-events

78. http://one80services.com/effective-meetings/scrum-events-the-too-many-meeting-problem/

79. http://one80services.com/effective-meetings/scrum-events-the-too-many-meeting-problem/

80. CASE STUDY
▸小明想和他家人在暑假前去北海道玩，請依照小明的需求規
劃一份行程表．
▸需求:
▸長輩喜歡戶外行程
▸小明喜歡逛街
▸想吃海鮮，拉麵和燒肉

81. HANDS-ON
▸According to the needs of the customer, choose a product
owner from your team members.
▸Ask your customer 3 questions about the product.

82. PRODUCT
BACKLOG

83. https://help.rallydev.com/rally-portfolio-manager-best-practices

85. AGILE PRODUCT ROADMAP
https://tech.gsa.gov/guides/develop_an_agile_product_roadmap/

86. RELEASE MAP AND USER STORIES
https://www.smashingmagazine.com/2017/09/comprehensive-overview-ux-design-deliverables/

87. SPRINT ROADMAP
https://medium.com/gestao-produtos/what-is-a-product-roadmap-9eaadc10c807

88. USER STORY AND BACKLOG
▸3 Ws
▸Who (user role)
▸What (goal)
▸Why (reason)
▸3Cs
▸Card
▸Conversation
▸Confirmation

89. EXAMPLE
▸AS a [User Role], I want to [Goal] so I can [Reason].
▸As a registered user I want to login so I can access
subscriber-only content

90. https://www.slideshare.net/rsrivastava91/introducing-agile-user-stories

91. https://www.slideshare.net/rsrivastava91/introducing-agile-user-stories

93. WRITE A GOOD USER STORY
https://www.farreachinc.com/blog/far-reach/2017/03/23/scrum-posters-(free-downloads!)

94. https://www.slideshare.net/FilipeLouro3/agile-user-stories-guide

95. BUSINESS VALUE AND PRIORITY
https://michaellant.com/2010/05/21/how-to-easily-prioritize-your-agile-stories/

96. SLACK
https://www.slideshare.net/nashjain/introduction-to-xp-and-scrum-practices

97. HANDS-ON
▸Write down 5 user stories and give each of them a business
value.
▸Please prioritize those user stories.
▸Write down how to confirm them.

98. SPRINT BACKLOG
https://www.yodiz.com/blog/product-backlog-vs-sprint-backlog-difference-in-agile-methodology/

99. http://scrumreferencecard.com/scrum-reference-card/

100. STORY POINTS
http://agiledigest.com/agile-digest-tutorial/agile-estimation/
RTANT: ONLY PEOPLE WHO WILL EXECUTE TASKS CAN ESTIMATE STORY P

101. TIPS
▸相對估算 > 絕對估算
▸粒度小 > 粒度大
▸估算單位用費式數列當作參考
http://www.codedata.com.tw/social-coding/estimation-with-dog-point-game/

102. https://medium.com/@MagnusDahlgren/a-quick-way-to-estimate-a-whole-backlog-cc5db956a0cf

103. https://help.rallydev.com/sizing-and-estimates

104. ADVANTAGE OF THIS METHOD
▸For PO/PM:
▸不用擔心被某些特定的 member 呼嚨或灌水。
▸評估過程中瞭解需求或任務在實作時，潛藏的難度在哪。
▸瞭解需求是否還有需要說清楚或被誤解的部分。
▸For team:
▸不再是不做事的人依照 deadline 給予一個不合理的時程限制。
▸在還沒開始動手進行任務之前，屬於開發人員之間的知識交換。不論因此增加或減少估
算的數字，都讓需求更明確，預估更客觀。
▸因為還不知道由誰認領此任務，所以客觀且有共識，透過過程也可以知道誰對此任務熟
悉度比較高，實際進行時，可以結對編程或知道找誰詢問與協助。
http://www.codedata.com.tw/social-coding/requirement-story-point-planning-poker/

105. STORY POINT AND ROI
https://www.scrumalliance.org/community/articles/2012/january/key-dimensions-of-user-stories

106. SCRUM BOARD
http://www.agilebuddha.com/agile/printing-physical-scrum-board-from-atlassian-jira/

107. HANDS-ON
▸Each sprint will be take 3 minutes.
▸Put user stories in the backlog for next sprint.
▸Convert each user story to tasks.
▸Estimate story points of each tasks.

108. https://www.safaribooksonline.com/library/view/learning-agile/9781449363819/ch04.html

109. BURNDOWN CHART
https://commons.wikimedia.org/wiki/File:SampleBurndownChart.png

110. IF YOU FACE A PROBLEM LIKE THIS...
http://lukeangel.co/project-management/whats-a-workback-schedule/

111. 專案範圍不變，團隊開發速率不變→專案時程的變化
http://www.codedata.com.tw/social-coding/scrum-project-gold-triangle/

112. 時程不變，團隊開發速率不變→專案範圍的變化
http://www.codedata.com.tw/social-coding/scrum-project-gold-triangle/

113. SCRUM BOARD WITH BURNDOWN
CHART
http://old.xpday.net/Xpday2008/sessions/SCRUM%20Board%20Game.html

114. MISUNDERSTANDING OF STORY
POINTS
▸Equating Story Points To Complexity, Uncertainty or Value.
▸Translating Story Points To Hours.
▸Averaging Story Points.
▸Adjusting Story Point Estimates of Issues During Sprint.
▸Never Story Pointing Bugs.
▸Conforming To The Expert In The Room.
▸Not Discussing Incorrectly Story-Pointed Issues In Retrospective.Not
Discussing Incorrectly Story-Pointed Issues In Retrospective.
https://medium.com/bynder-tech/12-common-mistakes-made-when-using-story-points-f0bb9212d2f7

115. REFLECT
▸這樣的做法在我們 team 裡面可能遇到什麼問題?

116. http://scrumreferencecard.com/scrum-reference-card/
Project A
Project B
Project C

117. DAILY SCRUM

118. DAILY STAND-UP MEETING
https://www.slideshare.net/dj1arry/week-8-presentation-slide

119. DAILY STAND-UP MEETING
http://www.the-program-manager.com/project-management/9-tips-for-an-effective-stand-up-meeting/

120. THE DAILY STAND-UPS
ARE MORE THAN JUST
ASKING WHAT YOU DID
AND IF YOU’RE BLOCKED.
IT’S ABOUT REACHING
THE SPRINT GOAL!
Patrick van Marsbergen
TEXT

121. HANDS ON
▸Let's develop (2 min)
▸Please hold a stand-up meeting in 30 seconds
▸Let's develop again (2 min)
▸Please hold a stand-up meeting in 30 seconds

122. REVIEW AND
RETROSPECTIVE

123. SPRINT REVIEW & RETROSPECTIVE

126. SPRINT REVIEW

127. HANDS-ON
▸Please demo your project to the customer.
▸Check what is not done in this sprint and move them to the
"To Do" column.

128. BASIC RETROSPECTIVE TEMPLATE

129. HANDS-ON
▸Please hold a retrospective meeting and write down:
▸what worked well
▸what can be improved
▸how to improve in the next sprint

130. https://www.linkedin.com/pulse/all-scrum-swapnika-g/

131. https://www.safaribooksonline.com/library/view/learning-agile/9781449363819/ch04.html

132. 敏捷是需要向給想掌握事情的人說
出深刻的實話，而在把尊重、敬意
與留面子看得很重的地方，這種說
實話的能力是很難的．
Claudio Caballero
- CTO of Goodwill Group
TEXT

133. HANDS-ON
▸Let's do again from plaining this sprint!

134. WORKFLOW
https://www.linkedin.com/pulse/6-agile-principles-apply-everything-%D1%95riram-cg

135. 【文思不藏私】@笨蛋，問題不在「敏捷」！
▸計劃會議（Sprint Planning）的目的，並不在於『計劃完善』而在於『溝通共
識』。
▸精煉會議（Refinement Planning）的目的，並不在於『技術分析』而在於『提
前溝通』。
▸每日站會（Daily Standup）的目的，並不在於『進度報告』而在於『資訊同步
』。
▸檢視會議（Sprint Review）的目的，並不在於『展示成果』而在於『分享價值
』。
▸回顧會議（Sprint Retrospective）的目的，並不在於『檢討過失』而在於『學
習自省』。
https://medium.com/%E6%96%87%E6%80%9D%E4%B8%8D%E8%97%8F%E7%A7%81/%E6%96%87%E6%80%9D%E4%B8%8D%E8%97%8F%E7%A7%81-%E7%AC%A8%E8%9B%8B-%E5%95%

136. SMALL TEAM, MULTIPLE PROJECTS: AN
AGILE APPROACH TO PLANNING
https://davidmarquis.wordpress.com/2011/12/03/small-team-multiple-projects-agile-planning/

137. COMBINE PROJECTS INTO VALUE
STREAMS

138. PUT ITEMS INTO SINGLE SPRINT
BACKLOG

140. FOCUS ON EACH PERSON
https://medium.com/@anttihavanko/how-to-handle-multiple-projects-with-a-small-team-ebdfde5f6714

141. FOCUS ON EACH PROJECT
https://medium.com/@anttihavanko/how-to-handle-multiple-projects-with-a-small-team-ebdfde5f6714

142. LET VALUE STREAMS SMALLER THEN
NUMBER OF MEMBERS
▸floor(team size / 2) + 1
▸ Team of 3: 2 value streams
▸ Team of 6: 4 value streams
▸ Team of 7: 4 value streams

143. eXtreme Programming

144. https://agilevelocity.com/agile/xp-values-forgotten-agile-guidance/

145. XP VALUES
https://www.slideshare.net/tsg.developer/extreme-programming-a-practitioners-approach-presentation/2-Outline

146. https://en.wikipedia.org/wiki/Extreme_programming

147. http://www.ambysoft.com/essays/whyAgileWorksFeedback.html

149. http://slideplayer.com/slide/6938506/

151. https://www.slideshare.net/nashjain/introduction-to-xp-and-scrum-practices

155. SCRUM BOARD
APPENDIX A

156. SCRUM BOARD
https://www.itworld.com/article/2832700/it-management/my--hypothetical--thanksgiving-scrum-board.html

157. SCRUM BOARD 2
https://www.tnpvisualworkplace.com/webshop/visualization-boards/scrum-boards/scrum-board-%7C-example-a

158. KANBAN
APPENDIX B

159. ▸Visualizing the flow
▸Limiting the WIP (Work In Progress)
▸Measuring the Lead Time
▸Optimize iteratively with data
https://www.avantica.net/blog/2016/11/17/dont-stay-in-the-shu-box-agile-is-not-a-recipe-4

160. VISUALIZE THE WORKFLOW
https://www.quora.com/What-is-Kanban-1

161. https://leankit.com/learn/kanban/kanban-board/

163. CUMULATIVE FLOW
https://www.microtool.de/en/what-is-a-cumulative-flow-diagram/

164. SCRUM BOARD VS KANBAN
https://www.slideshare.net/tothenewtech/introduction-to-kanban-21088273/42-Emphasis_should_be_on_the

165. SCRUM VS KANBAN
https://www.slideshare.net/tothenewtech/introduction-to-kanban-21088273/42-Emphasis_should_be_on_the

167. GOOD TO
GREAT
Johnny Appleseed

168. http://www.addictedtodigital.org/2017/06/book-summary-good-to-great/

169. IS EVERYTHING
PERFECT?

170. http://searchsoftwarequality.techtarget.com/photostory/4500251250/VersionOne-surveys-Agile-development-

171. http://searchsoftwarequality.techtarget.com/photostory/4500251246/VersionOne-surveys-Agile-development-

172. https://www.slideshare.net/DerkJandeGrood/walking-in-narrow-shoes-v03

173. RESOURCES
▸https://www.safaribooksonline.com/library/view/learning-
agile/9781449363819/ch01.html
▸http://wangterryonagile.blogspot.tw/2015/11/agile-tour-taipei-
2015-scrum.html