Phase 02 · Define
Requirement feasibility check
How it works
Once requirements get concrete in Define: every single requirement is checked against the API, schema and test surface of the codebase – what the code does not support cheaply becomes visible before anything is built. The difference to the Impact & Feasibility Matrix: there whole initiatives are scored for the portfolio; here the feasibility check happens per requirement.
- Checks feasibility against the API, schema and test surface
- Links every requirement to the code it touches
- Records the verdict per requirement as a short feasibility note
Roles
Head of product & engineering
Teklens apps & integrations
Teklens.aiJira
Example prompts & actions
Copy one of the following prompts and paste it into the Teklens chat. Adapt the details to your use case.
Check the feasibility of requirement [Q] against the code.
Related use cases
Three use cases closely connected to this one.
Prioritisation by impact and feasibility.Prioritises features by business impact × technical feasibility – grounded in the real code instead of gut feeling.View use case A roadmap anchored in Jira and code.Connects strategic priorities with Jira, dependencies and real engineering reality – and flags it when the two drift apart.View use case Spec → epic with code contextTurns a spec into a build-ready epic with acceptance criteria from real code paths.View use case
From the PM Lab
Articles that explore this use case in depth.
Give Teklens a real job.
Connect Jira and your code – and let Teklens work on something real.