Jira: A Product management tracker

Namrata Khisa
Aug 27, 2017 · 4 min read

In pathao, the process we follow for product management and development is we make stories, we design, we push code and we deploy — the so called art of agile methodology. Jira, the handy tools for scrum project management keeps all tasks noted and organized gives a framework for all working process. As we are new, this process has been introduced not a long ago but hereby not taking much time to get along with. Jira is another way called a platform to define task for tracking which is especially tailored for scrum project management and sprint planning. As an user, i have managed to put some pros and cons of jira.

Pros:

  1. A configurable set up

In jira it is easy to define stage of different issue or task under separate column or segments. Jira usually have five stages in the issue lifecycle open issue, in progress, in review, resolved issue and closed issue. The columns are configurable in to various strata of tasks which depends on the scrum process or project demand. i.e some team divide process into several stages, some may work in only a few column. A column can also be considered as one’s individual list of tasks, such as QA or testing column can certainly be pre configured for QA engineers and peer review is for tech team lead or senior engineer for evaluation. Anyone can actively or passively select assignee of tasks. Once a task is done it is pulled to the next column respectively.

2. Tool for project management

To handle a project in organized manner there is an option of selecting type of issue following the nature of the task such as user story, bug, tech, subtask, epic etc under selective project. An estimated time of within how many days the task can be resolved can be set. There is also an way to select the priority of the task into medium, high, low so for a scrum master it is easy to expedite from a ton of tickets. This is where most of the process of planning, development and integration and delivery can be driven uninterruptedly.

3. A bug tracker

Jira was presumed to be developed as a bug tracker at its initial phase. Which profoundly helps to grow startups and small companies to coordinate a gradual technical improvements.

4. Release and version management

Jira enables to organize way of maintaining all release processes. A release version can be created and all the assigned task which are done within a sprint can be pushed under that version. It helps to schedule and organize releases.

5. Interactive

Any update of task can be written as a comment, once a comment is made the assignee is notified by e-mail. So commenting on ticket is also one easy way can considered communicative and interactive. From my side, I was missing a chat feature here, may be jira could think of having this in future.

Cons:

  1. Modification in ticket not traceable

There is always a bottlenecks for every services, sometimes due to repeated changes in the ticket, assignee can’t prompt to identify the main modification. In that case I usually try finding a notification pointer for each tickets if any changes done.

2. Much ado in writing

Jira is not a complete user friendly tools for me because this is partly following a lot use of notation in writing of the description, which can easily be done in normal text writing format i believe. It also doesn’t save any task automatically while writing especially when it suddenly goes offline, you have to write whole user story from the very beginning.

3. Less efficient for big project

More stakeholders become involved in the project than just the engineers. It becomes more a whiteboard of all project meeting than a project management tracker.

4. Exposed to risk and failures

Sometimes, It is contemplated as kind of threat to the big companies who prefer the quality first. Being too much exposed of complex product development phase may goes against the whole project coherently when it comes accounting the articulation. Companies may become ungenerous of shutting down projects seeing complex workflow.

Finally, some tips for writing user story in Jira, In a big team with many developers it is mandatory to write a story as precisely and concisely as possible. The shorter the description, the lesser time take to read and concentrate. If possible, it is good to attach the file of design or a shareable link of doc or ppt file. Tag all accountable person and comment on any modification done. The pros and cons may vary and depends on how each individual team handling it according to their working process. But this is undoubtedly one effective way of project management that many teams can thoroughly rely on.

Moving Bangladesh