<--- Score
54. Is it clearly defined in and to your organization what you do?
<--- Score
55. Has the Microsoft Office Mobile 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
56. Has a project plan, Gantt chart, or similar been developed/completed?
<--- Score
57. What is in the scope and what is not in scope?
<--- Score
58. How do you gather Microsoft Office Mobile requirements?
<--- Score
59. How do you manage changes in Microsoft Office Mobile requirements?
<--- Score
60. What gets examined?
<--- Score
61. Are customer(s) identified and segmented according to their different needs and requirements?
<--- Score
62. Is there any additional Microsoft Office Mobile definition of success?
<--- Score
63. Are different versions of process maps needed to account for the different types of inputs?
<--- Score
64. How do you manage unclear Microsoft Office Mobile requirements?
<--- Score
65. Is Microsoft Office Mobile required?
<--- Score
66. Is scope creep really all bad news?
<--- Score
67. What information should you gather?
<--- Score
68. Is the Microsoft Office Mobile scope manageable?
<--- Score
69. How are consistent Microsoft Office Mobile definitions important?
<--- Score
70. Has a Microsoft Office Mobile requirement not been met?
<--- Score
71. How would you define Microsoft Office Mobile leadership?
<--- Score
72. How do you catch Microsoft Office Mobile definition inconsistencies?
<--- Score
73. What are the dynamics of the communication plan?
<--- Score
74. What happens if Microsoft Office Mobile’s scope changes?
<--- Score
75. Has everyone on the team, including the team leaders, been properly trained?
<--- Score
76. Are improvement team members fully trained on Microsoft Office Mobile?
<--- Score
77. Are there any constraints known that bear on the ability to perform Microsoft Office Mobile work? How is the team addressing them?
<--- Score
78. What are (control) requirements for Microsoft Office Mobile Information?
<--- Score
79. What system do you use for gathering Microsoft Office Mobile information?
<--- Score
80. What are the record-keeping requirements of Microsoft Office Mobile activities?
<--- Score
81. What scope to assess?
<--- Score
82. The political context: who holds power?
<--- Score
83. Who defines (or who defined) the rules and roles?
<--- Score
84. What is the context?
<--- Score
85. What Microsoft Office Mobile services do you require?
<--- Score
86. What is out of scope?
<--- Score
87. Is the team equipped with available and reliable resources?
<--- Score
88. What are the Microsoft Office Mobile tasks and definitions?
<--- Score
89. What is the scope of the Microsoft Office Mobile effort?
<--- Score
90. Have the customer needs been translated into specific, measurable requirements? How?
<--- Score
91. What constraints exist that might impact the team?
<--- Score
92. Is Microsoft Office Mobile linked to key stakeholder goals and objectives?
<--- Score
93. What would be the goal or target for a Microsoft Office Mobile’s improvement team?
<--- Score
94. When is the estimated completion date?
<--- Score
95. Is there a completed, verified, and validated high-level ‘as is’ (not ‘should be’ or ‘could be’) stakeholder process map?
<--- Score
96. 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
97. Is data collected and displayed to better understand customer(s) critical needs and requirements.
<---
