Avisi provides Agile coaching and one of the tools that we use is our Agile Maturity Check. This is an elaborate model which looks at a lot of different aspects in your organization to determine how Agile you are and where you can improve.
This model is based on 3 key improvement area’s. If you focus on improving these, the other aspects more or less automatically follow.
Faster feedback – How fast can I get real customer feedback on my working product?
Blast radius reduction – If I break something here, how much of my product also stops working?
Predictability – When can you deliver on your promise?
In future posts we will dive deeper into these topics and show you how you can improve them.
Soms kan het voorkomen dat er, als gevolg van hooggespannen verwachtingen of veranderende marktomstandigheden, noodzaak ontstaat om eens kritisch te kijken naar de staat van een softwareproduct. Het is dan raadzaam om analytisch en objectief te kijken naar zaken als de codekwaliteit, kwaliteit van de architectuur, schaalbaarheid of het softwareontwikkelproces. Continue reading →
Recently I was invited to join a discussion forum to discuss the relationship between architecture and an agile software development process. During the talk with the person that invited me, we talked about what to expect. Then he mentioned students asking the question how architecture and agile relate and he spoke the phrase: “In theory they don’t. They are really a different philosophy.” That triggered a thought train in my head that kept me thinking for some days. Because is it really a different philosophy? In my opinion it is a different craftsmanship.
Our core business is software development and we’re good at it. We know our job and are proud of our work. Our customers say we are professionals and we agree. We listen to our customers, we build what they need and appreciate their feedback on a regular basis.
JIRA is used within a great number of teams as an agile issue tracking tool. In bigger companies different scrum teams will use the same tool to manage the company backlog. Program or project management often set up a corporate backlog of issues from which tasks are distributed across the different teams.
But teams are not an entity in Jira. So how should you go about distributing tasks between your different teams in JIRA? This post describes several solutions to that problem that we use ourselves and have seen in the field.
That said, we are very much interested in your solutions, so let us know what they are in the comments below!
Within JIRA Agile you’re able to create KanBan or Scrum boards. These boards allow you to get a better overview of your tickets. What most people don’t know, is what you’re able to do with the card colors…
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 →
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.
Today was the big day for Atlassian Summit 2013 with the opening keynote where all the big announcements were made. Co-founders and co-ceo’s Scott Farquhar and Mike Cannon-Brookes traditionally open the summit and this year they had yet again cool stuff to announce. Here is a brief overview of the all new things announced. More in-depth analysis of all the new stuff is coming over the next couple of days.
As an Atlassian experts, we are often asked to help teams implement their development process in the Atlassian tools. Often, there are many questions in the area of Applications Lifecycle Management (ALM). This inspired us to invite a few of the bigger Dutch companies to discuss the topic further.
In line with our Agile Software Architecture Symposium, we value knowledge sharing. We felt that discussing the subject with a small group of experts and users would benefit all the parties involved.
The group was made up of 6 large companies that are currently in the process of implementing Agile Applications Lifecycle Management and 6 consultants that work in the area of ALM.