Insights

A user story is a simple description used to understand a feature to be made, typically used in Agile work environments; the story of a user. They are meant to be told from the end user's perspective to contrive the most business value.

If you’re familiar with maturity assessments, you may have heard a few criticisms about their value and effectiveness. In Felix Kiefer's experience, what has been evident is that assessments that are owned by the team produce more value.

Aggregating a lot of data into a centralised place, cleaning and joining data from different sources when building a data warehouse looks very similar to what we do with an MDM. So what’s the difference, and when might one be enough?

A leading travel and tourism business has transformed the customer experience, addressed pressing regulatory requirements, and positioned itself to reap a data-infused competitive edge following a major data modernisation program. Replacing a struggling AWS solution with a richly featured Microsoft Azure foundation, they took an agile approach, working with Aginic to make the giant leap in just a matter of weeks.

How does an agile approach differ from a traditional way of working? This post provides a brief overview of the differences and benefits of an agile approach to delivery, illustrating and comparing four key areas (visibility, adaptability, value, and risk) with a more traditional approach.

In this first of a series of posts, I will discuss and offer up some suggestive action to some agile anti-patterns that may resonate with you, especially if you have gone through, are going through, or about to embark on an agile transformation journey.

Deciding how much time to spend on DevOps is difficult at any stage. Here are a few useful tips on how DevOps can play a role during a project's discovery sprint!

I’ve been in many situations over the years debating the value of Pair Programming, so I thought I’d share my experiences and views on the subject.