Are roles and responsibilities formally defined?
<--- Score
17. What are the rough order estimates on cost savings/opportunities that Concept analysis brings?
<--- Score
18. What key stakeholder process output measure(s) does Concept analysis leverage and how?
<--- Score
19. How do you manage changes in Concept analysis requirements?
<--- Score
20. What is the definition of Concept analysis excellence?
<--- Score
21. What critical content must be communicated – who, what, when, where, and how?
<--- Score
22. How will variation in the actual durations of each activity be dealt with to ensure that the expected Concept analysis results are met?
<--- Score
23. What customer feedback methods were used to solicit their input?
<--- Score
24. Is there a critical path to deliver Concept analysis results?
<--- Score
25. What is the scope?
<--- Score
26. What baselines are required to be defined and managed?
<--- Score
27. Is there a Concept analysis management charter, including stakeholder case, problem and goal statements, scope, milestones, roles and responsibilities, communication plan?
<--- Score
28. Are accountability and ownership for Concept analysis clearly defined?
<--- Score
29. Has anyone else (internal or external to the group) attempted to solve this problem or a similar one before? If so, what knowledge can be leveraged from these previous efforts?
<--- Score
30. Why are you doing Concept analysis and what is the scope?
<--- Score
31. Is the scope of Concept analysis defined?
<--- Score
32. What Concept analysis services do you require?
<--- Score
33. Is the current ‘as is’ process being followed? If not, what are the discrepancies?
<--- Score
34. Is scope creep really all bad news?
<--- Score
35. How does the Concept analysis manager ensure against scope creep?
<--- Score
36. Is there any additional Concept analysis definition of success?
<--- Score
37. What is a worst-case scenario for losses?
<--- Score
38. How have you defined all Concept analysis requirements first?
<--- Score
39. Are the Concept analysis requirements complete?
<--- Score
40. Has a project plan, Gantt chart, or similar been developed/completed?
<--- Score
41. What is the scope of Concept analysis?
<--- Score
42. Are different versions of process maps needed to account for the different types of inputs?
<--- Score
43. Have all basic functions of Concept analysis been defined?
<--- Score
44. How would you define the culture at your organization, how susceptible is it to Concept analysis changes?
<--- Score
45. What are the requirements for audit information?
<--- Score
46. What is the scope of the Concept analysis effort?
<--- Score
47. Has the direction changed at all during the course of Concept analysis? If so, when did it change and why?
<--- Score
48. Will a Concept analysis production readiness review be required?
<--- Score
49. Are resources adequate for the scope?
<--- Score
50. Scope of sensitive information?
<--- Score
51. Who approved the Concept analysis scope?
<--- Score
52. How was the ‘as is’ process map developed, reviewed, verified and validated?
<--- Score
53. 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
54. What are the core elements of the Concept analysis business case?
<--- Score
55. What are the Roles and Responsibilities for each team member and its leadership? Where is this documented?
<--- Score
56. What is the worst case scenario?
<--- Score
57. Have all of the relationships been defined properly?
<--- Score
58. Is special Concept analysis user knowledge required?
<--- Score
59. Has a team charter been developed and communicated?
<---
