Despite an approved detailed statement of work (SOW), an agile service delivery team can fail to meet customer expectation. Though SOWs are the safest bait to wash your hands off of a failed delivery, you cannot be lucky twice. In this CA Technologies article, Kristy Corkan shares 2 best practices that an agile service delivery team must follow.
Excellence in Agile Service Delivery
It is common for teams that adopted agile recently to compose SOWs which is signed by the stakeholders. However, there are going to be differences in how you deliver the product and how the client envisioned it. You will inevitably work on change requests that delay the final delivery date. The agile service delivery team can imbibe the following best practices to avoid delay in delivery:
- No-Frills Requirements and Estimation Period: Do not make detailed SOWs. Ensure your customers, the accounts department, and the service team agrees to this informally. The agile services delivery team can then focus on the change requests. Understand the immediate goal of this change and the value it provides. Analyze the pitfalls and limitations of obliging this request. When you have listed all the requests, let the agile services delivery team discuss doubts and probable solutions. Come up with an estimate for every solution. Create a SOW based on the finalized solution and estimate.
- Regular Collaboration and Feedback from Customers: Update the customers on the project progress and proactively ask for feedback. Create a backlog of their requests and divide them into small deliverables that you can prioritize strategically. Do weekly checkpoint meetings to provide a working model and reprioritize backlogs. You must continue this process to improve customer engagement. Since they do not have a detailed documentation, these updates will remove their investment doubts. Maintain transparency by clarifying their questions. They might understand the pros and cons of their vision when it becomes reality. If you are co-located, provide regular working models. Or else, weekly or biweekly updates will do.
To view the original article, visit the following link: https://www.ca.com/en/blog-highlight/key-practices-for-agile-services-delivery.html