Thoughts and Perceptions on Agile, Lean and related software development methods Have you come across teams struggling in iterations bombarded with surprises ? I have seen many times. Teams and POs concentrate mostly on “Definition of Done” by keeping the end in mind, which is good. However, it is also important to evaluate the readiness before entering the iterations. As we all know, Garbage in
Thoughts and Perceptions on Agile, Lean and related software development methods Product Owner (PO) plays a pivotal role in Scrum projects. As the saying goes “Garbage in – Garbage out”, if the PO provides poor quality requirements, the developers churn out equivalent code, and in turn an inferior product. We keep seeing a lot of failed products in the market. If we track back and identify the ro
Thoughts and Perceptions on Agile, Lean and related software development methods Iteration 0 is typically the duration between the initial “Discovery” and “Evolve Phase” of a software project. As such, there is no formula or a number to determine the iteration 0 duration, which suits all the projects. I use the following check list to decide the duration 1. Duration of the project : If the durat
An interesting discussion about Who should be blamed for a failed Scrum Project ? in Scrum Practitioners forum made me to write this short article. Personally, I feel that as long as there is a blame game culture around, the weakest one gets the blame. My experience has been that being more vocal one could push away blame easily. As far as I know, there is no democratic debate to nail down the c
Thoughts and Perceptions on Agile, Lean and related software development methods Have you observed that every company wants to be known as an Agile company(company implementing Agile methods), but no one wants to really follow Agile by the book ?. Software Project teams do a lot of Agile tweaking during the journey of implementing Agile to fit the company’s culture. Since, company’s culture cannot
Thoughts and Perceptions on Agile, Lean and related software development methods There are several ways to prioritize the requirements in the backlog. Some of the most popular ones include, MoSCoW M - MUST have this. S - SHOULD have this if at all possible. C - COULD have this if it does not effect anything else. W - WON'T have this time but would like in the future. Each requirement will have the
Thoughts and Perceptions on Agile, Lean and related software development methods It is a tradition to use MS Project as a Project Management tool in Waterfall projects. However, trying to use MS Project in an Agile project makes the lives of the developers more difficult than easy. There are several reasons for that and a few based on my personal experiences are.. 1. Adding new tasks in between as
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く