In Requirements Management for Ranger Projects … Epics, Team and Personas we introduced a more formalised requirements management process for all new Rangers projects, which were targeting Visual Studio and Team Foundation Server 2010.
In the upcoming Visual Studio 11 Readiness Content (Understanding our Visual Studio 11 Readiness conspiracy) we are reusing the personas and customer type definitions to map our out-of-band tooling and guidance with real-world scenarios. We introduced for new personas Alex, Bill, Jeff and Paul as required for the new solutions as shown in the summary illustration below:
Here is an example of a customer types used in the guidance, whereby this extract is from the Team Foundation Server Project Planning project:
Troy Research is a small application development organization that focuses on developing specialized solutions for numerous clients. Because of the volume of clients, they have to run a lean and efficient team. In addition to performing ISV work, a number of individuals from Troy Research travel to client sites to work on projects for the client, gather requirements, or perform integration work for solutions that the client has developed. Troy Research has around 100 employees with about 20 people interacting with Team Foundation Server.
How are the Personas and Customer Types used?
If we look at the Team Foundation Server Project Planning guidance document, we note the following in the overall table of content:
Comments welcome! The above is an interim snapshot of work in progress, which implies that changes can still be made.
We will be investigating the feasibility of aligning the ALM Ranger personas with the personas used by other groups, so that we can hopefully consolidate to one common set of definitions.