Skip to main content
Sign In |
  Help (new window)

Enterprise MSF Agile (with CobiT)

Go Search
Home
  
Enterprise MSF Agile (with CobiT) > Wiki Pages > Activity - Validate a Release (Fix a Bug)  

Activity - Validate a Release (Fix a Bug)

View All Site Content

Recent Changes
Activity Information

Validate a Release

Release a ProductValidate a Release

Description

A build is ready to be validated for release when functionality, time, and quality objectives defined in the vision statement and test approach are met. Alpha and beta releases also constitute releases. The build must pass a final set of regression tests and subsequent triage to become a release. When regression tests are complete, a decision is made whether to fix bugs or designate the build as the release candidate.

Roles

PerformerRelease Manager
AssistantsTester

Attributes

CategoriesMSF Agile Principles - Foster open communications, Quality Indicators, Project, MSF Agile Principles - Empower Team Members , MSF Agile Principles - Establish Clear Accountability, MSF Agile Principles - Invest in Quality , MSF Agile Principles - Work Toward a Shared Vision , Deploy, AI7.6 Testing of Changes

Steps

  1. Create a Release Branch:
    Create a new branch for the release candidate. This isolates the code so that only selected fixes may be applied.

  2. Run Regression Test:
    Run a full regression test on the release candidate.

  3. Open a Bug:
    A test failure results in a new bug report. Assess the impact and reproduce each bug.

    Check for duplicate bugs. Attach bugs identified to the test task that generated the bugs.

    Attach the test case, test results, test configuration, and scenario or quality of service requirement to the bug report.

Predecessors

TypeNameDependency Type
Execute a Release PlanFinish-Start

Successors

TypeNameDependency Type
Create Release NotesFinish-Start

Last modified at 1/17/2008 11:18 PM  by Administrator