57. Are roles and responsibilities formally defined?
<--- Score
58. How do you manage changes in Community Information Systems requirements?
<--- Score
59. What gets examined?
<--- Score
60. What are the core elements of the Community Information Systems business case?
<--- Score
61. What is the scope of the Community Information Systems effort?
<--- Score
62. How will variation in the actual durations of each activity be dealt with to ensure that the expected Community Information Systems results are met?
<--- Score
63. Are resources adequate for the scope?
<--- Score
64. How have you defined all Community Information Systems requirements first?
<--- Score
65. What would be the goal or target for a Community Information Systems’s improvement team?
<--- Score
66. Do the problem and goal statements meet the SMART criteria (specific, measurable, attainable, relevant, and time-bound)?
<--- Score
67. What sources do you use to gather information for a Community Information Systems study?
<--- Score
68. What intelligence can you gather?
<--- Score
69. What scope do you want your strategy to cover?
<--- Score
70. Is there a critical path to deliver Community Information Systems results?
<--- Score
71. What are the tasks and definitions?
<--- Score
72. When is the estimated completion date?
<--- Score
73. Do you have organizational privacy requirements?
<--- Score
74. Does the team have regular meetings?
<--- Score
75. Is there regularly 100% attendance at the team meetings? If not, have appointed substitutes attended to preserve cross-functionality and full representation?
<--- Score
76. What are the requirements for audit information?
<--- Score
77. Is there any additional Community Information Systems definition of success?
<--- Score
78. What is out-of-scope initially?
<--- Score
79. What scope to assess?
<--- Score
80. What specifically is the problem? Where does it occur? When does it occur? What is its extent?
<--- Score
81. Will team members regularly document their Community Information Systems work?
<--- Score
82. In what way can you redefine the criteria of choice clients have in your category in your favor?
<--- Score
83. Are customer(s) identified and segmented according to their different needs and requirements?
<--- Score
84. 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
85. Are there any constraints known that bear on the ability to perform Community Information Systems work? How is the team addressing them?
<--- Score
86. What are the compelling stakeholder reasons for embarking on Community Information Systems?
<--- Score
87. What is in scope?
<--- Score
88. How can the value of Community Information Systems be defined?
<--- Score
89. How often are the team meetings?
<--- Score
90. Is data collected and displayed to better understand customer(s) critical needs and requirements.
<--- Score
91. How do you gather requirements?
<--- Score
92. Scope of sensitive information?
<--- Score
93. What are the rough order estimates on cost savings/opportunities that Community Information Systems brings?
<--- Score
94. How would you define Community Information Systems leadership?
<--- Score
95. Is there a clear Community Information Systems case definition?
<--- Score
96. What are the dynamics of the communication plan?
<--- Score
97. What defines best in class?
<--- Score
98. What happens if Community Information Systems’s scope changes?
<--- Score
99. Are different versions of process maps needed to account for the different types of inputs?
<--- Score
100. Are all requirements met?
<---
