who should own the Jira board Development team or Scrum Master
Please share your own thoughts on this topic with why?
It will be very helpful to me.
Have the Development Team defined their workflow? Can they account for where it begins and ends in Jira?
Although Ian Mitchell asked some good questions, I'm more curious as to what you mean by "own". What does "ownership" of Jira, or any tool, actually entail? Also, why is the Product Owner not considered as a possible "owner" of Jira?
Who is doing the work accounted for on the board and why would anyone but those individuals own the board? Is a Scrum Master a Project Manager?
(I think this is first time I have ever been able to pull an @Ian!!)
Why not whole Scrum Team? PO has some responsibility in managing backlog (which I guess would be stored in JIRA), while then the Dev Team should update status of their work items in JIRA. It is not too much of a hassle, and brings a lot of transparency. The SM makes couches the other roles to do as described in previous sentence.
Did this ever get answered? My opinion is that a PO "own" the product which may be represented as a Project in Jira.
Additionally, the Development Team "owns" the board that they work from, and carries out the DoD in a high-level visual manner via the Jira Scrum or Kanban board.
The Jira Project would not exist without a Product to deliver, and therefore having the PO "own" the Jira Project seems the correct route to take.
The Jira Board, would not have anything done if it were not for the Development Team, and therefore having the Development Team "own" the Jira Board seems the correct route to take.
Hope this helps!
Just a little nitpick, it's the Developers, not Development Team.
What exactly is the content of a "Jira board"?