Direkt zum Hauptinhalt

Project Phase & Milestone Tracking

Clients often ask how they can measure the number of iterations (back‑and‑forth review rounds) made to a survey link link—from the moment the initial link is shared until final sign‑off.
SurveyTester provides a flexible and structured way to track these stagesiterations using Milestones / Phases, which allowenabling teams to measure time, effort, and iteration counts across the entire project lifecycle.

How to useUse Milestones and relatedRelated featuresFeatures to trackTrack testingTesting phases, issue cycles,Phases and iterationIterations
progress?

You can track each phase of the testing process by creating Milestones that represent each round of changeschanges, reviews, or reviewquality cycles.
checks.
Milestones allow you to monitor:

  • HowThe manytotal number of testing rounds occurredcompleted
  • When each round started and ended
  • HowThe manynumber of issues belongedlogged toin each iteration
  • HowThe longduration of each milestone took
  • Which issues were resolved before movingprogressing to the next phase

Once you create multiple milestones,milestones are created, SurveyTester gives youprovides several views and tools to analyze project iterations.

progress
and iteration effort.
How1. toCreating TrackMilestones Iterations/ Phases Using MilestonesIssue Status

1. Create Milestones for Each Round

Milestones can be createdused basedto on:

structure
workflow phases such as:
  • Each round of testing (e.g., Round 1, Round 2, Final QC, Sign‑off,off)
    • etc.)
  • Internal process stages (e.g., Ready for QC, Script Update Needed)
    image.png
Filtering issues by these statuses adds an additional layer of visibility into testing progress.
Custom milestones can also be created for:
  • Significant project events (e.g., Initial Link,Link Shared, Major Script Update, Final Review)
  • Team processes (Ready for QC, Script Update Needed)

image.png

You canshould add a new Milestone whenever:

  • A major script or link update is pushedreleased
  • A roundtesting ofor feedback round is completed
  • The project moves tointo thea nextnew phase

This creates a clear historical timeline of testing iterations.activity. However, manually created milestones cannot be used for tracking phase iteration counts.
2. Insights → Project Phase
The Insights section provides automatic analytics for each phase, including:
  • Duration per phase
  • Workload per testing round
  • Counts of issues, comments, and resolutions
  • Performance comparisons across milestones

image.png


This is the primary tool for calculating iteration effort.

2.Important: WhatManually Youcreated Willmilestones Seedo Afternot Creatinggenerate a new Phase for phase counting. A new Phase (along with its round‑based analytics) is created only when Milestones are added using the Issues → Project Phase drop‑down list.
Combined with start and end timestamps, milestones create a clear and auditable record of project effort.
How to Track Iterations Using Milestones

image.png

Once milestones are created, SurveyTester populates multiple features automatically:

a. Filter Issues by Milestone:Milestone
You can filter
Filtering issues by milestone allows you to seeview:
-

  • Total issues raised during each iteration
  • Issues resolved within each round
  • Items that require follow‑up
image.png

  • Total issues raised in each iteration
  • How many were resolved
  • Which require follow-up

This helps quantify the effort per iteration.

testing

cycle.

b. View Issues Grouped by Milestone:Milestone
SurveyTester visually separatesgroups issues by milestonemilestone, somaking youit caneasy easilyto seesee:
-

  • Issue volume per testing phase
  • Quality improvements from early testing to final sign‑off
  • Which rounds required the most effort
image.png

  • Number of issues per testing cycle
  • The progression of quality from early rounds to final sign‑off
  • Which rounds were most effort-heavy

c. ExportingExport Screenshots by Milestone:Milestone
When exporting screenshots, you can choose -

image.png

choose:
  • All screenshots infrom the project
  • Screenshots forassociated with a specific milestone only

d. Insights → Project Phase: The Insights section provides automatic analytics for each Milestone, such as -

image.pngimage.png

  • Duration per phase
  • Workload per round
  • Counts of issues, comments, resolutions
  • Performance comparisons across milestones

This is the closest tool for calculating iteration effort.

Please note that manually creating a Milestone will not create a new Phase for phase counting. A new Phase (and its corresponding phase round information) is generated only when Milestones are created using the Issues / Project Phase drop-down list, as shown in the image below.

e. Creating Phases Using Issue Statuses

In addition to milestones, you can structure workflow phases using:

  • Ready for QC
  • Script Update Needed

    image.png

Filtering issues by these statuses provides another layer of visibility into testing progress.

  1. Create Milestone: Initial Link Shared
  2. Team tests → issues are logged
  3. Developer updates script
  4. Create Milestone: Ready for QC - Round 1
  5. Test again → new issues added
  6. Developer fixes remaining issues
  7. Create Milestone: Ready for QC - Round 2
  8. Continue until final sign‑off
  9. Create Milestone: Final Sign‑off

In the end, the total number of milestones = total number of iterations. Combined with timestamps, this gives you a clear record of project effort.

Benefits of Using Milestones for Iteration Tracking

✅ UnderstandTrack the total number of revision rounds
✅ CalculateMeasure testing time per iteration
✅ Show clearDemonstrate progress and quality improvements
✅ Provide transparency to clients orand vendors
✅ MakeSimplify audits and post‑project reviews easier
✅ CreateMaintain ana organizedstructured testtesting history

Summary

Survey Tester

SurveyTester does not directlyautomatically label iterationsiterations. automatically, butHowever, Milestones provide a powerful and structured way to track every testing phase, measure time and effort, and count the fulltotal number of iteration cycles.

By consistently creating milestones for each testtesting round or build update, teams gain complete visibility visibility—from the initial survey link through to final sign‑off.

nach oben