Defining intent
Active time spent expressing the objective and business rules, separate from the technical investigation handled by DevSense.
Measurement methodology
Measure human effort per accepted delivery, not waiting time
The pilot identifies the work DevSense takes on and the active time that remains with your team. Percentages must compare equivalent outcomes and distinguish human involvement from execution duration.
Human activities are recorded separately
Reviewing the requirement
Active time spent reading, adjusting and approving scope. Elapsed time between creation and approval is not counted as human work.
Sandbox review and acceptance
Active time spent evaluating behavior and reviewing delivery. Opening a link or session does not by itself measure that time.
Intervention for external blockers
Time spent resolving infrastructure, network, billing or external system blockers, recorded separately so it is not hidden in results.
How to calculate a comparable reduction in effort
- 01
Define an equivalent comparison
Use the same expected outcome and quality criteria for the current workflow and the pilot.
- 02
Record active time
Agree on how to measure each human activity. Do not substitute HTTP duration, waiting time or model runtime.
- 03
Include all attempts
Include corrections, cancellations and executions without a delivery. Do not select only work that converged.
- 04
Compare accepted deliveries
Calculate human effort per delivery and express the change from the current workflow as a percentage.
Calculation rules
Every percentage needs a definition and denominator
Human effort reduction is calculated as: 100 × (1 − active human time with DevSense ÷ active human time in the reference workflow), for comparable outcomes and acceptance conditions.
Each activity’s share is calculated against total measured active human time. Development, automated review and QA duration describe platform work; they are not converted into human hours saved.
- Unit: accepted delivery, including effort from preceding attempts.
- Cohort and period defined before selecting outcomes, with technical tests identified separately.
- Results published as aggregate percentages, without customer names or requirement identifiers.
- An approval or Sandbox access timestamp confirms an event; it does not by itself measure active effort.
Evaluate savings against your own engineering workflow
Agree on the objective, involvement measurement and acceptance criteria before running the pilot.