TestAndAcceptTestAndAccept

Create Version

Creating a version locks in a snapshot of your Statement of Work at a specific point in time. This enables formal approval processes and ensures tests are run against a stable baseline.

Quick Steps

  1. Navigate to your Statement of Work
  2. Click Create Version
  3. Add version details:
    • Version Name: e.g., "v1.0", "Initial Release", "Q1 2024"
    • Description: Summary of what's included in this version
    • Release Notes: Key changes from previous version (if applicable)
  4. Click Publish Version
Creating a version

Why Version?

Versioning provides several critical benefits:

  • Baseline for Testing: Tests run against a specific, unchanging version
  • Formal Approvals: Stakeholders approve a specific version, not a moving target
  • Change Tracking: Clear record of what changed between versions
  • Rollback Capability: Return to previous versions if needed
  • Audit Trail: Complete history for compliance and governance

Version States

Draft

  • Initial state when created
  • Can still be modified
  • Not visible to approvers

Published

  • Locked and immutable
  • Visible to all team members
  • Ready for approval and testing

Approved

  • Has received all required approvals
  • Ready for implementation
  • Serves as the contract baseline

Approval Process

Once a version is published:

  1. Notifications Sent: All approvers receive email notifications
  2. Review Period: Approvers review the complete SOW
  3. Feedback: Comments and questions can be added
  4. Approval/Rejection: Each approver votes
  5. Status Update: Version marked as approved when all approve

Version Comparison

Test & Accept provides powerful version comparison tools:

  • Side-by-side View: See what changed between versions
  • Highlighted Differences: Added, modified, and deleted items
  • Change Summary: Overview of all modifications
  • Impact Analysis: Understand how changes affect tests

Best Practices

  • Meaningful Names: Use clear version identifiers (v1.0, v2.0, etc.)
  • Comprehensive Notes: Document what's included and what changed
  • Regular Versions: Create versions at logical milestones
  • Review Before Publishing: Ensure all content is complete and accurate
  • Communicate Changes: Notify team members of significant updates

What's Next?

With a published version, you're ready to run Tests to verify all criterion are satisfied.

Was this page helpful?