Score
22. What are the core elements of the Trusted system business case?
<--- Score
23. Is the work to date meeting requirements?
<--- Score
24. Is the scope of Trusted system defined?
<--- Score
25. What is the scope of the Trusted system effort?
<--- Score
26. How do you manage unclear Trusted system requirements?
<--- Score
27. What sort of initial information to gather?
<--- Score
28. Has the Trusted system 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
29. How did the Trusted system manager receive input to the development of a Trusted system improvement plan and the estimated completion dates/times of each activity?
<--- Score
30. Is special Trusted system user knowledge required?
<--- Score
31. Are accountability and ownership for Trusted system clearly defined?
<--- Score
32. How do you think the partners involved in Trusted system would have defined success?
<--- Score
33. How do you gather Trusted system requirements?
<--- Score
34. When are meeting minutes sent out? Who is on the distribution list?
<--- Score
35. What system do you use for gathering Trusted system information?
<--- Score
36. How do you hand over Trusted system context?
<--- Score
37. How do you manage changes in Trusted system requirements?
<--- Score
38. Has the improvement team collected the ‘voice of the customer’ (obtained feedback – qualitative and quantitative)?
<--- Score
39. What are the Roles and Responsibilities for each team member and its leadership? Where is this documented?
<--- Score
40. What is the scope?
<--- Score
41. What specifically is the problem? Where does it occur? When does it occur? What is its extent?
<--- Score
42. How do you gather the stories?
<--- Score
43. What is the scope of the Trusted system work?
<--- Score
44. What would be the goal or target for a Trusted system’s improvement team?
<--- Score
45. Is the current ‘as is’ process being followed? If not, what are the discrepancies?
<--- Score
46. How would you define Trusted system leadership?
<--- Score
47. What is in the scope and what is not in scope?
<--- Score
48. Are resources adequate for the scope?
<--- Score
49. Does the scope remain the same?
<--- Score
50. Are there different segments of customers?
<--- Score
51. How do you catch Trusted system definition inconsistencies?
<--- Score
52. How is the team tracking and documenting its work?
<--- Score
53. Is the Trusted system scope manageable?
<--- Score
54. What are the record-keeping requirements of Trusted system activities?
<--- Score
55. How do you build the right business case?
<--- Score
56. Has a high-level ‘as is’ process map been completed, verified and validated?
<--- Score
57. Will a Trusted system production readiness review be required?
<--- Score
58. Are roles and responsibilities formally defined?
<--- Score
59. Who is gathering Trusted system information?
<--- Score
60. Do the problem and goal statements meet the SMART criteria (specific, measurable, attainable, relevant, and time-bound)?
<--- Score
61. Are required metrics defined, what are they?
<--- Score
62. Who is gathering information?
<--- Score
63. What customer feedback methods were used to solicit their input?
<--- Score
64. What are the Trusted system use cases?
<--- Score
65. Is the Trusted system scope complete and appropriately sized?
<--- Score
66. What knowledge or experience is required?
