style="font-size:15px;"> <--- Score
8. Have the customer needs been translated into specific, measurable requirements? How?
<--- Score
9. How do you build the right business case?
<--- Score
10. What scope do you want your strategy to cover?
<--- Score
11. Has a team charter been developed and communicated?
<--- Score
12. Who approved the Systems Architecture Service scope?
<--- Score
13. What is the context?
<--- Score
14. How is the team tracking and documenting its work?
<--- Score
15. What would be the goal or target for a Systems Architecture Service’s improvement team?
<--- Score
16. How do you manage unclear Systems Architecture Service requirements?
<--- Score
17. What are the rough order estimates on cost savings/opportunities that Systems Architecture Service brings?
<--- Score
18. How do you catch Systems Architecture Service definition inconsistencies?
<--- Score
19. How will the Systems Architecture Service team and the group measure complete success of Systems Architecture Service?
<--- Score
20. Are there different segments of customers?
<--- Score
21. Does the team have regular meetings?
<--- Score
22. What was the context?
<--- Score
23. What are the tasks and definitions?
<--- Score
24. Is there a clear Systems Architecture Service case definition?
<--- Score
25. Is there any additional Systems Architecture Service definition of success?
<--- Score
26. How can the value of Systems Architecture Service be defined?
<--- Score
27. Do you have a Systems Architecture Service success story or case study ready to tell and share?
<--- Score
28. Why are you doing Systems Architecture Service and what is the scope?
<--- Score
29. What are the compelling stakeholder reasons for embarking on Systems Architecture Service?
<--- Score
30. Have all of the relationships been defined properly?
<--- Score
31. What customer feedback methods were used to solicit their input?
<--- Score
32. Who is gathering information?
<--- Score
33. How will variation in the actual durations of each activity be dealt with to ensure that the expected Systems Architecture Service results are met?
<--- Score
34. How are consistent Systems Architecture Service definitions important?
<--- Score
35. How do you manage changes in Systems Architecture Service requirements?
<--- Score
36. What are the Systems Architecture Service use cases?
<--- Score
37. Has the Systems Architecture Service work been fairly and/or equitably divided and delegated among team members who are qualified and capable to perform the work? Has everyone contributed?
<--- Score
38. How do you gather Systems Architecture Service requirements?
<--- Score
39. Are accountability and ownership for Systems Architecture Service clearly defined?
<--- Score
40. Are task requirements clearly defined?
<--- Score
41. How do you gather the stories?
<--- Score
42. Where can you gather more information?
<--- Score
43. In what way can you redefine the criteria of choice clients have in your category in your favor?
<--- Score
44. How does the Systems Architecture Service manager ensure against scope creep?
<--- Score
45. What is the scope of Systems Architecture Service?
<--- Score
46. Are customer(s) identified and segmented according to their different needs and requirements?
<--- Score
47. Who defines (or who defined) the rules and roles?
<--- Score
48. What are the requirements for audit information?
<--- Score
49. Is the team equipped with available and reliable resources?
<--- Score
50. Is the current ‘as is’ process being followed? If not, what are the discrepancies?
<--- Score
51. What are the boundaries of the scope? What is in bounds and
