Many clients are slow, It’s better to simply reduce your exposure to that risk. You can send progress report to clients who stall, and write into your estimate that you cannot maintain schedules for clients who are late on deliverable.
When you are following SCRUM in a project you are managing, how to handle delays? Explain your experiences here to handle the situation
What kind of delays are you talking about? Would you give a practical example, so we can provide answers for handling that situation.
For example, if this is about missing details in development tasks, you can have a definition of ready, which means stories need to reach that in order to be eligible for estimation. This means they would not enter a Sprint anyway, so there would not be a problem with client not providing the details. If the client feels this is a problem for them, they need to find tools (hopefully together with the SCRUM team) to take corrective actions.
Jari Laakso, First of all I would like to say thank you for the detailed explanation.
For example, Being a QA member for a Music Distribution website production team where a new feature was considered so critical that it was prioritized over everything else in the backlog. Minimal time was taken for the development of user stories and my team had to make assumptions because the business stakeholders were unavailable. When we were nearing completion, the stakeholders came out of hiding and identified more business rules that required not only additional work, but some re-work of things that were already completed, including global changes to the company’s customer-facing website. The impact to the business had not been appropriately analyzed, and when the new feature was rolled out, the value delivered was negative, causing refunds and ultimately financial loss.
How to handle such kind of situations.. ?? Your prompt feedback highly appreciated….
This reply was modified 2 years, 3 months ago by Amna Sherazi.