Score
57. Are approval levels defined for contracts and supplements to contracts?
<--- Score
58. Has everyone on the team, including the team leaders, been properly trained?
<--- Score
59. What is the definition of success?
<--- Score
60. Are required metrics defined, what are they?
<--- Score
61. Has a team charter been developed and communicated?
<--- Score
62. Have specific policy objectives been defined?
<--- Score
63. Have the customer needs been translated into specific, measurable requirements? How?
<--- Score
64. Is there regularly 100% attendance at the team meetings? If not, have appointed substitutes attended to preserve cross-functionality and full representation?
<--- Score
65. How would you define Self service software leadership?
<--- Score
66. Is the scope of Self service software defined?
<--- Score
67. How do you gather Self service software requirements?
<--- Score
68. Where can you gather more information?
<--- Score
69. Does the scope remain the same?
<--- Score
70. What sources do you use to gather information for a Self service software study?
<--- Score
71. What baselines are required to be defined and managed?
<--- Score
72. How do you manage unclear Self service software requirements?
<--- Score
73. Is there a critical path to deliver Self service software results?
<--- Score
74. How do you gather requirements?
<--- Score
75. What specifically is the problem? Where does it occur? When does it occur? What is its extent?
<--- Score
76. How is the team tracking and documenting its work?
<--- Score
77. Is the work to date meeting requirements?
<--- Score
78. Is Self service software required?
<--- Score
79. Who is gathering information?
<--- Score
80. Who approved the Self service software scope?
<--- Score
81. What information should you gather?
<--- Score
82. When is/was the Self service software start date?
<--- Score
83. Who defines (or who defined) the rules and roles?
<--- Score
84. Have all basic functions of Self service software been defined?
<--- Score
85. What are (control) requirements for Self service software Information?
<--- Score
86. What system do you use for gathering Self service software information?
<--- Score
87. How do you hand over Self service software context?
<--- Score
88. How does the Self service software manager ensure against scope creep?
<--- Score
89. What Self service software requirements should be gathered?
<--- Score
90. What are the compelling stakeholder reasons for embarking on Self service software?
<--- Score
91. What critical content must be communicated – who, what, when, where, and how?
<--- Score
92. What is the definition of Self service software excellence?
<--- Score
93. Has the Self service 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
94. Has the direction changed at all during the course of Self service software? If so, when did it change and why?
<--- Score
95. 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
96. Will a Self service software production readiness review be required?
<--- Score
97. Has a project plan, Gantt chart, or similar been developed/completed?
<--- Score
98. Do the problem and goal statements meet the SMART criteria (specific, measurable, attainable, relevant, and time-bound)?
<--- Score
99. What is out-of-scope initially?
<--- Score
100. How are consistent Self service software definitions important?
<---
