Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

From the blog: Setup Jira & Confluence for success - The Complete series

Recommended Posts

  • Owner

I often get questions on how I think the best setup for Jira and Confluence should look when I meet organizations. Because of that I will make a series of posts about this where I setup Jira and Confluence from scratch. This will include not just how I do things, but also the thought behind it. I hope you will find this useful for setting up your own setup in Jira and Confluence.

This series will be divided into several parts. This is because adding every step in a single post would make for a very long blog post. Dividing into a series also make it easier for you to look at specific parts that is most interesting for you at the moment. The parts that I have in mind could change as I write the series, but at the moment the plan is this:

  • Part 1: Defining the tools
  • Part 2: Defining Jira Issue Types
  • Part 3: Defining Jira Issue workflows
  • Part 4: Defining Jira Screens & Custom fields
  • Part 5: Defining Jira security & access
  • Part 6: Defining Confluence Information Structure
  • Part 7: Defining Confluence Requirement Templates
  • Part 8: Defining Confluence Design Templates

With the setup completed in Jira and Confluence I will probably add a second series called "Work processes in Confluence & Jira - From Need to Deploy" where we go through how to use the setup from a practical point of view. It will be a more generic process so it can be used in any methodology with some minor tweaks. If anyone want I could also add a post about how to use the power of Jira and Confluence for programmers without ever leaving your IDE.


Is there anything you miss from this series that you feel I should add?



View full article


Link to post
Share on other sites
  • Replies 0
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Similar Content

    • By ©Jimi Wikman
      My assignment was to review and build a new work process with JIRA & Confluence as tools for the development efforts at Axfood. Based on the SAFE agile process with practical experience in making projects actually become a reality I built a process that was custom-made for Axfood and their specific challenges.
    • By ©Jimi Wikman
      Jira tool manager with the task of stabilizing the system and setting up work processes for all teams within H&M. Responsible for several projects including cloud initiatives and coordination with other systems such as ServiceNow. Heavily involved in designing the build processes (requirements, development, design, deploy and test) for the process office. Responsible for the design and implementation of SAFe in Jira and the build processes. Responsible for a small team of Atlassian experts. Supported 400+ teams with Jira questions and training of work processes.
    • By ©Jimi Wikman
      Going over requirements and making time estimations and technical solutions for the front end part of the project.
    • By ©Jimi Wikman
      I was the team lead for the front end development team doing the redesign of all H&M brands on the new Hybris platform.

      Working with H&M we needed to build a new way of working within Accenture as we had 3 companies that had never worked together before: Fjord, Brightstep and Accenture Italy. I built a completely new delivery workflow from design to frontend and then to backend in Jira and Confluence. In total I spent over 500 hours building and training the teams with great result. This was extra difficult due to the fact that we built design for 6 brands and one was under NDA and not open to Fjord for one of the projects.

      We also built a pattern library so we could work according to atomic design for both development and design. This was accompanied by a delivery pipeline to the backend team for a very smooth development process.
    • By ©Jimi Wikman
      I played around a bit with a new portfolio design this weekend.
      I kind of like it so far...


  • Create New...