What is the worst case scenario?
<--- Score
6. Has a team charter been developed and communicated?
<--- Score
7. The political context: who holds power?
<--- Score
8. Has anyone else (internal or external to the group) attempted to solve this problem or a similar one before? If so, what knowledge can be leveraged from these previous efforts?
<--- Score
9. Is Architecture design software linked to key stakeholder goals and objectives?
<--- Score
10. Are there different segments of customers?
<--- Score
11. What is out-of-scope initially?
<--- Score
12. What are the record-keeping requirements of Architecture design software activities?
<--- Score
13. How will variation in the actual durations of each activity be dealt with to ensure that the expected Architecture design software results are met?
<--- Score
14. What customer feedback methods were used to solicit their input?
<--- Score
15. Is Architecture design software currently on schedule according to the plan?
<--- Score
16. Are all requirements met?
<--- Score
17. What are the boundaries of the scope? What is in bounds and what is not? What is the start point? What is the stop point?
<--- Score
18. How do you gather Architecture design software requirements?
<--- Score
19. Are required metrics defined, what are they?
<--- Score
20. Is there a clear Architecture design software case definition?
<--- Score
21. What specifically is the problem? Where does it occur? When does it occur? What is its extent?
<--- Score
22. What gets examined?
<--- Score
23. What are (control) requirements for Architecture design software Information?
<--- Score
24. Has everyone on the team, including the team leaders, been properly trained?
<--- Score
25. What system do you use for gathering Architecture design software information?
<--- Score
26. What are the tasks and definitions?
<--- Score
27. What defines best in class?
<--- Score
28. Is the current ‘as is’ process being followed? If not, what are the discrepancies?
<--- Score
29. Is Architecture design software required?
<--- Score
30. Has the improvement team collected the ‘voice of the customer’ (obtained feedback – qualitative and quantitative)?
<--- Score
31. Are the Architecture design software requirements testable?
<--- Score
32. What is the definition of Architecture design software excellence?
<--- Score
33. What are the rough order estimates on cost savings/opportunities that Architecture design software brings?
<--- Score
34. Will team members perform Architecture design software work when assigned and in a timely fashion?
<--- Score
35. Is there a completed, verified, and validated high-level ‘as is’ (not ‘should be’ or ‘could be’) stakeholder process map?
<--- Score
36. Are the Architecture design software requirements complete?
<--- Score
37. Is there a Architecture design software management charter, including stakeholder case, problem and goal statements, scope, milestones, roles and responsibilities, communication plan?
<--- Score
38. What scope do you want your strategy to cover?
<--- Score
39. Is it clearly defined in and to your organization what you do?
<--- Score
40. Does the team have regular meetings?
<--- Score
41. Is data collected and displayed to better understand customer(s) critical needs and requirements.
<--- Score
42. What are the dynamics of the communication plan?
<--- Score
43. What sources do you use to gather information for a Architecture design software study?
<--- Score
44. What is in scope?
<--- Score
45. What knowledge or experience is required?
<--- Score
46. What baselines are required to be defined and managed?
<--- Score
47. Have all of the relationships been defined properly?
<--- Score
48.
