Have specific policy objectives been defined?
<--- Score
39. What constraints exist that might impact the team?
<--- Score
40. What sort of initial information to gather?
<--- Score
41. How do you keep key subject matter experts in the loop?
<--- Score
42. 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
43. What baselines are required to be defined and managed?
<--- Score
44. Is the work to date meeting requirements?
<--- Score
45. What is out-of-scope initially?
<--- Score
46. Has a project plan, Gantt chart, or similar been developed/completed?
<--- Score
47. How are consistent Business and Information Systems Engineering definitions important?
<--- Score
48. Is the Business and Information Systems Engineering scope manageable?
<--- Score
49. If substitutes have been appointed, have they been briefed on the Business and Information Systems Engineering goals and received regular communications as to the progress to date?
<--- Score
50. Is Business and Information Systems Engineering currently on schedule according to the plan?
<--- Score
51. Why are you doing Business and Information Systems Engineering and what is the scope?
<--- Score
52. How do you catch Business and Information Systems Engineering definition inconsistencies?
<--- Score
53. What are the Business and Information Systems Engineering use cases?
<--- Score
54. What is in the scope and what is not in scope?
<--- Score
55. What information should you gather?
<--- Score
56. Are the Business and Information Systems Engineering requirements complete?
<--- Score
57. What is the worst case scenario?
<--- Score
58. Do you have a Business and Information Systems Engineering success story or case study ready to tell and share?
<--- Score
59. How would you define the culture at your organization, how susceptible is it to Business and Information Systems Engineering changes?
<--- Score
60. What is the scope of Business and Information Systems Engineering?
<--- Score
61. 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
62. What would be the goal or target for a Business and Information Systems Engineering’s improvement team?
<--- Score
63. What key stakeholder process output measure(s) does Business and Information Systems Engineering leverage and how?
<--- Score
64. Is there a completed, verified, and validated high-level ‘as is’ (not ‘should be’ or ‘could be’) stakeholder process map?
<--- Score
65. Has the improvement team collected the ‘voice of the customer’ (obtained feedback – qualitative and quantitative)?
<--- Score
66. How do you gather requirements?
<--- Score
67. How do you manage changes in Business and Information Systems Engineering requirements?
<--- Score
68. What happens if Business and Information Systems Engineering’s scope changes?
<--- Score
69. How can the value of Business and Information Systems Engineering be defined?
<--- Score
70. What is in scope?
<--- Score
71. Are accountability and ownership for Business and Information Systems Engineering clearly defined?
<--- Score
72. What intelligence can you gather?
<--- Score
73. Have all basic functions of Business and Information Systems Engineering been defined?
<--- Score
74. What are the core elements of the Business and Information Systems Engineering business case?
<--- Score
75. How often are the team meetings?
<--- Score
76. Are the Business and Information Systems Engineering requirements testable?
<--- Score
77. When is/was the Business and Information Systems Engineering start date?
<--- Score
78. Are customer(s) identified and segmented according to their different needs and requirements?
<--- Score
79. What is the definition of success?
<--- Score
80.
