Score
15. What Standard data model requirements should be gathered?
<--- Score
16. How will the Standard data model team and the group measure complete success of Standard data model?
<--- Score
17. If substitutes have been appointed, have they been briefed on the Standard data model goals and received regular communications as to the progress to date?
<--- Score
18. What is the scope of the Standard data model effort?
<--- Score
19. Is scope creep really all bad news?
<--- Score
20. What information should you gather?
<--- Score
21. What specifically is the problem? Where does it occur? When does it occur? What is its extent?
<--- Score
22. Is the scope of Standard data model defined?
<--- Score
23. Is data collected and displayed to better understand customer(s) critical needs and requirements.
<--- Score
24. Are all requirements met?
<--- Score
25. Is the team adequately staffed with the desired cross-functionality? If not, what additional resources are available to the team?
<--- Score
26. What knowledge or experience is required?
<--- Score
27. Is there a completed SIPOC representation, describing the Suppliers, Inputs, Process, Outputs, and Customers?
<--- Score
28. How do you hand over Standard data model context?
<--- Score
29. What critical content must be communicated – who, what, when, where, and how?
<--- Score
30. How do you gather Standard data model requirements?
<--- Score
31. How does the Standard data model manager ensure against scope creep?
<--- Score
32. Is it clearly defined in and to your organization what you do?
<--- Score
33. Are there different segments of customers?
<--- Score
34. What are the rough order estimates on cost savings/opportunities that Standard data model brings?
<--- Score
35. Are task requirements clearly defined?
<--- Score
36. How do you gather the stories?
<--- Score
37. How do you think the partners involved in Standard data model would have defined success?
<--- Score
38. What sources do you use to gather information for a Standard data model study?
<--- Score
39. Is the Standard data model scope complete and appropriately sized?
<--- Score
40. Has a project plan, Gantt chart, or similar been developed/completed?
<--- Score
41. 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
42. Are required metrics defined, what are they?
<--- Score
43. Is there a completed, verified, and validated high-level ‘as is’ (not ‘should be’ or ‘could be’) stakeholder process map?
<--- Score
44. Do you all define Standard data model in the same way?
<--- Score
45. Is the team equipped with available and reliable resources?
<--- Score
46. Will a Standard data model production readiness review be required?
<--- Score
47. What are the core elements of the Standard data model business case?
<--- Score
48. How would you define Standard data model leadership?
<--- Score
49. What is the scope of Standard data model?
<--- Score
50. How can the value of Standard data model be defined?
<--- Score
51. How are consistent Standard data model definitions important?
<--- Score
52. In what way can you redefine the criteria of choice clients have in your category in your favor?
<--- Score
53. How would you define the culture at your organization, how susceptible is it to Standard data model changes?
<--- Score
54. What is out of scope?
<--- Score
55. How have you defined all Standard data model requirements first?
<--- Score
56. What are the record-keeping requirements of Standard data model activities?
<--- Score
57. What system do you use for gathering Standard data model information?
<--- Score
58.
