So, basically, one checkin usually links to a single work item? Dylan. ________________________________
From: [email protected] [mailto:[email protected]] On Behalf Of Mike Schimmel Sent: Thursday, 16 April 2009 1:49 PM To: [email protected] Subject: RE: Requirements gathering I'm doing this from my phone so i can't articulate all details, but you link change sets for code and unit tests to tasks and system level tests to the backlog. a.k.a. Requirement/bug/scenario/quality of service. Mike Schimmel Solution Architect Microsoft Consulting Services [email protected] (cell) 847-420-4121 (office) 312-920-5632 ________________________________ From: Dylan Tusler <[email protected]> Sent: Wednesday, April 15, 2009 8:43 PM To: [email protected] <[email protected]> Subject: RE: Requirements gathering Just a clarification, you say: We link the Task WITs to the Requirement/Scenario and associate the code checkins with the appropriate Task/Requirement/Scenario WITs for traceability to the code. By this, do you mean that you link your code checkins to ONE OF these, or to ALL OF these? (That is, link the checkin to the Task and the Scenario work items?) Dylan. ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Guger, Larry Sent: Thursday, 16 April 2009 12:58 AM To: [email protected] Subject: RE: Requirements gathering Hi Deepak, This could easily be a question that results in a short book on the topic! However I will tell you one approach that I have used to some success. First off we need to define how you scope your requirements, are they user stories? Feature sets? Do they represent hours of effort, days of effort or months of effort? Since you say that you have 100s I assume that they are closer to days or hours than anything... I will usually create a Requirement WIT (CMMI) or Scenario WIT (Agile) for each user story level requirement, these are things like "Add new user". I will keep a short description of the requirement in the WIT but then create a word document that has the full details (use case, field descriptions, persona usage examples, etc) and store that in the project SharePoint site and create a link in the WIT to the word document. I usually take a Scrum approach and the Requirements/Scenario WITs make up my product backlog and the tasks required to develop the Requirement/Scenario are Task WITs and are my sprint backlog. This way I have traceability from the WIT to the Word document via the link. We link the Task WITs to the Requirement/Scenario and associate the code checkins with the appropriate Task/Requirement/Scenario WITs for traceability to the code. I hope that helps. Cheers, Larry Guger From: [email protected] [mailto:[email protected]] On Behalf Of Deepak Srinivasan Sent: Wednesday, April 15, 2009 7:39 AM To: [email protected] Subject: Requirements gathering Hello What would you recommend to gather rquirements (process/tools) in a TFS environment. How granular does one get for using Requirements WIT (incase of 100s of requirements). I understand that it can be reduced if we plan the iteration properly. But, what I would be very interested in is how do I track my requirement all the way to the code. Any insights/ideas would be great. Thanks Deepak ________________________________ Support procedure: https://www.codify.com/lists/support List address: [email protected] <mailto:[email protected]> Subscribe: [email protected] <mailto:[email protected]> Unsubscribe: [email protected] <mailto:[email protected]> List FAQ: http://www.codify.com/lists/oztfs <http://www.codify.com/lists/oztfs> Other lists you might want to join: http://www.codify.com/lists <http://www.codify.com/lists> ________________________________ Support procedure: https://www.codify.com/lists/support List address: [email protected] <mailto:[email protected]> Subscribe: [email protected] <mailto:[email protected]> Unsubscribe: [email protected] <mailto:[email protected]> List FAQ: http://www.codify.com/lists/oztfs <http://www.codify.com/lists/oztfs> Other lists you might want to join: http://www.codify.com/lists <http://www.codify.com/lists> ************************************************************************ ****************** To find out more about the Sunshine Coast Council, visit your local council office at Caloundra, Maroochydore, Nambour or Tewantin. Or, if you prefer, visit us on line at www.sunshinecoast.qld.gov.au This email, together with any attachments, is intended for the named recipient(s) only. Any form of review, disclosure, modification, distribution and or publication of this email message is prohibited without the express permission of the author. Please notify the sender immediately if you have received this e-mail by mistake and delete it from your system. Unless otherwise stated, this email represents only the views of the sender and not the views of the Sunshine Coast Regional Council. ************************************************************************ ******************* mail5.2.13 ________________________________ Support procedure: https://www.codify.com/lists/support List address: [email protected] <mailto:[email protected]> Subscribe: [email protected] <mailto:[email protected]> Unsubscribe: [email protected] <mailto:[email protected]> List FAQ: http://www.codify.com/lists/oztfs <http://www.codify.com/lists/oztfs> Other lists you might want to join: http://www.codify.com/lists <http://www.codify.com/lists> ________________________________ Support procedure: https://www.codify.com/lists/support List address: [email protected] <mailto:[email protected]> Subscribe: [email protected] <mailto:[email protected]> Unsubscribe: [email protected] <mailto:[email protected]> List FAQ: http://www.codify.com/lists/oztfs <http://www.codify.com/lists/oztfs> Other lists you might want to join: http://www.codify.com/lists <http://www.codify.com/lists> -------------------------------------------------------------------------------- Support procedure: https://www.codify.com/lists/support List address: [email protected] Subscribe: [email protected] Unsubscribe: [email protected] List FAQ: http://www.codify.com/lists/oztfs Other lists you might want to join: http://www.codify.com/lists
