Your SlideShare is downloading. ×
0
Chapter 14  Sprints: Succeeding With Agile: Software Development Using Scrum
Chapter 14  Sprints: Succeeding With Agile: Software Development Using Scrum
Chapter 14  Sprints: Succeeding With Agile: Software Development Using Scrum
Chapter 14  Sprints: Succeeding With Agile: Software Development Using Scrum
Chapter 14  Sprints: Succeeding With Agile: Software Development Using Scrum
Chapter 14  Sprints: Succeeding With Agile: Software Development Using Scrum
Chapter 14  Sprints: Succeeding With Agile: Software Development Using Scrum
Chapter 14  Sprints: Succeeding With Agile: Software Development Using Scrum
Chapter 14  Sprints: Succeeding With Agile: Software Development Using Scrum
Chapter 14  Sprints: Succeeding With Agile: Software Development Using Scrum
Chapter 14  Sprints: Succeeding With Agile: Software Development Using Scrum
Chapter 14  Sprints: Succeeding With Agile: Software Development Using Scrum
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Chapter 14 Sprints: Succeeding With Agile: Software Development Using Scrum

410

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
410
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
6
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Chapter 14 Sprints<br />Succeeding With Agile: Software Development Using Scrum<br />David Ko<br />
  • 2. 如何在每個Sprint中,交付可運行的軟體<br />是新的Scrum團隊必須克服的最大挑戰之一<br />
  • 3. 為什麼要交付可運行的軟體<br />鼓勵回饋<br />Demo可收集到更多更好的意見<br />只有文件容易讓人遺忘和忽略<br />可衡量進度<br />Project最大的風險是不知道還剩多少東西沒完成<br />在需要時可及早發布<br />
  • 4. Potentially Delivery的含意<br />達到某個里程碑的標準<br />並非意味著沒有defect<br />重點是否做到了當初DoD (Definition of Done)所要求的<br />意味被測試過<br />不意味整個功能是完整的<br />意味著CI(Continuous Integration)已經做好<br />
  • 5. 每次試著交付有價值的東西<br />嘗試將功能分解, 以便在每次sprint可以交付<br />對於無法展示的功能, 多加一些額外的工作來展示其成果<br />Ex: Fake UI 或是測試執行結果報告<br />縱向切割比橫向切割好<br />
  • 6. 為下個Sprint做準備<br />在每個sprint中花點時間準備下一個sprint<br />Ken Schwaber建議約花10%時間準備下一個sprint<br />當然, 團隊可根據自己的經驗, 適當地調整<br />
  • 7. 只在一個sprint中加入能完成的東西<br />User story大小不能無法在一個sprint內完成<br />對於還不清楚的user story<br />在sprint前, 先充分理解, 而不是完全理解<br />若放入sprint 內的story, 必須被理解透徹<br />
  • 8. 在每個sprint保持一起合作<br />跨職能的成員一起合作<br />不是將工作由一個角色, 交給另一個角色<br />在scrum中不建議循序地執行工作, 也就是不斷地交接<br />
  • 9. 避免特定活動的sprint<br />原因如下<br />進度的不確性增加<br />因為取決於前一個sprint完成的品質如何<br />不易估計下個sprint要花多久處理<br />花很長時間來確認功能的特性<br />要經過數個sprint, 一個功能才被完成<br />無法盡早回饋<br />Analysis<br />Sprint<br />Design<br />Sprint<br />Coding Sprint<br />Testing Sprint<br />
  • 10. Sprint長度固定的好處<br />團隊有固定的節奏<br />知道何時開始, 何時要demo, 何時要開scrum的會議<br />Sprint計畫變得容易<br />經過2-5次的sprint, 容易根據歷史資料來規劃下次sprint的工作<br />Release planning變得容易<br />容易規劃要幾次sprint, 每個sprint要處理多少事情<br />不用每次sprint前, 都花時間討論這次要多長<br />
  • 11. 絕不要延長sprint<br />否則成員會覺得deadline是可以延長的<br />但是這代表你會有些東西在這個sprint中無法完成<br />因此若是有看到這跡象, 要及早馬上討論甚麼該被完成, 甚麼該被丟下<br />
  • 12. 若是中途要改變sprint的scope<br />不建議<br />通常是產品負責人缺乏遠見, 以至於計畫變動頻繁且快速<br />Scrum的作法<br />宣布目前sprint異常終止<br />重新對於新的變動加以計畫, 以建立新的sprint<br />

×