Creating and Managing Dev Items
A dev item is one feature you’re measuring. Create one, edit it, and track it through the lifecycle. Dev Items guide →
Features
VEKTIS turns feature releases into a repeatable loop: capture what “normal” looks like before you ship, mark the release, measure what happens after, then read whether the change you saw was real impact or just noise. This section walks through every step and the tools that surround it — initiatives for grouping related work, team roles for collaboration, and decision support for acting on results.
The pages below are grouped by what you’re trying to do. Most teams move through them in roughly this order on their first feature, then dip in and out as needed.
Build your measurement loop
Section titled “Build your measurement loop”Collecting Baseline Data
Establish reliable “before” measurements so the post-release comparison means something. Baseline guide →
Recording a Release
Mark the dev item as released — that’s the line in the sand for impact comparison. Release guide →
Measuring After You Ship
Collect post-release data and watch your feature’s impact accumulate over time. Post-release guide →
Read and act on results
Section titled “Read and act on results”Understanding Your Results
How VEKTIS decides whether the change you saw is real, marginal, or just normal noise. Statistical analysis guide →
Acting on Impact Results
Decision support for the three impact zones — celebrate, investigate, or keep measuring. Acting on impact →
Organize work and your team
Section titled “Organize work and your team”Organizing Work with Initiatives
Group related dev items under an initiative to track progress against a larger goal. Initiatives guide →
Inviting Your Team
Add teammates to your VEKTIS organization and pick the right role for each. User management guide →