none
CMMI Risk Management

    Question

  • The 'MSF for CMMI Process Improvement' process template includes both a template Word document called "RiskCategoriesandSources.dot" and a work item of type Risk.

    It is my understanding, that one should determine risk sources and categories (as stated in RSKM SP 1.1) and fill the corresponding document before creating work items of type Risk.

    The thing that bugs me is that there are no fields for Source or Category on the Risk work item. So, are the contents in RiskCategoriesandSources.doc used when creating work items of type Risk? How?

    We've been tinkering with the possibility of customizing the process template to include fields for Source and Category on the Risk WIT, but I don't want to do that unless I really have to.

    The 'official' book on CMMI doesn't help that much and I haven't been able to find 'concrete' examples of RSKM goals and practices being implemented in TFS.


    Alfred Myers | MVP Visual Developer - Visual C# | http://alfredmyers.spaces.live.com | http://twitter.com/AlfredMyers

    Friday, April 13, 2012 8:59 PM

Answers

  • Just to let you guys know that we decided to:

    1. Use the taxonomy from Taxonomy-Based Risk Identification (SEI) as a basis for categorization of our risks.
    2. Replicate the taxonomy's three-part structure  (class, element and atribute) in categorizing Risk workitems.
    3. Put the taxonomy structure under a single node called 'Risks' in the Area field.

    Why didn't we go the rout of adding an extra field?

    1. We wanted a pre-populated 'list' of valid options
    2. That 'list' should be editable by specified team members
    3. It should hierarchical

    A TreePath type field would meet all those three requirements, but unfortunately TFS does not allow for the creation of fields of this type beyond the pre-existing ones (Iteration and Area Path)

    HTH

    PS.: It would be really nice if TFS allowed us to add new fields of type TreePath when customizing our WITs.


    Alfred Myers http://alfredmyersjr.wordpress.com | http://twitter.com/AlfredMyers

    • Marked as answer by Alfred Myers Thursday, April 26, 2012 9:06 PM
    Thursday, April 26, 2012 9:06 PM

All replies

  • I would add the Category field to the Risk WIT. In my experience, sooner or later you want to categorize your risks.


    Jesper Fernström
    QWise Software engineering – refactored!

    Monday, April 16, 2012 6:00 AM
  • Thanks Jesper for your reply.

    Creating a Category field is one of the alternatives we are analyzing.

    Do you guys use the RiskCategoriesandSources.dot Word template that is part of the process template?

    Do you guys guarantee somehow that the Category field in the Risk work item is filled exclusively with values from the Categories list in RiskCategoriesandSources.dot?


    Alfred Myers http://alfredmyersjr.wordpress.com | http://twitter.com/AlfredMyers

    Thursday, April 19, 2012 6:12 PM
  • Hi Alfred, 

    Thanks for your post. 

    Yes, the RiskCategoriesandSources.dotx is part of the CMMI process template.

    As far as I know, we can’t fill the Category field value from the Categories list(in RiskCategoriesandSources.dotx) directly. You can custom the Category field to add that Categories list(in RiskCategoriesandSources.dotx) as the default values for Category field.  


    John Qiao [MSFT]
    MSDN Community Support | Feedback to us

    Friday, April 20, 2012 6:26 AM
  • Just to let you guys know that we decided to:

    1. Use the taxonomy from Taxonomy-Based Risk Identification (SEI) as a basis for categorization of our risks.
    2. Replicate the taxonomy's three-part structure  (class, element and atribute) in categorizing Risk workitems.
    3. Put the taxonomy structure under a single node called 'Risks' in the Area field.

    Why didn't we go the rout of adding an extra field?

    1. We wanted a pre-populated 'list' of valid options
    2. That 'list' should be editable by specified team members
    3. It should hierarchical

    A TreePath type field would meet all those three requirements, but unfortunately TFS does not allow for the creation of fields of this type beyond the pre-existing ones (Iteration and Area Path)

    HTH

    PS.: It would be really nice if TFS allowed us to add new fields of type TreePath when customizing our WITs.


    Alfred Myers http://alfredmyersjr.wordpress.com | http://twitter.com/AlfredMyers

    • Marked as answer by Alfred Myers Thursday, April 26, 2012 9:06 PM
    Thursday, April 26, 2012 9:06 PM