The five rules when we work with Jira and why what's not written down never happened.
Jira is our primary tool for tracking and managing all projects. We have developed the following rules:
Why do you need to break down tasks into smaller pieces and then combine them into epics? The answer is simple. The smaller the task, the easier it is to finish them. Small tasks increase the chances to find bugs and to uncover issues. The massive task loses the complexity illusion once it is broken down into smaller, understandable pieces.
When we have a complex task in mind instead of finish it — we screw everything up by always overthinking it. We can help ourselves by writing down our thoughts. The main benefits of it:
It is up to you to decide how small subtasks to make and to tackle. Jira is your personal instrument, and you should use it to fit your needs.
The most efficient way to break down tasks is to do it with the project manager and the stakeholder. It allows us to gather all the necessary information to estimate the scope of work accurately.
Writing comments might seem like a waste of time when you already write work logs. Yet comments are the critical tool for the transparent team’s communication. Writing comments pursue four goals:
Once again, the comment section is your personal tool. Though you still need to keep in mind that your comments should also be understandable to your teammates. They help you see the whole work process so that you can decide what to try and what not to.
If comments reflect our task solving process, Worklogs reflect the RESULT we’ve achieved in a given time. If you’ve been researching, then you should describe the result of your research and attach some materials if needed. We always write down our work progress in a work log, even if the ticket is not yet closed.
Remember, the work log and the commits are proof of your work in a project. It is your insurance in case of misunderstandings or questions from the client regarding the time you’ve spent. The absence of work logs means that there is no evidence of what has been done and achieved.
If you forget to log work, you can create it with a backdate. But if your manager sees it, you owe him/her a cookie/beer/bbq/chocolate or whatever they choose.
Need more experience in Jira? Discover how we’ve integrated Jira Automation to Project Managers’, HR’s, QCD’s repeated processes:
Sprint planning is a vast topic that requires its own article, but let’s briefly cover the process here. Regarding the tasks in Jira, all of the tasks must be closed before the end of the sprint. It is possible to ask the manager to move the task to another sprint, but this must be done as soon as possible.
Additionally, all the tasks created during the given sprint must be included in that sprint (often tasks are being created after the start of the sprint and often get omitted from the final work report).
Optimal frequency: once every 1 to 3 hours. Comments should be added on the basis, “The more, the better.” You need this to understand in time that you’ve dug up a hole for yourself but haven’t realized yet.
Just remember. What’s not written is wasted.
You open another office because your company is growing. Some people move there, and you are proud that the company gets bigger. But it makes you...
People bring a human factor to company regulations and standards. We forget tasks while creating to-do lists and waste time by fixing the crappy...
Project start in most of the cases seems so brightful and carefree — the team is involved, the customer is excited to work, the deadlines are far...