Why and how to build a relationship with Customer in Agile Projects

  • The very first thing you must do to become Agile is establish a good relationship with your customers, users, and domain experts; who ever it is that directly or indirectly pays for your work.
  • The first symptom of a damaged customer relationship is when your customer considers it a waste of time to participate in the project. 
  • You may have delivered software that just doesn't meet return on investment (ROI).
  • In any case your customer is important and you need to repair your relationship first.
  • One way to start a partnership with your customers is to listen to their needs and respond immediately.
  • The best way to guarantee your customer's time (and thus money) isn't wasted is to involve them enough to guarantee success.
  • Respect your customer by acknowledging their expertise, listen carefully, defer to their authority, and never insert your own opinions into your code.
  • Communicate with your customers simply and in a language they understand.
  • If your customers think being part of software development is wasteful you might be  building the wrong software.

Source-  http://www.agile-process.org/first.html

Comments

Post a Comment

Popular posts from this blog

Scrum Answer to Top 10 Software Project Risks

Source: (The Standish Group, 2011) Lack of top management commitment Scrum demands commitment from the top management through the assignation of a full-time cross-functional self organized team. The team is protected and can take their own decisions about the project with the support of the top management. Failure to gain user commitment In Scrum, the team constantly show working software to the users, which increase the commitment and feedback. Misunderstanding the requirements Scrum knows that is not possible to fully understand all the user requirements. In each iteration, the team work in the more important and clear requirements. As the software is developed, the team get better insights about the project goals and have more clarity about the following requirements. Lack of adequate user involvement Constantly working software makes the users more involve in the process. Lack of required knowledge/skills in the project personnel In Scrum, the teams are cros...
Read more