Document workflow on TFS?

hello,

 

we implementing tfs and there methodology describing processes have follow during development of new features. initial work done on top of several word docs (vision document, use cases, test cases , on). create kind of workflow :

1. the requirements guy creates use cases doc;

2. the quality guy has review , approve use cases.

    2a. if approved, architect starts turning use cases taks developers;

    2b. if not, requirements guy receives "why not approved" doc , goes 1;

3. development guy picks 1 task , codes it;

... , etc.

 

since tfs has source code control feature, thought storing docs on tfs scc, not see how implement workflow control if docs on scc. perhaps i'm not using tfs right? better workflow on team project portal tfs creates? there drawbacks on storing docs on sharepoint instead of tfs scc? have guys experience on scenario this?

 

thanks lot,

 

gb

the short answer tfs currently, whether use scc or wss, doesn't provide full solution. me, full solution includes:

• workflow
• web access
• traceability (link doc work item)
• branching/labeling
• querying

i our direction use wss handle documents tfs-based projects, , continue enhance integration full solution. now, branching/labeling, you'd have handle manually wss, is, copy files new document library create "branch"

 

having said that, believe there strong case scc, if whoever writing requirements doesn't have aversion working visual studio / tfs / source control. many of our customers requirements anaylsts won't go near vs. :-)

 

i realize not definite answer, provide more information.

 

- gregg

Archived Forums V  >  Team Foundation Server - General