Collaboration, sharing, discussions, documents, knowledge, wiki, intranet. These are some of the keywords people use when talking about Confluence. Confluence started out as a wiki-like system but it goes a lot further than that these days. We’ve seen it (or installed it ourselves) in many different forms, like (social) intranets, public websites, knowledge bases or just a place to store documents. With Confluence it is easy to create content, to share it, to find it and to breathe life into it. Besides that, it’s easy to customize or extend Confluence and it’s openness allows you to do just about anything you like with it.
Atlassian Summit was a while ago already. It was during the event that I presented a way to implement the Scaled Agile Framework in JIRA. The full video of my talk can be found in the Atlassian Summit archives.
During my Summit talk, I discussed three enterprise challenges when scaling Agile; process and documentation culture, underestimation of planning effort and managing a complicated infrastructure. There certainly is a lot to say on all three topics!
In this blog post, I would like to dive a bit deeper into the planning effort when scaling agile and how to track progress by using Atlassian JIRA. Continue reading →
I am currently working on an application that has very high test coverage, which usually means applying changes is a safe and relatively easy task. Still, I felt that I was losing a disproportional amount of time fixing unit tests that failed after a change. We all know frustration is one of the best drivers of improvement; when I was facing another round of unit test fixing I created a more future proof solution instead.
Yesterday, December 3rd, Atlassian released Confluence 5.4. The main highlight of this new minor release is better integration with JIRA and JIRA Agile. JIRA, in combination with JIRA Agile and Confluence, now offers you full traceability of your Scrum process.
At Avisi, I have been working with JIRA since 2007. We are using JIRA for many different processes, like sales, marketing, financial control, etc. As a developer I am used to work, think and track issues in projects. But when you want to track a business process in JIRA, the term project all of a sudden becomes a problem. Continue reading →
Some software development teams are so perfectly balanced that more work comes out than the sum of the work of the individual members. It’s a team of skilled experts, that get the most out of themselves and bring out the best in others. If you are invited to join such a team, expect to feel pain. The pain of trying to keep up with the pace of the team. The pain of others trying to push you to heights you did not reach before. The pain of raising the bar for yourselves.
If you manage to hang in there though, the pain becomes gain. You learn, you get better at everything and the team becomes even better, just because of you.
In the systems integration field we often encounter systems that more or less frustrate the integration process. An example is a system that sends confusing messages or messages that clearly violate interface definitions. Requests to the owner of that system to fix those messages might result in improvements that work out better for everyone, but are often ignored and you will just have to deal with it. What are the options? Continue reading →
It happens a lot, you get interrupted by questions from fellow colleagues by chat, by email or just them walking by. It’s normal honestly, you have answers and they need to know. But what if you could share your answers with the rest of the organization? Here is where Confluence Questions comes in. Answers to your questions, behind the firewall (probably on OnDemand soon too).