Information Products
Information
Product
a product
encapsulating data, code, analytics and visualisation
which delivers information within a defined boundary
enabling actions and outcomes that drive business value
Information
Product
Canvas
a pattern template
to quickly discover and capture
data and information requirements
in a repeatable way
so stakeholders love them
and data teams can build from them
Information Product
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 it in small iterations. I often articulate...
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 enables the Information Product boundaries to be...
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 a shared language. The areas can be grouped into 3...
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 added as you discover and document it. There are five...
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 in the data domain we should be aware that data...
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 should be cautious when using it. Some examples of...
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 to work best for a team when they are starting...
New Course! Capture high level data requirements
Learn how to capture requirements for an Information Product, with your stakeholders, and in 30 minutes, which your data the team can deliver in days or weeks.