---
title: 12 Follow-up: one proof of concept in three sprints
---

# 12 Follow-up: one proof of concept in three sprints

The concept is not built from scratch. Three capabilities that exist or are in preparation are unified into one initial proof of concept. The requirements profile extraction is Sprint 2 deliverable 1.2 and extends the Ontology Store; the existing CV extraction becomes the CV-assisted background step; and the assessment concept of this report – evidence profile, scorecard, methods, staging – is the model the two extractions are mapped to.

In the second week of Sprint 2 the concept is separated into work streams by capability and, per stream, the requirements (inputs, outputs and contracts between extraction, Ontology Store and scorecard), the goals (which reviewer feedback and customer-case outcomes the first version addresses) and the validation strategy (how the prototype is evaluated in Sprint 4: vacancies, populations, comparison against the current flow, bias indicators) are defined.

Sprint 3 builds the unified proof of concept, one flow from vacancy to evidence profile. Sprint 4 evaluates the prototype on real vacancies against the current flow.

![Figure 29 – One proof of concept from three existing capabilities; the goal of the second sprint week.](../media/image29.png)

*Figure 29 – One proof of concept from three existing capabilities; the goal of the second sprint week.*

![Figure 30 – Three sprints – define, build, evaluate – with the work streams by capability (concept presentation, slide 39).](../media/image30.png)

*Figure 30 – Three sprints – define, build, evaluate – with the work streams by capability (concept presentation, slide 39).*

| **Work stream**                 | **Sprint 2 · week two (define)**                                | **Sprint 3 (build)**                      | **Sprint 4 (evaluate)**                                     |
|---------------------------------|-----------------------------------------------------------------|-------------------------------------------|-------------------------------------------------------------|
| Work streams & requirements     | Streams by capability; requirements, goals, validation strategy | –                                         | –                                                           |
| Ontology Store extension        | Requirements profiles (1.2) → evidence profile                  | Build                                     | –                                                           |
| Requirements profile extraction | Mapped to the unified profile                                   | Build                                     | –                                                           |
| CV extraction → background step | Reuse plan                                                      | Build                                     | –                                                           |
| Scorecard & evidence profile    | Evidence claims, scoring guides, one profile                    | Build                                     | –                                                           |
| Unified proof of concept        | –                                                               | One flow from vacancy to evidence profile | –                                                           |
| Evaluation of the prototype     | Validation strategy                                             | –                                         | Real vacancies, current flow as comparison, bias indicators |

*Table 5 – The three-sprint plan by work stream.*

Seven work streams carry the plan: work streams and requirements (define); the Ontology Store extension from requirements profiles to the evidence profile (define, build); the requirements profile extraction mapped to the unified profile; the CV extraction as background step; the scorecard and evidence profile; the unified proof of concept (build); and the evaluation of the prototype (evaluate). Owners per stream are assigned in the sprint planning.