How do you create a board?

Stuart Clark May 25, 2015
 

3 answers

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

0 votes
Answer accepted
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 25, 2015

Click "manage boards" -> "Add board".

I suspect there is more to this question though - could you explain what you are looking for?

0 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 26, 2015

Makes sense.  There's a lot of variation in Agile and part-Agile, and JIRA is mostly flexible enough to support a lot of approaches.

JIRA Agile was built with Agile in mind though, so when you drift far enough away from it, it can become a bit convoluted. JIRA Agile gives you two options for boards - Scrum and Kanban.  Although we could ramble for hours about how they're not quite right for certain Agile stuff and missing things people would like in others, I try not to.  

My usual opening question is "do you want to plan your work, in some form of segmented time frames".  If you do, use a Scrum board.  If you don't, then use Kanban.

You've already indicated you want planning, so Scrum it is.  I'd create a Scrum board, and get it right ("right" meaning "works for you", not "follows agile doctrine to the letter").  In my head, I then bypass all that waffle about Agile and tell you to do three things:

  1. Use only ONE scrum board per team or planning group or product.  This keeps it simple, your sprints don't leak into other places and everyone knows how to plan stuff.  Ideally, avoid having projects appear in multiple scrum boards.
  2. Use Kanban boards for everything else. You can think of them of "views" of the issues, and you can do what you like to the issues on Kanban boards without breaking the scrum board or other people's Kanbans.  So you can have many of them.  They respect all the rules you set up for the projects and won't mess up Scrum (although your changes will be reflected in Scrum, as that is also a "view" on to your issues)
  3. Train your users not to click "release" on the Kanban boards.  It just messes with versions, and it may actually be ok, but until you understand how you're working, stick to the scrum board versioning.

Once you've got one scrum and several kanbans running, you'll get used to it, then you can tweak and expand as needed.  But get a scrum board to do what you want first, and work from there.

 

0 votes
Stuart Clark May 26, 2015

Thanks Nic, I actually wanted to create a project plan with some workflows beyond one test/issue... a reporting process and output structure needs to be re-designed in full, and completed within about 5 weeks, so it's not a typical Agile methodology, with many unknown or incremental improvements, though it will have some minor iterations/adjustments.  I need to maintain communications (or links to) within the project.

The project is somewhere between a Scrum and Kanban, in that the overall requirements are fairly fixed as in a Sprint, but requires visualisation of the workflow as in Kanban.  I'm not sure which is preferable in this scenario.  My current understanding is that creating a board is that the first step to take in managing this on Jira.  Would that definitely be right?

Regards,

Stuart

TAGS
AUG Leaders

Atlassian Community Events