Best Practice: When to create a new status in JIRA

JIRA Projects WorkflowJIRA’s workflow engine provides a powerful tool for managing and monitoring the work that you and your teams are doing. By tracking the status of tasks, stories, epics, and initiatives, you can improve certainty, reduce or eliminate status update meetings, and build in automation and controls at each status transition. But when a company begins using JIRA for the first time, they sometimes make the mistake of over-complicating their workflow. You want to get fine-grained visibility into the status of work, but building a workflow with twenty or thirty statuses results in a workflow nobody wants to use. A better approach is to start with a simple workflow, and add statuses when you need them.

But how do you know when you will need a new status? I have a couple of rules that help me make workflows that people like to use, and when people enjoy using them, they’re more likely to keep the ticket updated, which means your data is more accurate and actually useful.

Continue reading

It is better to be explicit and wrong than to be vague

One of my favourite quotes from Strunk and White is, “Don’t compound ignorance with inaudibility.” While it is wise to not say anything if you’ve got nothing nice to say, at least in some circumstances, remaining silent just because you don’t know what you’re talking about benefits no one. You need to be open to correction, and if you don’t ask questions or share your views, you’ll never be able to grow.

We need to get over our fear of being wrong. If we don’t, we’ll never learn enough to be right.

Continue reading