AgileData Way of Working
An agile way of working leverages widely used agile approaches to describe good practices and processes for recurring team problems using a common language
Conceptual approaches from the agile world can be applied in concrete use cases regardless of the agile “methodology” used. Reusable approaches are useful because they:
- represent proven solutions to common problems;
- organise solutions into a standard and easily referenced format;
- can be adopted and implemented by most practitioners who work in the data and analytics domain;
- can be used to ensure consistency in how teams work together;
- provide a shared language for specific problems and potential solutions.
We have taken the approaches and patterns we have adopted or crafted with our customers over the last 10 years and are articulating them using a book pattern.
We are taking an agile approach to writing the book content and so are publishing the content early and as we develop it. You should expect the content structure to constantly change over time.
We welcome early and constant feedback as all agilist’s should.
When asking an agile practitioner, expert or coach for a one sentence answer to “what is agile” you will often get the response “agile is a mindset”. When you ask the follow on question of “what is an agile mindset”, more often than not you will get an answer that is along the lines of “it is hard to explain but you will know it when you see it”
Building a self organising team is one of the key factors required to crafting your own AgileData Way of Working. Creating a team with T-Skills, adopting agile patterns and helping the team through the process of forming, storming and norming is a massive challenge.
Big design and requirements upfront results in a lot of unused work and waste. AgileData Design helps us gather reqiurements and design thinsg in smaller chunks.
An Information Product is an approach to describe a subset of data, analytical and visualisation requirements in a way that the business stakeholders can agree what they will get and the team can understand and deliver it in small iterations.
Data is typically complex, and we need a proven set of patterns to help manage this complexity. Data patterns are often adapted from other domains, such as product and software engineering.
As well as building an AgileData team and your own AgileData Way of Working you also need to build an AgileData Platform, there are a bunch of patterns that can make that process easier.
When there is more than “just a team” and you need collaboration and co-ordination outside of one team.
Content we haven’t quite found the right place to live, yet.
Have an agile data approach to share
Get in touch and help us publish more useful patterns