Comments on Agile Software Development Made Easy!: Agile Principle #5: How Do You Eat An Elephant?

Hi srutanjayRe your first point, I have worked in ...

2008-05-15T10:32:23.191Z

Hi srutanjay

Re your first point, I have worked in development for many years and the only reason I've ever had to do this is to argue with people about why we're late. In agile development, the key stakeholders (especially the product owner) should have been involved throughout, so this risk is mitigated. In my experience of agile, I don't think I've seen this need once as a result.

If any requirements are defered for a later release, they can simply be captured on the product backlog and a new user story written nearer the time of development.

It's a very interesting point though. Has anyone else got a view on this?

Kelly.

Hi kelly,First, when requirements keep getting mod...

2008-05-15T09:39:00.000Z

Hi kelly,

First, when requirements keep getting modified due to iterative method of development, one may need to see how the final requirement has shaped up as compared to the initial one.

Secondly, as time and cost are fixed, some of the requirements may be differred for a later release.

Thanks.

Hi srutanjayYou say "it's important to track the r...

2008-05-14T16:42:08.703Z

Hi srutanjay

You say "it's important to track the requirements" - why is that?

Kelly.

Well, when changes happen over a small discussion ...

2008-05-14T09:03:00.000Z

Well, when changes happen over a small discussion or verbally it is important that those are tracked. how are the changes documented. At the end of the day it is important to track the requirements, though it may keep changing.
Thanks.

Very nice and succinct. I will borrow some langua...

2007-07-05T02:14:51.661Z

Very nice and succinct. I will borrow some language for a presentation I need to give!
Thanks.

Hi Kelly. I posted a link from my blog to yours. T...

2007-03-26T17:34:09.578Z

Hi Kelly. I posted a link from my blog to yours. Thanks for the information.