Comments on: My inferences about Agile from Sanjiv Augustine’s workshop at Xebia India http://blog.xebia.com/2008/11/21/my-inferences-about-agile-from-sanjiv-augustines-workshop-at-xebia-india/ Software development done right! Wed, 08 Feb 2012 14:41:38 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Serge Beaumont http://blog.xebia.com/2008/11/21/my-inferences-about-agile-from-sanjiv-augustines-workshop-at-xebia-india/#comment-63828 Serge Beaumont Sun, 23 Nov 2008 09:08:06 +0000 http://blog.xebia.com/?p=817#comment-63828 @Josh: I rephrase the WBS part. A backlog is a list of outcomes, not work. So it is a Product Breakdown Structure, not a WBS. One of the traps of planning based on activity is the belief that executing all activities will automatically achieve the end results. Of course this is not the case, and everybody should have the outcome in mind at all times. This is what allows a team to identify the need for different work than was originally planned to reach the outcome. @Josh: I rephrase the WBS part. A backlog is a list of outcomes, not work. So it is a Product Breakdown Structure, not a WBS. One of the traps of planning based on activity is the belief that executing all activities will automatically achieve the end results. Of course this is not the case, and everybody should have the outcome in mind at all times. This is what allows a team to identify the need for different work than was originally planned to reach the outcome.

]]> By: Anurag Shrivastava http://blog.xebia.com/2008/11/21/my-inferences-about-agile-from-sanjiv-augustines-workshop-at-xebia-india/#comment-63799 Anurag Shrivastava Sun, 23 Nov 2008 06:47:53 +0000 http://blog.xebia.com/?p=817#comment-63799 "The fact that Agile is built on passion, transparency, trust, discipline, liberty, opportunity, reciprocity and equality helps in creating a great and highly productive working environment." Many people ask how they can build an Agile team in a company. Passion,....,equality are the first things to be looked at. Teams may falter at times. Managers should play a crucial role in keeping the Agile spirit alive. “The fact that Agile is built on passion, transparency, trust, discipline, liberty, opportunity, reciprocity and equality helps in creating a great and highly productive working environment.”

Many people ask how they can build an Agile team in a company. Passion,….,equality are the first things to be looked at. Teams may falter at times. Managers should play a crucial role in keeping the Agile spirit alive.

]]> By: Abhinav Kumar http://blog.xebia.com/2008/11/21/my-inferences-about-agile-from-sanjiv-augustines-workshop-at-xebia-india/#comment-63723 Abhinav Kumar Sat, 22 Nov 2008 18:35:13 +0000 http://blog.xebia.com/?p=817#comment-63723 Thanks for reading the post and adding your invaluable comments. It is immaculate. I could not have agreed more. Perhaps I could have been more explicit by saying that plan the work ONCE and work that plan FOREVER is not the way to go anymore. And thanks for showing the way to go in no implicit terms. Thanks for reading the post and adding your invaluable comments. It is immaculate. I could not have agreed more. Perhaps I could have been more explicit by saying that plan the work ONCE and work that plan FOREVER is not the way to go anymore. And thanks for showing the way to go in no implicit terms.

]]> By: Josh Nankivel http://blog.xebia.com/2008/11/21/my-inferences-about-agile-from-sanjiv-augustines-workshop-at-xebia-india/#comment-63649 Josh Nankivel Sat, 22 Nov 2008 11:36:06 +0000 http://blog.xebia.com/?p=817#comment-63649 Thanks for the post. I just wanted to add a little more to your comments about the planning that is still required with Agile. This is what I have used in the past and have found works well. The moral of the story is that you don't get away with less planning when you do Agile right, in my opinion. You are just spreading out your planning across the sprints, and so you have more information with each one...and your planning gets better and better. You STILL plan the work, and work the plan. 1) Develop a high-level plan up front. This is much less rigorous than traditional waterfall planning, but gives you a high-level WBS structure, major deliverables/list of features, engineering approach, architecture, etc. You plan how many sprints the project should take and roughly how many features will get developed each sprint. 2) Plan each sprint in detail regarding the features that will be developed, and stick to that plan for the duration of the sprint. 3) After each sprint review, you have better information to adjust the high-level project plan, and make the next sprint plan more accurate. Josh Nankivel http://pmStudent.com Thanks for the post. I just wanted to add a little more to your comments about the planning that is still required with Agile. This is what I have used in the past and have found works well. The moral of the story is that you don’t get away with less planning when you do Agile right, in my opinion. You are just spreading out your planning across the sprints, and so you have more information with each one…and your planning gets better and better. You STILL plan the work, and work the plan.

1) Develop a high-level plan up front. This is much less rigorous than traditional waterfall planning, but gives you a high-level WBS structure, major deliverables/list of features, engineering approach, architecture, etc. You plan how many sprints the project should take and roughly how many features will get developed each sprint.
2) Plan each sprint in detail regarding the features that will be developed, and stick to that plan for the duration of the sprint.
3) After each sprint review, you have better information to adjust the high-level project plan, and make the next sprint plan more accurate.

Josh Nankivel
http://pmStudent.com

]]>