Comments on: Going Agile, 10 Mistakes: Don’t Create a Project Plan http://tynerblain.com/blog/2006/12/27/going-agile-mistake-06/ Software product success. Sun, 12 Feb 2012 19:10:25 +0000 hourly 1 http://wordpress.org/?v=3.0.4 By: Scott Sehlhorst http://tynerblain.com/blog/2006/12/27/going-agile-mistake-06/comment-page-1/#comment-59687 Scott Sehlhorst Thu, 28 Dec 2006 17:01:44 +0000 http://tynerblain.com/blog/2006/12/27/going-agile-mistake-06/#comment-59687 Sorry for the confusion Johanna - the "mistake" would be not having a project plan. My thoughts are that when transitioning to Agile for the first time, over-communication (early and often) is very important. We're asking our execs to take a leap of faith and do something they haven't done before. Thanks again for reading and commenting! Sorry for the confusion Johanna – the “mistake” would be not having a project plan. My thoughts are that when transitioning to Agile for the first time, over-communication (early and often) is very important. We’re asking our execs to take a leap of faith and do something they haven’t done before.

Thanks again for reading and commenting!

]]> By: Johanna Rothman http://tynerblain.com/blog/2006/12/27/going-agile-mistake-06/comment-page-1/#comment-59681 Johanna Rothman Thu, 28 Dec 2006 13:38:29 +0000 http://tynerblain.com/blog/2006/12/27/going-agile-mistake-06/#comment-59681 I must be confused. Are you saying to *not* develop a release plan? Especially when you're moving to agile, not having any plan will confuse management and make them suspicious. It's reasonable to create a release plan that says, "Here's where we're headed. We will take two iterations to measure our progress and update the release plan. In the meantime, here's the location of our product backlog and here's the location of our iteration backlog, if you want to see where things are." Maybe I don't understand what you're saying. I must be confused. Are you saying to *not* develop a release plan? Especially when you’re moving to agile, not having any plan will confuse management and make them suspicious.

It’s reasonable to create a release plan that says, “Here’s where we’re headed. We will take two iterations to measure our progress and update the release plan. In the meantime, here’s the location of our product backlog and here’s the location of our iteration backlog, if you want to see where things are.”

Maybe I don’t understand what you’re saying.

]]>