Latest readiness adventure Part 3 … embracing and upgrading recent solutions
Following on to the Visual Studio ALM Rangers recently called it a daunting but exciting adventure … what’s coming? post, we introduce four known and fairly recent solutions that will be upgraded as part of this readiness wave. What is exciting is that three of the four are lead by Visual Studio ALM MVPs … now that is “raw” passion for the technology 
----------------------------------------------------------------------------------
Build Customization Guidance
Context
Practical and scenario based guidance for the use and customization of Team Foundation Build.
Codename: African Tawny Eagle (ATE)
… “Rosie” from https://birdsofprey.co.za/
Proposed Epics
- Epic: As Abu, the build master, I would like to understand the changes and impact of the next version of Visual Studio on my builds
- Epic: As Abu, the build master, I would like guidance on using Team Foundation Build with non-Microsoft environments
- Epic: As Abu, the build master, I would like all feedback and suggestions from the community on v1 addressed
Project Lead
--------------------------------------------------------------------------------
BRDLite Reference Template(s)
Context
Reference templates for the Build Customization Guidance.
Codename: African Tawny Eagle (ATE)
Proposed Epics
- Epic: As Abu, the build master, I would like to understand the changes and impact of the next version of Visual Studio on BRDLite
- Epic: As Abu, the build master, I would like to guidance on extending the BRDLite reference template with new custom activities
- Epic: As Abu, the build master, I would like a number of BRDLite reference templates, which implement scenario based custom activities.
Project Lead
--------------------------------------------------------------------------------
Visual Studio Lab Management Guidance
Context
Provide practical and scenario-based guidance for Visual Studio Lab Management, backed by VM Factory automation.
Codename: African Hawk Eagle (AHE)
… “Nicola”, from https://birdsofprey.co.za/
Proposed Epics
- Epic: As Dave, the Team Foundation Administrator, I would like to understand the changes and impact of the next version of Visual Studio on Lab Management
- Epic: As Dave, the Team Foundation Administrator, I would like all feedback and suggestions from the community on v1 addressed
Project Lead
---------------------------------------------------------------------------------
Visual Studio Architecture Tooling Guidance
Context
Practical and scenario based guidance for the Visual Studio Architecture tooling.
Codename: African Black Eagle (ABE)
Proposed Epics
- Epic: As Alex, the technology consultant, I would like to understand the impact of the next version of Visual Studio on the Visual Studio ALM architecture tooling
- Epic: As Garry, the dev lead, I would like to use the architecture tooling to design my Windows Phone solution
- Epic: As Garry, the dev lead, I would like practical guidance on how to customize DGML graphs
- Epic: As Garry, the dev lead, I would like to exchange UML diagrams created with Visual Studio with other vendor tooling
- Epic: As Garry, the dev lead, I would like to use DSLs for generate program code, configuration files, and other artefacts
Project Lead
-------------------------------------------------------------------
Have you noticed…
Have you noticed that we are removing version numbering in the solution names? It is a suggestion to create longer-living and version-agnostic, but version-aware guidance.
What do you think? Good idea?