Kanban boards are a great tool to help keep your processes streamlined and organized. If you’re using Confluence, you can now add Kanban boards to your wiki pages with the power of the new Properties Board View. Read on to find out more.
The larger the company, the harder it gets to see where you are in the grand scheme of things. The best tool to see this is an org chart. And luckily, Properties’ latest update adds just that.
During the Apollo 11 mission in July 1969, an error message occured. And when things go wrong in such a high-stakes mission, they can go horribly wrong. Astronauts wouldn’t be able to come back to Earth. But thanks to the fact that the ground crew had checklists to work through when the error flashed up, they knew exactly what to do. And that’s why checklists are so important. They make sure you don’t forget anything when the stakes are high.
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.
In every company, countless activities take place day in and day out that have already been processed many times in this or a similar form. And yet, in the same companies, many things go wrong. That’s why teams work with checklists. They explain how routine processes work. They map standardized processes that have been thought through beforehand so that they can subsequently be processed as efficiently and seamlessly as possible. But not all checklists are the same. And not all checklist tools are equal.
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.
We can probably all agree that it’s nice to cross things off a list, so in today’s article, we give you 10 use cases for situations at work where a checklist would not go amiss. Especially if you use Jira and Confluence already.
If you’ve been using Jira Cloud for a while, you may know that it often happens that a Jira issue is marked “Done” when it’s not actually done yet. Maybe someone forgot something, or just didn’t realize there was still more to do, but from their point of view, it was done. Let us introduce a sure-fire way of never forgetting anything anymore: Checklists for Jira!
RPG fans and those who want to become one, watch out: Here we go! The unexpected journey of four disparate heroines and heroes starts in the offices of a company somewhere in the USA… Dive into the world of role-playing games, follow a team of four normal people (at least in the beginning) and get suggestions and tips from the draw.io team about diagrams, whiteboards and the best “Lord of the Rings” meme ever!
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.