Comments on: 3 Ways to Kill Focus in Agile Projects http://www.pmhut.com/3-ways-to-kill-focus-in-agile-projects Thu, 17 May 2012 02:40:15 +0000 http://wordpress.org/?v=abc hourly 1 By: Rodney http://www.pmhut.com/3-ways-to-kill-focus-in-agile-projects/comment-page-1#comment-19980 Rodney Tue, 13 Apr 2010 04:20:24 +0000 http://www.pmhut.com/?p=4403#comment-19980 I agree with David above, there has to be a point when the Agility of the Agile Methodology is overrun with the varying expectations of the client. I've completed a task for NAB where the number of requirements had doubled from the initial quote, and the business person was renowned for pressing more after the quote was given and accepted. We used to be told dont provide anymore func pts than the spec asks for because the customer will likely change their mind. Its bad management practice in Agile or Waterfall to accept every new story or use case or func pt, without standing back at some point and seeing the trend of engagement with the client. I agree with David above, there has to be a point when the Agility of the Agile Methodology is overrun with the varying expectations of the client. I’ve completed a task for NAB where the number of requirements had doubled from the initial quote, and the business person was renowned for pressing more after the quote was given and accepted.

We used to be told dont provide anymore func pts than the spec asks for because the customer will likely change their mind.

Its bad management practice in Agile or Waterfall to accept every new story or use case or func pt, without standing back at some point and seeing the trend of engagement with the client.

]]> By: David Pletcher http://www.pmhut.com/3-ways-to-kill-focus-in-agile-projects/comment-page-1#comment-13835 David Pletcher Mon, 14 Dec 2009 22:38:02 +0000 http://www.pmhut.com/?p=4403#comment-13835 You could simply delete "Agile" and then these issues describe the proverbial 99.9% of software project problems. For point 3, if you are receiving that many changes to requirements then stop. There is no need to 'sprint' or do anything at this point. What needs to be done is for the product manager to renegotiate terms with the customer (or sponsor). I suspect some will gasp at the prospect of doing so, but it is a legitimate option that organizations, managers and teams neglect. You could simply delete “Agile” and then these issues describe the proverbial 99.9% of software project problems.

For point 3, if you are receiving that many changes to requirements then stop. There is no need to ’sprint’ or do anything at this point. What needs to be done is for the product manager to renegotiate terms with the customer (or sponsor). I suspect some will gasp at the prospect of doing so, but it is a legitimate option that organizations, managers and teams neglect.

]]>