I've been managing the Jira deployment for my organization, and have streamlined a few aspects of the setup to achieve consistency across Projects. The only aspect that doesn't sit well with me so far, is the Sprint Management.
Let me describe our setup a little bit:
Here's what we want to achieve:
Hurdles we are facing:
All that put together, I feel I still don't understand the right way to manage sprints as Atlassian had intended. Can anyone point me in the right direction, if I am straying?
I'm with Dave on this one - people first, process second, your choice of tools should fall out third (and as the Atlassian fanboy, use the Atlassian suite that is built with people first. But do not do that unless it is right - do what works best for you)
Thank you for your responses, @Dave Mathijs and @Nic Brough -Adaptavist- , and let me state that I believe in the same as well, and I'm not going to prioritize a tool over people.
I was only wondering how the Product Managers had intended the product to be used. As I have mentioned in my post, I want to achieve a few things, and I am facing some challenges that I can't seem to overcome.
Jira Software was built to support Scrum and Kanban. With these, a board generally represents a team. Your people going off and creating their own boards is not a problem, but if they're creating their own sprints, they are not working as a team.
There's a whole load of things I could address individually in your question, but they are all down to a core problem - your people are not working as a team.
Thank you for making time to respond to my concern :)
Now, I didn't mention that my team members are creating sprints. Please allow me to repaint the picture. Here's the chronology of events:
Additionally, since you mention there's a whole load of things that you could address, if you would be kind enough to share your insights on how it should be done ideally, I'll be very grateful.
Cheers!
Stop trying to manage sprints in different boards - they do not work the way you are guessing they do. A sprint should be closed from the board the sprint was created in, as a board represents a sprint team.
That's my wish too, and the challenge I am facing with this is - I can't restrict it for sure. If it was the original expectation in Jira that the Sprint should be managed from the board it was created on, there should be indications about it.
Right now, when I get to a sprint, there's no way to see where it was created. It only tells me the boards that it appears on.
That's what I have mentioned in my original post as well
- There's no central place of listing all the sprints, and the boards that they were created on
I understand, appreciate and agree with what you're suggesting, but seems like there's no way to enforce the behaviour right now. If there's a way, I don't know about it yet and it would help if you could point me in the right direction.
Recommended Learning For You
Level up your skills with Atlassian learning
Learning Path
Apply agile practices
Transform how you manage your work with agile practices, including kanban and scrum frameworks.
Learning Path
Configure agile boards for Jira projects
Learn how to create and configure agile Jira boards so you can plan, prioritize, and estimate upcoming work.
Jira Essentials with Agile Mindset
Suitable for beginners, this live instructor-led full-day course will set up your whole team to understand how to use Jira with an agile methodology.