一些進行scrum of scrums會議的建議 (2)
Advice on Conducting the Scrum of Scrums Meeting
http://www.mountaingoatsoftware.com/articles/35-advice-on-conducting-the-scrum-of-scrums-meeting
May 2007
Posted by Mike Cohn
一些進行scrum of scrums會議的建議 (2)
Advice on Conducting the Scrum of Scrums Meeting
http://www.mountaingoatsoftware.com/articles/35-advice-on-conducting-the-scrum-of-scrums-meeting
May 2007
Posted by Mike Cohn
一些進行scrum of scrums會議的建議 (1)
Advice on Conducting the Scrum of Scrums Meeting
http://www.mountaingoatsoftware.com/articles/35-advice-on-conducting-the-scrum-of-scrums-meeting
May 2007
Posted by Mike Cohn
Scrum of Scrums會議是一個非常重要的技巧, 讓大型的project teams用來進行scaling scrum. 這個會議允許切割團隊以用來討論他們的工作, 著重於integration和overlap的問題.
Bug bars
微軟在測試方面提出一個practice: bug bars.
也就是說他們會設定一個magic number, 當RD身上所負責的bug number超過這個數字, 他必須要停下手中的工作, 立即把bug number降到這個數字已下, 或者是全部解完.
它的目的是希望bug早點找到, 就能夠儘早被處理. 避免bug影響之後其他功能. 此外若是這bug很久之後才解, 容易被忘記它到底是怎麼發生, 或者是要根據哪個版本的source code才能解, 這都將增加問題處理的困難度
不過, 每種practice都容易被遭到濫用. 如果RD故意就是撐到這個數字才開始解, 而不是一開始找到就盡量解, 那原先的美意就被曲解了.
有問題的bug report種類
Defective Bug Reports
http://blogs.msdn.com/imtesty/archive/2006/06/28/649862.aspx
June 28, 2006
Posted by Bj Rollison
Published in I.M.Testy