Hi Vikas,

I find your list oriented towards customer satisfaction but the ultimate measure of success is:

“I got the business value that i envisioned from the project.”  As you have stated in your list.

Unfortunately we often see that the business does a poor job in preparing the business case and sometimes it is even difficult to measure the business value within a reasonable time frame.

In such cases it is best to claim a project successful when you have delivered working software based upon customer’s requirements and your customer is satisfied about the whole engagement.

I have written about business value topic on Xebia blogs:

http://blog.xebia.com/2007/10/30/agile-need-not-deliver-business-value-early/

Regards,

Anurag Shrivastava

Visit Xebia on web at  www.xebia.com & blog.xebia.com  

NAUG Website: http://naug. wikidot.com | New presentation ideas are always welcome.

Agile India Yahoo Group: http://tech. groups.yahoo. com/group/ agileindia/ messages

---

From: agileindia@yahoogroups.com [mailto:agileindia@yahoogroups.com] On Behalf Of Vikas Hazrati
Sent: Monday, December 17, 2007 10:11 AM
To: agileindia@yahoogroups.com
Subject: Re: [agileindia] How to measure success on agile projects from customer point of view

Hi,

In my view measuring success on an agile project would be an ongoing thing throughout the project. The customer should be able to measure success of each iteration on the basis of business value delivered to him at the end of every iteration. This way he would be able to measure what he values success every iteration and fine tune it as and when required.

That being said as a customer I would be happy at the end of a project which was executed the agile way if

1. I got the business value that i envisioned from the project.
2. I was able to change course as per the business demands and get functionality delivered which makes more sense today.
3. I was able to give early feedback
4. I was able to prioritize the development of features/stories so that I got the right functionality at the right time
5. I was able to stop development before all the functionality was implemented because i realized that I got all the functionality that I wanted and rest of the functionality might never be used.
6. I trusted the development team and the trust relationship was vice versa
7. Impediments were raised frequently as and when they happened and I worked with the team to resolve them.
8. I got no surprises during the project.
9. I got peace of mind because every iteration gave me results and I knew i was in control.
10. I got value for money :)

Regards | Vikas

On Dec 14, 2007 5:50 PM, ANIKET MHALA < aniketm@techmahindra.com> wrote:

Hi,

I am basically looking for simple mechanism to measure success on agile projects from customer point of view.

How customer would measure/define success on agile project? Is there any simple matrix which would help customer to measure success on agile project?

Thanks in advance

Regards,

Aniket

============================================================================================================================ Disclaimer: This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at http://www.techmahindra.com/Disclaimer.html externally and http://tim.techmahindra.com/Disclaimer.html internally within Tech Mahindra. ============================================================================================================================