How to handle clients using Scrum-Agile - (Tips for Scrum Master)

Tip#1 -Spend a few moments to get inside your client’s head. Talk to them, listen carefully, figure out exactly how you need to package your ideas so that they will choose the option that’s best for their needs.

Tip#2 - Do your research and present your case clearly. Support your design decisions with data. 

Tip#3 - Build a Product backlog with clear acceptance criteria 

Tip#4 - Be specific about the project’s deliverable and outcomes, and protect yourself by       having a solid terms and conditions agreement in the event of out-of-scope work. 

Tip#5- Empower team to openly share the gaps and changes in the system the client is suggesting so that you can set expectation with client for successful delivery.

Tip#6- Identify the risks (Uncertainty/ambiguity in Environment,Technology,Domain) and keep a plan for this and inform to client. This can be updated on a regular DSM ( daily scrum meetings) or from Refinement meetings.

Tip#7 - Communication management - Ensure assumptions,Dependencies,questions are communicated to client and set a deadline to take action on these.

Happy project delivery to customer......!!

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