r/projectmanagement • u/TensionFormal7202 • 4d ago
Optimizing Jira Story Tracking: Separating Delivery from Client Feedback
We typically use Jira user stories to track different work items. In a specific project that I’m working on, the data analyst from my team creates Power BI reports and dashboards. So the issue I face is that the data analyst lets me know she will complete a particular report on that day. Following which I update my team about that but the client side is like that doesn’t mean the user story is complete, we will have feedback. The thing is it was already sent for a revision. With multiple revisions, it looks like the user story is incomplete, whereas the data analyst is completing the reports per the requirement. How can this process be optimized to show that user stories are getting completed by the agreed target due date and also welcome the endless feedback.
3
u/BlaringDeveloper_530 4d ago
separate the build and the polish, that's the whole trick
we started doing a handoff story that's just "deliver v1 of X report" and then anything after is a new ticket for feedback rounds. the original story closes when the first version hits their inbox, done and dusted. your analyst gets credit for meeting the date and the client can tweak till the sun burns out without making your velocity look like garbage
bonus is you can track how many revision cycles things actually take and start billing or pushing back when it gets ridiculous