Requirements and Team Foundation Server


Published on

Published in: Technology, Business
  • Be the first to comment

Requirements and Team Foundation Server

  1. 1. Requirements Management
  2. 2. <ul><li>Introductions </li></ul><ul><li>Recap: Team Foundation Server </li></ul><ul><li>Requirements Management in TFS </li></ul><ul><ul><li>Document-based Approach </li></ul></ul><ul><ul><li>Item-based Approach </li></ul></ul><ul><li>Comparison: Borland CaliberRM </li></ul><ul><li>Q&A </li></ul><ul><li>Close & Next Steps </li></ul>
  3. 3. Business Analyst Operations, QA and Help Desk Third-Party IDEs Web Clients and XML Web Services
  4. 4. <ul><li>Two Approaches </li></ul><ul><ul><li>Document-based </li></ul></ul><ul><ul><li>Item-based Approach </li></ul></ul><ul><li>Many variations to both approaches </li></ul>
  5. 5. <ul><li>Leverage Team Portal site (SharePoint) for document control & approval </li></ul><ul><li>Documents accessible via portal, Team System, TFS Web Access </li></ul>
  6. 6. Benefits Drawbacks <ul><li>Analysts remain in comfort application (Word, etc.) </li></ul><ul><li>SharePoint is a &quot;natural&quot; extension in Word/Office applications </li></ul><ul><li>Requirement specs more easily consumed by other roles in lifecycle. </li></ul><ul><li>Provides basic mechanism to enable traceability and better &quot;cross-artifact&quot; reporting. </li></ul><ul><li>Lack of item-level granularity. </li></ul><ul><li>Document-level linking only (can't link to an individual requirement inside specification document) </li></ul><ul><li>Document Workflow managed by SharePoint, whereas Workflow for other lifecycle artifacts are managed by TFS. </li></ul>
  7. 7. <ul><li>Leverage Work Item Tracking in TFS </li></ul><ul><li>Increased granularity </li></ul><ul><li>Complete control over form, fields, permissions, workflow, etc. </li></ul><ul><li>Full link-support </li></ul><ul><ul><li>Work Items (other req’s, bugs, tasks, etc.) </li></ul></ul><ul><ul><li>Source </li></ul></ul><ul><ul><li>Test Results </li></ul></ul><ul><li>Accessible (Team System, TFS Web Access, Excel, etc.) </li></ul><ul><li>Detailed reporting </li></ul>
  8. 9. Benefits Drawbacks <ul><li>All changes will be recorded and audited </li></ul><ul><li>Consistency </li></ul><ul><li>Links can be created between individual requirements and other work items (any type), source code, test results, and hyperlinks) </li></ul><ul><li>Workflow is enforced and controlled in the same manner as all other work item types </li></ul><ul><li>Supporting information (screenshots, documents, UML diagrams, etc.) can be attached </li></ul><ul><li>Reporting can be much more granular (showing requirement implementation rates, impact analysis, scope creep). </li></ul><ul><li>Change of interface may meet resistance (i.e. no more Word!) </li></ul><ul><li>Customization involved </li></ul><ul><ul><li>Work item types, fields, & workflow </li></ul></ul><ul><ul><li>Reports </li></ul></ul>
  9. 10. Document-Based Item-Based Interface Any Any TFS client Repository SharePoint TFS Work Item Tracking Granularity Document Requirement Workflow SharePoint TFS Work Item Tracking Customization Some on the SharePoint Site Work Item types, fields, workflow & reports Consistency Rely on Word (or other) templates. Difficult to enforce Consistent UI, data capture via Work Item Tracking
  10. 14. <ul><li>Whitepaper: Requirements Management and Visual Studio Team System: </li></ul><ul><li>Blog Series: Requirements and TFS: </li></ul>
  11. 15. <ul><li>Questions? </li></ul>
  12. 16. © 2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.