Do you have a Internet of Services success story or case study ready to tell and share?
<--- Score
57. What is the scope of Internet of Services?
<--- Score
58. How do you manage changes in Internet of Services requirements?
<--- Score
59. What customer feedback methods were used to solicit their input?
<--- Score
60. Is the Internet of Services scope complete and appropriately sized?
<--- Score
61. Are the Internet of Services requirements testable?
<--- Score
62. Has the direction changed at all during the course of Internet of Services? If so, when did it change and why?
<--- Score
63. Is there regularly 100% attendance at the team meetings? If not, have appointed substitutes attended to preserve cross-functionality and full representation?
<--- Score
64. How would you define the culture at your organization, how susceptible is it to Internet of Services changes?
<--- Score
65. What would be the goal or target for a Internet of Services’s improvement team?
<--- Score
66. Are roles and responsibilities formally defined?
<--- Score
67. What is in the scope and what is not in scope?
<--- Score
68. Is the improvement team aware of the different versions of a process: what they think it is vs. what it actually is vs. what it should be vs. what it could be?
<--- Score
69. Have the customer needs been translated into specific, measurable requirements? How?
<--- Score
70. What gets examined?
<--- Score
71. Is Internet of Services required?
<--- Score
72. Do you all define Internet of Services in the same way?
<--- Score
73. Is it clearly defined in and to your organization what you do?
<--- Score
74. What happens if Internet of Services’s scope changes?
<--- Score
75. Has a team charter been developed and communicated?
<--- Score
76. How does the Internet of Services manager ensure against scope creep?
<--- Score
77. How do you think the partners involved in Internet of Services would have defined success?
<--- Score
78. Is the team equipped with available and reliable resources?
<--- Score
79. What is a worst-case scenario for losses?
<--- Score
80. What are the rough order estimates on cost savings/opportunities that Internet of Services brings?
<--- Score
81. Has/have the customer(s) been identified?
<--- Score
82. Is the current ‘as is’ process being followed? If not, what are the discrepancies?
<--- Score
83. Are audit criteria, scope, frequency and methods defined?
<--- Score
84. What information should you gather?
<--- Score
85. What specifically is the problem? Where does it occur? When does it occur? What is its extent?
<--- Score
86. What is the definition of success?
<--- Score
87. What are the requirements for audit information?
<--- Score
88. What are the dynamics of the communication plan?
<--- Score
89. How do you gather the stories?
<--- Score
90. What are the Internet of Services use cases?
<--- Score
91. How is the team tracking and documenting its work?
<--- Score
92. Are approval levels defined for contracts and supplements to contracts?
<--- Score
93. How and when will the baselines be defined?
<--- Score
94. Has everyone on the team, including the team leaders, been properly trained?
<--- Score
95. Is there a completed, verified, and validated high-level ‘as is’ (not ‘should be’ or ‘could be’) stakeholder process map?
<--- Score
96. Is scope creep really all bad news?
<--- Score
97. Will a Internet of Services production readiness review be required?
<--- Score
98. Why are you doing Internet of Services and what is the scope?
<--- Score
99. What constraints exist that might impact the team?
<--- Score
100.
