1
Business Understanding
step 1 of 10
The project does not start with the data but with the decision it is meant to improve. We establish which business goal the project serves, how success will be measured and who will work with the outcome. Skip this phase and the model can succeed while nothing changes in the organisation.
+ · steps 2–4 of 10 · added by the IBM methodology
Analytic Approach
Which kind of analysis fits the question: predicting, explaining, detecting or optimising. In the model this step comes before data exploration, while in practice you often only know which analysis fits after a first exploration. Knowing that, you plan the loop instead of being caught out by it.
Data Requirements
What data that analysis needs: sources, format, period and quality.
Data Collection
How that data comes in, what is missing and what may not be used. If collecting reveals that the requirements are off, they are revised: the loop back to Data Requirements.
2
Data Understanding
step 5 of 10
The first confrontation with the real data: how complete, how current and how reliable is it, and does it mean what everyone assumes it means? Assumptions fail in this phase, and that is the point: better in week three than after go-live. If data turns out to be missing, the loop takes you back to Data Collection.
3
Data Preparation
step 6 of 10
Usually the largest item in the project budget: joining sources, fixing errors, building features and recording every operation so it stays reproducible. What is done well here pays off in every later phase; what is missing here you pay for later, and then the loop back to Data Collection fetches new data after all.
Only now does the modelling start. We train and compare several candidates against the measure from phase one, from simple to complex: the simplest model that answers the question wins. Modelling and preparation alternate: every intermediate result feeds back into data preparation. In our projects the model itself is rarely the risk; the phases before and after it are.
5
Evaluation
step 8 of 10
Two questions, in this order: does the solution answer the business question from phase one, and do the results hold up on data the model has not seen? This is where the decision is made: to production, back to Modeling via the return loop, or stop. Stopping is an outcome too; better here than in production.
6
Deployment
step 9 of 10
Where most data projects run aground: from working experiment to a system that runs in day-to-day operations, with monitoring, documentation and an owner. This is what Twentynext is built for: our Service & Maintenance practice keeps what we build running.
+ · step 10 of 10 · added by the IBM methodology
Feedback
After go-live the real measurement starts: is the system being used, are the predictions still right and is reality shifting under the model? The answers loop back to Modeling: adjust, redeploy, and the system does not quietly grow stale.
The order is not strict: as soon as the findings give reason to, you return to an earlier phase. What that looks like in practice is in our cases and projects.
CRISP-DM describes how we run a single data project. If you are looking for the route by which your whole organisation starts making decisions based on data, start at Data-driven working.