Score
47. Who defines (or who defined) the rules and roles?
<--- Score
48. How does the Project management application manager ensure against scope creep?
<--- Score
49. When is/was the Project management application start date?
<--- Score
50. Has/have the customer(s) been identified?
<--- Score
51. What are the dynamics of the communication plan?
<--- Score
52. Have specific policy objectives been defined?
<--- Score
53. When is the estimated completion date?
<--- Score
54. How would you define the culture at your organization, how susceptible is it to Project management application changes?
<--- Score
55. How did the Project management application manager receive input to the development of a Project management application improvement plan and the estimated completion dates/times of each activity?
<--- Score
56. Has the Project management application 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
57. Do you all define Project management application in the same way?
<--- Score
58. Has a team charter been developed and communicated?
<--- Score
59. How have you defined all Project management application requirements first?
<--- Score
60. Is there a completed SIPOC representation, describing the Suppliers, Inputs, Process, Outputs, and Customers?
<--- Score
61. Are approval levels defined for contracts and supplements to contracts?
<--- Score
62. In what way can you redefine the criteria of choice clients have in your category in your favor?
<--- Score
63. What is a worst-case scenario for losses?
<--- Score
64. How often are the team meetings?
<--- Score
65. What are the core elements of the Project management application business case?
<--- Score
66. What is out of scope?
<--- Score
67. What are the tasks and definitions?
<--- Score
68. Does the team have regular meetings?
<--- Score
69. Have the customer needs been translated into specific, measurable requirements? How?
<--- Score
70. What is in scope?
<--- Score
71. Have all of the relationships been defined properly?
<--- Score
72. What key stakeholder process output measure(s) does Project management application leverage and how?
<--- Score
73. What is in the scope and what is not in scope?
<--- Score
74. How was the ‘as is’ process map developed, reviewed, verified and validated?
<--- Score
75. Have all basic functions of Project management application been defined?
<--- Score
76. Who is gathering information?
<--- Score
77. How do you gather the stories?
<--- Score
78. How can the value of Project management application be defined?
<--- Score
79. 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
80. What intelligence can you gather?
<--- Score
81. Where can you gather more information?
<--- Score
82. How would you define Project management application leadership?
<--- Score
83. How do you build the right business case?
<--- Score
84. Is full participation by members in regularly held team meetings guaranteed?
<--- Score
85. What is the context?
<--- Score
86. What are the Project management application use cases?
<--- Score
87. What gets examined?
<--- Score
88. How do you keep key subject matter experts in the loop?
<--- Score
89. What are the rough order estimates on cost savings/opportunities that Project management application brings?
<--- Score
90. Are task requirements clearly defined?
<--- Score
91.
