Team Focus

Typically before a team is formed, a few core individuals go through the early stages of working with project sponsor(s) to quantify the problem or opportunity and establish an initial vision for a solution. As more information is learned and the effort seems worthy of pursuing, other key individuals join the team to refine the vision while constricting it into an achievable project scope. As the initial solution concept(s) becomes clearer, additional resources are solicited to help further refine project goals, assumptions, risks, and constraints. The team starts to form initial high-level requirements and puts forth a few options and approaches to implementing a solution.

At this point, all advocacy groups should be represented on the team. The team is starting to work through defining detailed roles and responsibilities for the team as well as identifying any skills gaps that would necessitate bringing on additional people or that might justify replacing existing team members. Overall roles and responsibilities for the team during an Envision Track are described in Table 7-1.

Table 7-1. Team Focal Areas During Envisioning

Advocacy	Group Focus
Product Management	Overall goals, identify customer needs, requirements, vision/scope definition, customer acceptance criteria
Program Management	Project structure, project constraints, constraint trade-offs
Architecture	Design goals and strategies, solution concept, feasibility analysis, build and technology options
Development	Build needs and strategies
User Experience	User performance needs and implications, user acceptance criteria
Test	Testing strategies, approach, and metrics
Release/Operations	Deployment implications, operations management and supportability, operations acceptance criteria, qualities of service