In both my consulting and my teaching practices I am astonished by how many people ask about handling interruptions to the work of an Agile team. Of course, many organizations are interrupt-driven, particularly with shoddy software in the field (and by shoddy, I don’t just mean full of bugs but also having very poor usability). Interruptions also come for positive reasons such as a changing ma
This article is one of the most popular on the Agile Advice blog. As well, reprinted, it has become one of the staples of my training courses. Of course, it is not a completely exhaustive list, and honestly some of these pitfalls aren’t really that common anymore, but nevertheless it is a good check against your own use of Scrum. However, a word of caution is also appropriate here: some bad Scr
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く