54. What are the compelling stakeholder reasons for embarking on Web data services?
<--- Score
55. Are roles and responsibilities formally defined?
<--- Score
56. Will a Web data services production readiness review be required?
<--- Score
57. What are the record-keeping requirements of Web data services activities?
<--- Score
58. Has the direction changed at all during the course of Web data services? If so, when did it change and why?
<--- Score
59. What are the Roles and Responsibilities for each team member and its leadership? Where is this documented?
<--- Score
60. What is in the scope and what is not in scope?
<--- Score
61. What are the dynamics of the communication plan?
<--- Score
62. What scope do you want your strategy to cover?
<--- Score
63. Do you have a Web data services success story or case study ready to tell and share?
<--- Score
64. How often are the team meetings?
<--- Score
65. What information do you gather?
<--- Score
66. In what way can you redefine the criteria of choice clients have in your category in your favor?
<--- Score
67. Where can you gather more information?
<--- Score
68. How do you gather Web data services requirements?
<--- Score
69. Is the scope of Web data services defined?
<--- Score
70. Is scope creep really all bad news?
<--- Score
71. What is the scope of Web data services?
<--- Score
72. What are (control) requirements for Web data services Information?
<--- Score
73. What is the scope of the Web data services work?
<--- Score
74. What is the context?
<--- Score
75. What happens if Web data services’s scope changes?
<--- Score
76. Are different versions of process maps needed to account for the different types of inputs?
<--- Score
77. How do you manage scope?
<--- Score
78. What system do you use for gathering Web data services information?
<--- Score
79. Is the Web data services scope manageable?
<--- Score
80. Are required metrics defined, what are they?
<--- Score
81. Is data collected and displayed to better understand customer(s) critical needs and requirements.
<--- Score
82. How do you gather requirements?
<--- Score
83. How does the Web data services manager ensure against scope creep?
<--- Score
84. How is the team tracking and documenting its work?
<--- Score
85. Are the Web data services requirements complete?
<--- Score
86. What are the Web data services tasks and definitions?
<--- Score
87. What knowledge or experience is required?
<--- Score
88. Is there a Web data services management charter, including stakeholder case, problem and goal statements, scope, milestones, roles and responsibilities, communication plan?
<--- Score
89. 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
90. Is Web data services required?
<--- Score
91. If substitutes have been appointed, have they been briefed on the Web data services goals and received regular communications as to the progress to date?
<--- Score
92. How and when will the baselines be defined?
<--- Score
93. Does the team have regular meetings?
<--- Score
94. What is the definition of success?
<--- Score
95. Scope of sensitive information?
<--- Score
96. Are there different segments of customers?
<--- Score
97. When are meeting minutes sent out? Who is on the distribution list?
<--- Score
98. Is the team adequately staffed with the desired cross-functionality? If not, what additional resources are available to the team?
<--- Score
