Score
3. Is Information systems discipline linked to key stakeholder goals and objectives?
<--- Score
4. What are the record-keeping requirements of Information systems discipline activities?
<--- Score
5. Are resources adequate for the scope?
<--- Score
6. Are approval levels defined for contracts and supplements to contracts?
<--- Score
7. What would be the goal or target for a Information systems discipline’s improvement team?
<--- Score
8. Are audit criteria, scope, frequency and methods defined?
<--- Score
9. Has the improvement team collected the ‘voice of the customer’ (obtained feedback – qualitative and quantitative)?
<--- Score
10. Who is gathering Information systems discipline information?
<--- Score
11. Is there any additional Information systems discipline definition of success?
<--- Score
12. In what way can you redefine the criteria of choice clients have in your category in your favor?
<--- Score
13. What was the context?
<--- Score
14. How is the team tracking and documenting its work?
<--- Score
15. How do you gather requirements?
<--- Score
16. What sources do you use to gather information for a Information systems discipline study?
<--- Score
17. What are the core elements of the Information systems discipline business case?
<--- Score
18. How do you gather Information systems discipline requirements?
<--- Score
19. What are the Roles and Responsibilities for each team member and its leadership? Where is this documented?
<--- Score
20. Has the direction changed at all during the course of Information systems discipline? If so, when did it change and why?
<--- Score
21. When is/was the Information systems discipline start date?
<--- Score
22. What are the requirements for audit information?
<--- Score
23. How can the value of Information systems discipline be defined?
<--- Score
24. Do you all define Information systems discipline in the same way?
<--- Score
25. What information do you gather?
<--- Score
26. What constraints exist that might impact the team?
<--- Score
27. Are different versions of process maps needed to account for the different types of inputs?
<--- Score
28. How does the Information systems discipline manager ensure against scope creep?
<--- Score
29. How did the Information systems discipline manager receive input to the development of a Information systems discipline improvement plan and the estimated completion dates/times of each activity?
<--- Score
30. What is the definition of Information systems discipline excellence?
<--- Score
31. What critical content must be communicated – who, what, when, where, and how?
<--- Score
32. Has the Information systems discipline 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
33. What customer feedback methods were used to solicit their input?
<--- Score
34. What is the scope of the Information systems discipline effort?
<--- Score
35. Is data collected and displayed to better understand customer(s) critical needs and requirements.
<--- Score
36. Is there a Information systems discipline management charter, including stakeholder case, problem and goal statements, scope, milestones, roles and responsibilities, communication plan?
<--- Score
37. Is there a critical path to deliver Information systems discipline results?
<--- Score
38. 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
39. Are accountability and ownership for Information systems discipline clearly defined?
<--- Score
40. Is special Information systems discipline user knowledge required?
<--- Score
41. How do you catch Information systems discipline definition inconsistencies?
<--- Score
42. Are the Information systems discipline requirements testable?
<--- Score
43. What is in the scope and what is not in scope?
<--- Score
44. What intelligence can you gather?
<--- Score
45. Are customer(s) identified and segmented according to their different needs and requirements?
<--- Score
46. How will the Information systems discipline team and the group measure complete success of Information systems discipline?
<--- Score
47. How do you manage changes in Information systems discipline requirements?
<--- Score
48. If substitutes have been appointed, have they been briefed on the Information systems discipline goals and received regular communications as to the progress to date?
<--- Score
49. Is the scope of Information systems discipline defined?
<--- Score
50. What sort of initial information to gather?
<--- Score
51. Is the Information systems discipline scope complete and appropriately sized?
<--- Score
52. What are the tasks and definitions?
<--- Score
53. What key stakeholder process output measure(s) does Information systems discipline leverage and how?
<--- Score
54. How have