I've got a mixed team of UX, design, frontend and backend resources, using Jira. We are working in sprints and I have set up the following workflow: backlog --> In progress --> In Reveiw --> Done. My client wants to change it to UX --> Design --> Frontend --> Backend ect. I think that's not refelcting the agile methodology. Can you help with suggestions on making her understand that the workflow currently integrated works better for a multi disicplinary team? Her main concerns are that she can't see where the bottlenecks are, quick filters should help overcome. this. Any otehr suggestions?
Oh, I don't know that it doesn't fit with "Agile methodology". The main point in Agile is that you break things up into manageable parts, communicate well, keep the process "lean" so that everyone can get on and do useful things, and you deliver good stuff frequently.
Backlog -> In progress -> In Review -> Done works fine as an Agile process. But your client's suggestion doesn't look quite right. I'd have two questions
If you go for option 1 though, "Her main concerns are that she can't see where the bottlenecks are, quick filters should help overcome this" - you've hit on exactly the right answer. Define a quick filter for each component and she'll be able to toggle them on an off in a board and see exactly what the volumes are.
We're looking for participants for a workshop at Atlassian! We need Jira admins who have interesting custom workflows, issue views, or boards. Think you have a story to sha...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs