http://availagility.co.uk/2008/08/19/estimation-and-waste/ Karl Scotland - Using Agile to Deliver Value Sat, 06 Mar 2010 13:47:10 +0000 http://wordpress.org/?v=2.9.2 hourly 1 http://availagility.co.uk/2008/08/19/estimation-and-waste/comment-page-1/#comment-18 Karl Scotland Tue, 19 Aug 2008 14:29:29 +0000 http://availagility.wordpress.com/?p=82#comment-18 Hi hbflynn. If the client isn't agile, and the estimates are needed for a contract, then you should estimate. However, I still feel it is waste, as it isn't actually adding any value to the final deliverable. That being said, if you have a fixed date, then you can still estimate "how much" (3), which is easier if you have same sized, or classified (1). Hi hbflynn. If the client isn’t agile, and the estimates are needed for a contract, then you should estimate. However, I still feel it is waste, as it isn’t actually adding any value to the final deliverable. That being said, if you have a fixed date, then you can still estimate “how much” (3), which is easier if you have same sized, or classified (1).

]]> http://availagility.co.uk/2008/08/19/estimation-and-waste/comment-page-1/#comment-17 hbflynn Tue, 19 Aug 2008 12:48:39 +0000 http://availagility.wordpress.com/?p=82#comment-17 The challenge with No. 2, often found in service based organizations, is that clients need dates along with the estimates that get tied to a SOW. You may be Agile, but your clients may not be. It can be challenging and take time to get them to understand the value of developing software this way. I am struggling with this problem. The estimates are fine... but then you are put in a cast. I have yet to see much in the way of how best to structure service based contracts in an Agile environment, when your customer is not Agile. This is where estimation can have the biggest impact. The challenge with No. 2, often found in service based organizations, is that clients need dates along with the estimates that get tied to a SOW. You may be Agile, but your clients may not be. It can be challenging and take time to get them to understand the value of developing software this way. I am struggling with this problem. The estimates are fine… but then you are put in a cast. I have yet to see much in the way of how best to structure service based contracts in an Agile environment, when your customer is not Agile. This is where estimation can have the biggest impact.

]]>