Milestones
Start with the delivery period
MS-1 plans the FieldDesk pilot for September 21–October 2. Issue progress and QA progress are separate signals.
Organize delivery into stages
Organize delivery stages by period. Open and closed browsers separate current work from completed stages.
Review what belongs to the period and what still needs attention.
More views
Closed milestones: no completed stages in FieldDesk yet.
Review the milestone in context
Open the milestone detail view to inspect its period and available information about associated work. Use that context to guide the next investigation instead of relying on a date alone.
Progress, open issues, and verification evidence answer different questions. A completed piece of work does not automatically establish that its behavior has passed testing.
More views
Pilot scope: completed, in-progress, and new issues.
ISS-1 connects the pilot milestone to warranty change CR-1.
Maintain the delivery period
Create a milestone, update its period when plans change, and close it when the team completes that stage. Reopen it when further work needs to be managed in the same delivery context.
The milestone lifecycle records how the team organizes delivery. Closing a milestone is not an automatic quality certification.
More views
Edit the pilot start and due dates.
