In 2011, Netflix made quite a mistake with a rebranding, which could have been prevented had they communicated properly. Which brings us to our favorite issue tracking system: Jira. This tool uses custom fields, which can be customized with Awesome Custom Fields to make sure no one ever oversees any important information, improving communication.
No team can do without meaningful prioritization of its upcoming tasks and work, even if it only acts reasonably efficiently and doesn’t want to rush past the needs of customers when developing a release or project. The MoSCoW method addresses the actual importance and relevance of a feature or story to a release or project, regardless of the amount of work required.
As a rule, tasks and work need to be prioritized before they are scheduled for processing. Some less experienced teams might intuitively think that prioritizing a backlog is not a big deal: a simple discrete order seems to be a good approach. But as soon as things get a bit more complex, it fails. For larger scenarios, the WSJF method offers a proven alternative. Here is an introduction along with a way to map the WSJF in Jira.
Custom fields in Jira are a great thing: They allow individualization beyond the standard and enable adaptation to individual workflows and processes. At the same time, custom fields are quite an unwieldy topic for tech-savvy power users – but they are far too useful not to make more intensive use of the possibilities associated with them. What Jira lacks is true, intuitive management of custom fields. The app “Awesome Custom Fields” has set out to change that.