Computer Systems results are met?
<--- Score
12. Are different versions of process maps needed to account for the different types of inputs?
<--- Score
13. Is the scope of Business Computer Systems defined?
<--- Score
14. Is the Business Computer Systems scope complete and appropriately sized?
<--- Score
15. What sort of initial information to gather?
<--- Score
16. What information should you gather?
<--- Score
17. Has/have the customer(s) been identified?
<--- Score
18. Who defines (or who defined) the rules and roles?
<--- Score
19. Is there a clear Business Computer Systems case definition?
<--- Score
20. What gets examined?
<--- Score
21. What are the Business Computer Systems tasks and definitions?
<--- Score
22. What defines best in class?
<--- Score
23. What are the Roles and Responsibilities for each team member and its leadership? Where is this documented?
<--- Score
24. What constraints exist that might impact the team?
<--- Score
25. How have you defined all Business Computer Systems requirements first?
<--- Score
26. Has a team charter been developed and communicated?
<--- Score
27. How often are the team meetings?
<--- Score
28. Is it clearly defined in and to your organization what you do?
<--- Score
29. What is the scope of Business Computer Systems?
<--- Score
30. How can the value of Business Computer Systems be defined?
<--- Score
31. How are consistent Business Computer Systems definitions important?
<--- Score
32. Is special Business Computer Systems user knowledge required?
<--- Score
33. What happens if Business Computer Systems’s scope changes?
<--- Score
34. Is there regularly 100% attendance at the team meetings? If not, have appointed substitutes attended to preserve cross-functionality and full representation?
<--- Score
35. What are the rough order estimates on cost savings/opportunities that Business Computer Systems brings?
<--- Score
36. What critical content must be communicated – who, what, when, where, and how?
<--- Score
37. What customer feedback methods were used to solicit their input?
<--- Score
38. What is in the scope and what is not in scope?
<--- Score
39. Who is gathering information?
<--- Score
40. How do you gather requirements?
<--- Score
41. Has a high-level ‘as is’ process map been completed, verified and validated?
<--- Score
42. How would you define the culture at your organization, how susceptible is it to Business Computer Systems changes?
<--- Score
43. Where can you gather more information?
<--- Score
44. Are the Business Computer Systems requirements complete?
<--- Score
45. What is out of scope?
<--- Score
46. Has the improvement team collected the ‘voice of the customer’ (obtained feedback – qualitative and quantitative)?
<--- Score
47. How do you keep key subject matter experts in the loop?
<--- Score
48. Is Business Computer Systems currently on schedule according to the plan?
<--- Score
49. Are task requirements clearly defined?
<--- Score
50. Have the customer needs been translated into specific, measurable requirements? How?
<--- Score
51. How would you define Business Computer Systems leadership?
<--- Score
52. What is the scope of the Business Computer Systems work?
<--- Score
53. Is there any additional Business Computer Systems definition of success?
<--- Score
54. How do you think the partners involved in Business Computer Systems would have defined success?
<--- Score
55. How is the team tracking and documenting its work?
<--- Score
56.
