Delivery Manager
Keeping scope, coverage, and readiness visible so a release date means something.
Foundations
What a Delivery Manager actually tracks
Status is not progress and a percentage is not evidence. What a Delivery Manager should be tracking, and the signals that are worth escalating early.
What a Product Owner actually owns
The Product Owner decides what is worth building and in what order. Here is what that accountability really covers, and the three ways it gets diluted.
Practices
Release readiness checklist and template
A release readiness checklist with owners, evidence and stop signals, test exit criteria, UAT sign-off, and a go or no-go decision record template.
Requirement quality checklist and examples
A requirement quality checklist with before-and-after examples of ambiguous, incomplete and untestable requirements, how to find gaps, and a review decision.
Requirements change impact analysis
How to analyse the impact of a requirement change: what to trace, which tests to review, how to reassess earlier results, plus a worked example and a template.
Requirements gathering tools and checklist
Requirements gathering tools grouped by the job they do, a checklist and question bank for each stage, and a handoff template for decisions and open questions.
Requirements traceability matrix template
How to create a requirements traceability matrix step by step: what to link, planned versus executed coverage, and a free Excel RTM template with an example.
Choosing a requirements management tool
How to choose a requirements management tool: a practical checklist, demo questions, a worked refund example, and a free printable evaluation sheet.
Product
Test cases from Jira and Azure DevOps
Import Jira stories or Azure DevOps work items, generate reviewed test cases from their acceptance criteria, trace results, and push them back to the ticket.
Generating test cases from requirements
How to generate test cases from requirements, step by step: a worked refund example from acceptance criteria to linked test cases, review and approval.
Reporting coverage and traceability
How ReqLens turns pipeline evidence into reports a steering group can act on, and why end-to-end traceability is generated rather than assembled by hand.
Running a test cycle: a TestExecute guide
Why blocked is a first-class result rather than a kind of failure, what a run record needs to stay meaningful, and how execution feeds readiness.
Tracking defects across the pipeline
Defects do not only come from testing. How ReqLens tracks where a defect was found, separates severity from priority, and makes rejection reasons useful.
Workspaces, roles and permissions
Three roles, ranked rather than listed, and what each can do. How project access resolves, and why some things belong to the workspace rather than a person.