Services
Digital tooling: Jira, Confluence, and more
A Jira nobody trusts is worse than no Jira at all. I design, implement, and clean up Atlassian setups so teams and managers can use the platform for planning and see the actual status of the work, and I train the people who run them. I build the setup myself as well as advising on it.
How it usually goes wrong
- Every team has configured Jira its own way, so nothing adds up at portfolio level.
- Workflows have grown to a dozen statuses that nobody uses consistently.
- Managers ask for status in meetings because the tool can’t answer them.
- Confluence has become a graveyard of outdated pages that nobody can find.
- You pay for features (templates, automation, reporting, whiteboards) that nobody has discovered.
What I do
- Jira: standard project types, clean workflows, usage policies, and a portfolio level that adds up correctly.
- Confluence: a structure people can navigate, and the features you already pay for put to work.
- Ways of working: the tool follows the process, so I help teams agree on Kanban, estimation, Definition of Done, and prioritisation first.
- Training: for the teams, the admins, and the leaders who read the reports.
Where I’ve done this
- Danish Building and Property Agency (Bygningsstyrelsen): re-implemented Jira and Confluence as the standard task and portfolio management system for the IT and Legal departments, introduced a new approach to IT portfolio management, and trained the IT teams.
- Jira and Confluence implementations for media and online businesses, as well as in several of my release train roles.
Ways to work together
- Jira health check: a half-day review of workflows, boards, and configuration, with a prioritised fix list. See the sessions
- Confluence structure and untapped features: a two-hour review of how your space is organised and which features you already pay for could help you. See the sessions
- Implementation or clean-up: typically one to six months.