如何利用Daily Burndown Chart來追蹤進度
How To Implement Scrum In 10 Easy Steps - Step #8: Track Progress With A Daily Burndown Chart
http://www.agile-software-development.com/2007/11/how-to-implement-scrum-in-10-easy-steps.html
Posted by Kelly Water
Published in All About Agile
通常傳統的的開發專案, 在一開始的時候, 開啟來一切都很順利, 幾乎有80%的完成率. 可是隨著時間的演進, 事情越來越糟, 越來越多事情無法on schedule.直到最後的關頭, 你終於承認你無法達到原先的目標, 可是那時候已經為時已晚, 已經無法做什麼事情可以幫助它來改善.
在Agile的開發專案中, 有些好的principle可以早點指出這樣的問題. 雖然一開始令人看起來很不安, 但是仍然有時間可以做些事情來改善它.
像是testing, 在傳統開發流程中, 他總是在最後關頭才做, 因此在面對龐大的系統要做測試, 其品質即時程程很難控制的. 可是在Agile開發流程中, 測試的活動是伴隨著整個流程, 因此一旦某個feature完成, 通常也代表他已經經過適當的測試. 不會到最後才來確認他的品質.
因為Product Owner或是customer加入, 在整個流程的當中, 隨時可以review 產品, 以確認產品有照著需求來做.
除了這些principles外, 每天的stand-up meeting, 可以幫助你清楚知道整個專案的進度如何, 每個人會提供他自己的的處理狀況給所有team members知道
但是, 除了這樣之外, 作者認為Daily Burndown Char也是一個好的工具, 它很簡單, 但是很有用. 要怎樣來使用這個工具呢? 以下是作者覺得要注意的地方:
1. 'Estimate To Complete'
- Take all the tasks to be delivered in a particular Sprint in Scrum, i.e. your Sprint Backlog you created in step 4.
- On your Sprint Backlog, enter the estimated time to complete, which of course at the beginning of the Sprint is the same as the original estimate.
- Update the estimated time to complete (ETC) each task on a daily basis.
2. Team members需要對自己負責
- Each team member can be responsible for updating their own ETC's on a daily basis before the Scrum.
- Updating it daily - and sharing the effort amongst the team - means typically there should only be 2 or 3 items to update for each person each day.
- Therefore it should not be onerous and means team members take responsibility for their own tasks
- Be honest about what effort you believe is required to complete each task (and that's the effort needed to really complete each task), regardless of how long has been spent to date and regardless of what was estimated in the first place.
3. 清楚標示出團隊的目標
- The team's goal, quite simply, is for the team to reach zero hours to go, by the end of the Sprint duration.
4. 以視覺化圖形方式來呈現你的進度
- The beauty of this approach is that it's a numeric view of progress and can therefore be plotted visually on a graph.
- Plot the original estimates for the Sprint on one line, and the current estimates to complete on another line.
- When the actual line tracks below the original estimate line, you're on track.
- When it tracks higher, you're running behind. It really is as simple as that.
- Highly visual, instant feedback for the whole team.
5. 紀錄關鍵事件
- I've also found it useful to annotate the graph with 'speech bubbles' describing key events along the way.
- This is a useful way to record significant events so they're not forgotten by the time of the Sprint review.
- It's also useful to communicate important things to management and stakeholders instead of producing a separate status report.
6. Scrum 會指出你的問題, 但是不會解決它
- Using a burndown chart, when you spend one day on a task and discover
* a whole load of problems or
* effort you hadn't anticipated or
* estimated for, the estimate to complete jumps up,
* creating an all-too-visual indicator of the problem for all to see.
- When this happens early in a project, and/or on a large scale, believe me it's pretty scary!
- Suddenly you're not so sure about all this new-found visibility!
- It seemed like such a good idea at the time, but can you really stick *that* burndown chart on the wall?!
7. 呈現真實的狀態反應
- But you do gain one big advantage. One enormous advantage.
- You get to see where the project really is, every day, in all its techni-colour glory!
- And when you hit problems in a project, you actually see them.
- And see them when you might just have time to do something about it.
How To Implement Scrum In 10 Easy Steps - Step #8: Track Progress With A Daily Burndown Chart
http://www.agile-software-development.com/2007/11/how-to-implement-scrum-in-10-easy-steps.html
Posted by Kelly Water
Published in All About Agile
通常傳統的的開發專案, 在一開始的時候, 開啟來一切都很順利, 幾乎有80%的完成率. 可是隨著時間的演進, 事情越來越糟, 越來越多事情無法on schedule.直到最後的關頭, 你終於承認你無法達到原先的目標, 可是那時候已經為時已晚, 已經無法做什麼事情可以幫助它來改善.
在Agile的開發專案中, 有些好的principle可以早點指出這樣的問題. 雖然一開始令人看起來很不安, 但是仍然有時間可以做些事情來改善它.
像是testing, 在傳統開發流程中, 他總是在最後關頭才做, 因此在面對龐大的系統要做測試, 其品質即時程程很難控制的. 可是在Agile開發流程中, 測試的活動是伴隨著整個流程, 因此一旦某個feature完成, 通常也代表他已經經過適當的測試. 不會到最後才來確認他的品質.
因為Product Owner或是customer加入, 在整個流程的當中, 隨時可以review 產品, 以確認產品有照著需求來做.
除了這些principles外, 每天的stand-up meeting, 可以幫助你清楚知道整個專案的進度如何, 每個人會提供他自己的的處理狀況給所有team members知道
但是, 除了這樣之外, 作者認為Daily Burndown Char也是一個好的工具, 它很簡單, 但是很有用. 要怎樣來使用這個工具呢? 以下是作者覺得要注意的地方:
1. 'Estimate To Complete'
- Take all the tasks to be delivered in a particular Sprint in Scrum, i.e. your Sprint Backlog you created in step 4.
- On your Sprint Backlog, enter the estimated time to complete, which of course at the beginning of the Sprint is the same as the original estimate.
- Update the estimated time to complete (ETC) each task on a daily basis.
2. Team members需要對自己負責
- Each team member can be responsible for updating their own ETC's on a daily basis before the Scrum.
- Updating it daily - and sharing the effort amongst the team - means typically there should only be 2 or 3 items to update for each person each day.
- Therefore it should not be onerous and means team members take responsibility for their own tasks
- Be honest about what effort you believe is required to complete each task (and that's the effort needed to really complete each task), regardless of how long has been spent to date and regardless of what was estimated in the first place.
3. 清楚標示出團隊的目標
- The team's goal, quite simply, is for the team to reach zero hours to go, by the end of the Sprint duration.
4. 以視覺化圖形方式來呈現你的進度
- The beauty of this approach is that it's a numeric view of progress and can therefore be plotted visually on a graph.
- Plot the original estimates for the Sprint on one line, and the current estimates to complete on another line.
- When the actual line tracks below the original estimate line, you're on track.
- When it tracks higher, you're running behind. It really is as simple as that.
- Highly visual, instant feedback for the whole team.
5. 紀錄關鍵事件
- I've also found it useful to annotate the graph with 'speech bubbles' describing key events along the way.
- This is a useful way to record significant events so they're not forgotten by the time of the Sprint review.
- It's also useful to communicate important things to management and stakeholders instead of producing a separate status report.
6. Scrum 會指出你的問題, 但是不會解決它
- Using a burndown chart, when you spend one day on a task and discover
* a whole load of problems or
* effort you hadn't anticipated or
* estimated for, the estimate to complete jumps up,
* creating an all-too-visual indicator of the problem for all to see.
- When this happens early in a project, and/or on a large scale, believe me it's pretty scary!
- Suddenly you're not so sure about all this new-found visibility!
- It seemed like such a good idea at the time, but can you really stick *that* burndown chart on the wall?!
7. 呈現真實的狀態反應
- But you do gain one big advantage. One enormous advantage.
- You get to see where the project really is, every day, in all its techni-colour glory!
- And when you hit problems in a project, you actually see them.
- And see them when you might just have time to do something about it.
全站熱搜
留言列表
