There are a number of problems that come with the use of the fixed mindset prioritisation...
Design Articles
AgileData prioritisation patterns
There are a number of prioritisation patterns we have found in the agile and product domains which...
Levels of Prioritisation
When looking at the AgileData patterns for prioritisation you can see they are all based on...
Concept of an Information Product
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...
Information Product Canvas and Brief
The Information Product Canvas and the Information Product Brief are templates we use to document and share the definition of an Information Product. They are designed to provide a common and shared language which...
Information Product Canvas Areas
The information Product Canvas is divided into 11 areas, each is designed to articulate a subset of the information requirements in a way that we can quickly capture these requirements and we can articulate them using...
When to create or iterate a Information Product canvas
Like a lot of artefacts you create and update as part of your AgileData WOW, the Information Product canvas and brief is updated multiple times as you progress through the delivery process. Each time more detail is...
Information Products relationship to data and code
One of the questions about Information Products I get asked a lot, is what is the relationship between an Information Product and the data or the code it relies on? DORO — Define Once, Reuse Often When we start working...
Information Product Anti-Patterns
An anti-pattern is a common response to a problem that looks like a great idea but usually ends up making things worse. An anti-pattern doesn't mean it will also fail, but it does mean it is higher risk and so you...
Information Product FAQ
Does an Information Product have to be delivered in a single iteration? No. If you are using a time box pattern for your iterations, aka a Scrum centric approach, I have found that three week time-boxed iterations seem...