Module 2: Building a team of Microsoft Solutions Architecture
1) Module profile
Team model for Microsoft Solutions Architecture
Microsoft solution architecture role group
Team adjustment for improving project efficiency
A adjustment plan for project management
2) Team model of Microsoft Solutions Architecture
I. Typical features with challenge projects
Typical characteristics with challenge projects
Target of relevant successful projects
"The project is postponed, the budget is exceeded"
Submit product within project constraints
"Build is not what we need"
Products are built according to specifications
"This thing is unpredictable, we don't care about new problems."
Just know the problem and expressed
"We can't let it run in our environment"
Smooth deployment and prepare for the upcoming operation
"It's too difficult"
Improve user use efficiency
"It can't reach our expectations, we are not happy"
Let customers be satisfied
"The information you need is not shared in time."
Establish a good communication environment
II.
Microsoft Solution Team Model
Program Manager / Developer / Tester / Release Manager / User Experience / Product Manager
III. Other project participants --- External role
Project sponsor
client
end user
Operation: The organization responsible for the normal operation after the solution is submitted
IV. Application to Team Model in Microsoft Solution Architecture
Take a common idea for struggle
Focus on business value
Keep keen, expect changes
Authorized to team members
Cultivate open communication environment
Establishing responsibility, sharing responsibility
V. Key concepts and proof practices
Key concept:
l Partition members equality
l Concept of customer focus
l concept
l Zero error concept
l Willing to learn
Proven practice
l Use small, interdisciplinary teams
l Make the team work together in a place
l Create a solution design through the participation of all team members
