Does the team have regular meetings?
<--- Score
11. What information should you gather?
<--- Score
12. Is there a critical path to deliver Electronic system level results?
<--- Score
13. Has a team charter been developed and communicated?
<--- Score
14. Has a project plan, Gantt chart, or similar been developed/completed?
<--- Score
15. What is in the scope and what is not in scope?
<--- Score
16. How do you catch Electronic system level definition inconsistencies?
<--- Score
17. What is the definition of success?
<--- Score
18. Is scope creep really all bad news?
<--- Score
19. Do you have organizational privacy requirements?
<--- Score
20. What constraints exist that might impact the team?
<--- Score
21. How do you build the right business case?
<--- Score
22. Are required metrics defined, what are they?
<--- Score
23. Does the scope remain the same?
<--- Score
24. Is the Electronic system level scope complete and appropriately sized?
<--- Score
25. Has everyone on the team, including the team leaders, been properly trained?
<--- Score
26. How was the ‘as is’ process map developed, reviewed, verified and validated?
<--- Score
27. What customer feedback methods were used to solicit their input?
<--- Score
28. What is in scope?
<--- Score
29. How can the value of Electronic system level be defined?
<--- Score
30. How do you manage scope?
<--- Score
31. What happens if Electronic system level’s scope changes?
<--- Score
32. What are the compelling stakeholder reasons for embarking on Electronic system level?
<--- Score
33. What are (control) requirements for Electronic system level Information?
<--- Score
34. What specifically is the problem? Where does it occur? When does it occur? What is its extent?
<--- Score
35. Who approved the Electronic system level scope?
<--- Score
36. What gets examined?
<--- Score
37. Is the scope of Electronic system level defined?
<--- Score
38. How will the Electronic system level team and the group measure complete success of Electronic system level?
<--- Score
39. If substitutes have been appointed, have they been briefed on the Electronic system level goals and received regular communications as to the progress to date?
<--- Score
40. How do you hand over Electronic system level context?
<--- Score
41. Is there any additional Electronic system level definition of success?
<--- Score
42. In what way can you redefine the criteria of choice clients have in your category in your favor?
<--- Score
43. Is there a completed, verified, and validated high-level ‘as is’ (not ‘should be’ or ‘could be’) stakeholder process map?
<--- Score
44. Is Electronic system level currently on schedule according to the plan?
<--- Score
45. Is there a Electronic system level management charter, including stakeholder case, problem and goal statements, scope, milestones, roles and responsibilities, communication plan?
<--- Score
46. How do you gather requirements?
<--- Score
47. How did the Electronic system level manager receive input to the development of a Electronic system level improvement plan and the estimated completion dates/times of each activity?
<--- Score
48. Has/have the customer(s) been identified?
<--- Score
49. Is it clearly defined in and to your organization what you do?
<--- Score
50. What is the worst case scenario?
<--- Score
51. What are the rough order estimates on cost savings/opportunities that Electronic system level brings?
<--- Score
52. Is the work to date meeting requirements?
<--- Score
53. What key stakeholder process output measure(s) does Electronic system level leverage and how?
<--- Score
54.
