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


    Jira Tool Process och Method expert

    Jimi is an experienced project manager with a rather unique range of kills. He is a certified requirements manager, trained designer with special expertise in conversion optimization, experienced system, integration and acceptance testers and has 20+ years of experience in front end development…

    Project Summary

    Industry: Retail

    Job Title(s): Atlassian Expert

    Assignment: 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.

    Technique/Method: Jira, Workshops, Sharepoint, Powerpoint, Agile, ITIL, IT4IT, SAFe, Waterfall, RUP

    Customer Value: Establish a common work process so that all teams can work together in a way that is practically feasible. Create a strategic design for Jira that works and opens up for collaboration and communication instead of silo work. Educate and work with the teams to increase the understanding of Jira as a tool for improving efficiency and job satisfaction.

    My Thoughts

    My assignment at H&M is to act as a process and method expert for Jira. This means that I support and train between 5,000 and 10,000 people at Jira. I also participate in process and method forums where Jira is part of the processes and methods to be defined.

    A large part of my time is spent meeting and training the different teams. I also sit as a tool manager and holistic consultant for the major initiative that will guide working methods in the future. I am also responsible for making extensive changes to Jira and represent other Atlassian products such as Confluence.

    My Responsibility areas

    Strategic level

    • Hold meetings with customers about orders on the system to ensure that the right things are ordered
    • Educate H&M in using Jira. Both in person and through ordered training (through the Method Office).
    • Evaluate, recommend and / or approve new plugins to improve efficiency etc.
    • Design and implement workflows and information flows in Jira based on customer needs and H & M's stated strategies
    • Represent JIRA in all method / decision forums where that representation is relevant.
    • Define strategies for using Jira (security / field / statuses / flows / mm)
    • Create and lead the Jira Task Force (System forum for using Jira)

    Operational level

    • Manage system-critical requests
      • New fields
      • New workflows
      • New issue types
      • New plugins
      • New integrations
      • New hardware
    • Develop manuals for how different work is to be performed (new fields, values, workflows, triggers, etc.)
    • Evaluate and order work for stabilization and safety
    • Hold meetings with customers about orders on the system to ensure that the right things are ordered (Available in both areas)
    • Lead, educate and manage evaluation projects
    • Be responsible for evaluating and implementing upgrades (from a customer perspective).



    • Like 1

    User Feedback

    Recommended Comments

    There are no comments to display.

    Join the conversation

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

    Add a comment...

    ×   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
      Agile fail consistently in larger organizations. There are many reasons for it and here are my takes on why Agile currently fail very often:
      Agile is an operational model. Its origin is in the operations part of the organization and its design is on the operation part. By that I mean it has little to no tools for the steering part of an organization. This means that it clashes hard with the strategic aspects of companies as it lack input on portfolio management, change management that leads to projects and business requirements. It has no tools for resource management, external workforce collaboration and so on. This makes it one dimensional and more often than not very much at odds with the steering processes.
        Agile lack boundary overlap aspects. Agile is designed around a single work team that is assumed to have autonomy control over a system or product. This is rarely true in large organizations where teams are part of larger organizations or even split between multiple systems and products. Collaboration is defined within the team, but there are no collaboration over team or project boundaries. This cause friction and bastardizations is made to cope.
        Agile is for extroverts. Without defined roles and with no real guidelines for how to work with requirements and design aspects Agile is poorly suited to Introverts. For Agile to work you need a constant communication to be flowing and you need most of the team. This is highly disruptive and the content switching will take a heavy toll on the introvert team members and of course anyone who need to be able to focus to do their work. The focus on information flow rather than clarity and structure is often not a popular work environment for many developers.
        Agile is often turned into Ad-Hoc. Without proper flows from steering and no formal requirement process Agile often become an ad hoc experience where what to do change constantly. This cause a stressful and damaging environment for the team and it has been the cause of many people getting burnt out or leaving for other work conditions.
        Agile is turned into Waterfall with stand up. When Agile fail because of the above you usually end up in a situation where you have a Waterfall methodology dictated by the steering process (usually ITIL based) so you end up with a sequential workflow with stand-ups. In best case you might get sprints as well, but that is pretty much it.
        For Agile to succeed it need to recognize that there are always two processes in place: The Steering and The Operational. You either need to ensure the touchpoint between then work, or make sure that the Agile model works for both. SAFe is an option, but it is not Agile and quite honestly you can just as well have ITIL on top if you like because both are just steering and control processes.
    • By ©Jimi Wikman
      My assignment was to make a new design for the web based user area based on the graphical profile from one of ChessIT's clients. The design had to be light in terms of changes as the project had hard deadlines. I worked with the client and the developers to find a balance between the two that satisfied the requirements and respected the time constraints.
    • 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
      Going over requirements and making time estimations and technical solutions for the front end part of the project.
    • By ©Jimi Wikman
      Me and Mauro was tasked to go over the requirements to ensure they were properly understood and defined. The original requirements were loosely defined and as we went over them with Stadium we could identify the need properly and match it towards technical solutions. This ensured the need was possible to implement and that we could find and manage requirements that not yet been expressed.
  • Create New...