Score
60. Are different versions of process maps needed to account for the different types of inputs?
<--- Score
61. How do you keep key subject matter experts in the loop?
<--- Score
62. Is the On-demand software scope complete and appropriately sized?
<--- Score
63. What is out-of-scope initially?
<--- Score
64. What is the scope of the On-demand software work?
<--- Score
65. Are all requirements met?
<--- Score
66. Is there any additional On-demand software definition of success?
<--- Score
67. What is a worst-case scenario for losses?
<--- Score
68. Has a high-level ‘as is’ process map been completed, verified and validated?
<--- Score
69. Are required metrics defined, what are they?
<--- Score
70. 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
71. Have all of the relationships been defined properly?
<--- Score
72. How do you gather On-demand software requirements?
<--- Score
73. Does the team have regular meetings?
<--- Score
74. Is scope creep really all bad news?
<--- Score
75. What would be the goal or target for a On-demand software’s improvement team?
<--- Score
76. How do you hand over On-demand software context?
<--- Score
77. What are the tasks and definitions?
<--- Score
78. Are accountability and ownership for On-demand software clearly defined?
<--- Score
79. How do you gather the stories?
<--- Score
80. What key stakeholder process output measure(s) does On-demand software leverage and how?
<--- Score
81. What defines best in class?
<--- Score
82. What sources do you use to gather information for a On-demand software study?
<--- Score
83. How are consistent On-demand software definitions important?
<--- Score
84. What scope do you want your strategy to cover?
<--- Score
85. Has a team charter been developed and communicated?
<--- Score
86. Scope of sensitive information?
<--- Score
87. Is the team adequately staffed with the desired cross-functionality? If not, what additional resources are available to the team?
<--- Score
88. Who is gathering On-demand software information?
<--- Score
89. Has anyone else (internal or external to the group) attempted to solve this problem or a similar one before? If so, what knowledge can be leveraged from these previous efforts?
<--- Score
90. Is the team equipped with available and reliable resources?
<--- Score
91. Who defines (or who defined) the rules and roles?
<--- Score
92. What are the Roles and Responsibilities for each team member and its leadership? Where is this documented?
<--- Score
93. How was the ‘as is’ process map developed, reviewed, verified and validated?
<--- Score
94. When is/was the On-demand software start date?
<--- Score
95. How do you gather requirements?
<--- Score
96. How can the value of On-demand software be defined?
<--- Score
97. Is special On-demand software user knowledge required?
<--- Score
98. Who approved the On-demand software scope?
<--- Score
99. Has the On-demand software 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
100. What are the compelling stakeholder reasons for embarking on On-demand software?
<--- Score
101. Are roles and responsibilities formally defined?
<--- Score
102. Has everyone on the team, including the team leaders, been properly trained?
<--- Score
103. Do you have organizational privacy requirements?
<--- Score
104. How do you catch
