"Data before instinct"
Product ownership under constraint: 315 hours to rebuild a piece of software
Framing, prioritizing and validating a B2B software rebuild to secure time-to-market, when development time is the scarcest resource in the company.
When your development resource is counted in hours rather than in teams, prioritization stops being a comfortable exercise. Rebuilding Markprint meant six months of calendar time for 315 hours of developer availability, roughly the equivalent of two months full time. Under those conditions, every badly framed task costs proportionally far more than it would in a properly staffed team, and method matters more than velocity.
Director of Operations - Creative Manager
Product development (physical and digital)
Case study available on request
The content of this case study isn't public: it is accessible through an application link, or on request.
Get in touchRelated projects
