Score
10. Do you have organizational privacy requirements?
<--- Score
11. Is the current ‘as is’ process being followed? If not, what are the discrepancies?
<--- Score
12. Are task requirements clearly defined?
<--- Score
13. Is the team formed and are team leaders (Coaches and Management Leads) assigned?
<--- Score
14. Is the team equipped with available and reliable resources?
<--- Score
15. How do you build the right business case?
<--- Score
16. How have you defined all Web information system requirements first?
<--- Score
17. What are the dynamics of the communication plan?
<--- Score
18. What are (control) requirements for Web information system Information?
<--- Score
19. In what way can you redefine the criteria of choice clients have in your category in your favor?
<--- Score
20. What are the Web information system tasks and definitions?
<--- Score
21. What Web information system services do you require?
<--- Score
22. What is the scope of the Web information system effort?
<--- Score
23. Is it clearly defined in and to your organization what you do?
<--- Score
24. How do you catch Web information system definition inconsistencies?
<--- Score
25. How do you think the partners involved in Web information system would have defined success?
<--- Score
26. How do you gather Web information system requirements?
<--- Score
27. When is/was the Web information system start date?
<--- Score
28. How do you gather the stories?
<--- Score
29. Do you have a Web information system success story or case study ready to tell and share?
<--- Score
30. Has a project plan, Gantt chart, or similar been developed/completed?
<--- Score
31. Does the team have regular meetings?
<--- Score
32. Is there regularly 100% attendance at the team meetings? If not, have appointed substitutes attended to preserve cross-functionality and full representation?
<--- Score
33. What key stakeholder process output measure(s) does Web information system leverage and how?
<--- Score
34. 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
35. What Web information system requirements should be gathered?
<--- Score
36. Is there a completed, verified, and validated high-level ‘as is’ (not ‘should be’ or ‘could be’) stakeholder process map?
<--- Score
37. Scope of sensitive information?
<--- Score
38. What is the scope of the Web information system work?
<--- Score
39. What is the worst case scenario?
<--- Score
40. What information should you gather?
<--- Score
41. Who are the Web information system improvement team members, including Management Leads and Coaches?
<--- Score
42. The political context: who holds power?
<--- Score
43. Is data collected and displayed to better understand customer(s) critical needs and requirements.
<--- Score
44. Who defines (or who defined) the rules and roles?
<--- Score
45. What are the Web information system use cases?
<--- Score
46. How was the ‘as is’ process map developed, reviewed, verified and validated?
<--- Score
47. Where can you gather more information?
<--- Score
48. Is there a Web information system management charter, including stakeholder case, problem and goal statements, scope, milestones, roles and responsibilities, communication plan?
<--- Score
49. Has a high-level ‘as is’ process map been completed, verified and validated?
<--- Score
50. How do you manage changes in Web information system requirements?
<--- Score
51. What is in scope?
<--- Score
52. Are resources adequate for the scope?
<--- Score
53. Is Web information system linked to key stakeholder
