Visual Studio ALM … stepping through Brian’s HOLs and creating a DRAFT checklist (Part 1)

We have gone through a wave of guidance around Visual Studio 2010 earlier this year and wrapping up two more exciting guidance projects. You can either spot and click on the relevant link above ^^^ next to Latest Rangers Solutions or keeping an eye on the summary post VSTS Ranger Projects – summary of projects covered on this blog.

One of the questions that comes up again and again is “is there a quick reference poster that illustrates the basic steps I need explore as part of the ALM journey?”. The answer, from a Rangers guidance perspective is unfortunately no, but we are working on the idea. In fact, this blog is the first step of the journey, walking through Brian Keller’s Hands-on-Labs (HOL) and Rangers HOLs. We would appreciate your feedback and comments to this blog and the journey notes, so that we can mix all of the feedback and our findings to create a high-level step-by-step quick reference poster.

The table summarises the high level areas of focus, the content we are reviewing and the “suggested” steps within each area of focus.

Focus Area Reference Material Suggested steps for the quick reference poster
Define Business Requirements
  1. Rangers TFS Requirements Management Guidance addresses the People, Process, and Technology guidance for Requirements Engineering (RE) using Team Foundation Server.
  2. The Architecture Guidance takes a look at using the Visual Studio Modelling Tools in the design and exploration environments.
  3. The Quick Reference Guidance has some quick reference posters, such as the Scrum Guide below, which includes some quick templates for visions and user stories.
Project Planning
  1. Manage backlog of product work items using the Product Planning workbook. 
    1. Refresh workbook
    2. Plan new iteration using “Iterations” work tab. 
    3. Assign story tasks to the new iteration using the “Product Backlog” tab.
    4. Publish
  2. Manage iteration, using the Iteration ? backlog workbook.
    1. Refresh workbook
    2. Refine (add, assign) tasks to user stories in tab “Iteration Backlog”
    3. Define iteration details (dates) on “Iterations” tab
    4. Manage members under “Capacity” tab
    5. Publish
  3. Make use of Sample Documents, for which you will find both templates and sample documents.







Next time, in part 2, we will explore Code Discovery.

Comments (0)

Skip to main content