MSF Agile: cannot close scenarios

Hot Topic

Warehouse not updating after upgrading to RC
Reports in Team Explorer : 403 error
Unit tests for methods that return NotImplementedException
Start Date and Finish Date
How to set version information in a builded exe file
UpdateBuildNumberDropLocation and "Attempted to perform an unauthorized operation"
a "pre-sales" question of sorts about source control in TFS
Add user fails to add user to Portal and Reports
Can someone please explain Team System to me
Beta2: Cannot create a Team Project

VS Team System

Webtest
Types not checked if they have the GeneratedCodeAttribute.
Assembly.GetEntryAssembly() Returns Nothing when running from a Unit Test
Data driven Load testing
Web Testing using Anthem (ajax)
Mapping Project field to custom field in Work Item
Unit Test Adapter threw TypeInitializationException
Web Test Recorder : Can you turn off the replacement of hidden fields by context parameter placeholders?
Samples data for Team Foundation
Headache converting from NUnit

MSF Agile: cannot close scenarios

Hi,
    In the Process Guidance for MSF Agile v100.1, in the workstream "Create a Scenario", activity "Prioritize Scenario List", sub-activity "Determine an Overall Priority" it says:
  • Close the low priority scenarios that will be implemented in a future release using the deferred reason code.
    But in the Process Template, there is no transition from "Active" to "Closed" state for scenarios. So I cannot close it! The only transition available from "Active" is to "Resolved" but in the description of the "Resolved" state in the Guidance it says that the scenario has to be implemented in code. Thus I cannot set the scenario I want to postpone for a future release as "Resolved" neither.

    What should I do Am I missing something

Thanks!

PD: By the way, in the MSF Agile Guidance v100.1 - "Create a Scenario" workstream, activity "Develop Lifestyle Snapshot" the link to the top level workstream points to "Create a Quality of Service Requirement" workstream. Shouldn't it point to "Create a Scenario" workstream



Answer this question

MSF Agile: cannot close scenarios

  • rchrismor013

    Yes, unfortunately that's the only way to close them. We need a direct transition from active to closed, I know. We will have one in a future release.

    Randy

    MSF



  • Jim Evans

    As suggest in default process a scenario can only have following state transitions-
    Active to Resolved
    Resolved to Active
    Resolved to Close
    Close to Active.

    One has to follow set of above mentioned states in order to close a scenario.In default process there is not transition from "Active" to "Close" directly.You may ofcourse customize it by modifying process templates and/or state transition rules.

    Moreover "Resolve" state does not really say that a scenario has to be implemented in current iteration."Deferring" a scenario means that we may implement it in code but not in current iteration.
  • MSF Agile: cannot close scenarios
Answer this question