Has your scope been defined?
<--- Score
8. Is the team equipped with available and reliable resources?
<--- Score
9. How do you gather requirements?
<--- Score
10. Is the current ‘as is’ process being followed? If not, what are the discrepancies?
<--- Score
11. Is there a Web Design and Development management charter, including stakeholder case, problem and goal statements, scope, milestones, roles and responsibilities, communication plan?
<--- Score
12. How was the ‘as is’ process map developed, reviewed, verified and validated?
<--- Score
13. How can the value of Web Design and Development be defined?
<--- Score
14. Has/have the customer(s) been identified?
<--- Score
15. What Web Design and Development services do you require?
<--- Score
16. What Web Design and Development requirements should be gathered?
<--- Score
17. Has the Web Design and Development 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
18. How do you gather the stories?
<--- Score
19. What are the compelling stakeholder reasons for embarking on Web Design and Development?
<--- Score
20. How would you define Web Design and Development leadership?
<--- Score
21. If substitutes have been appointed, have they been briefed on the Web Design and Development goals and received regular communications as to the progress to date?
<--- Score
22. Has the improvement team collected the ‘voice of the customer’ (obtained feedback – qualitative and quantitative)?
<--- Score
23. How do you think the partners involved in Web Design and Development would have defined success?
<--- Score
24. How do you catch Web Design and Development definition inconsistencies?
<--- Score
25. How did the Web Design and Development manager receive input to the development of a Web Design and Development improvement plan and the estimated completion dates/times of each activity?
<--- Score
26. Are approval levels defined for contracts and supplements to contracts?
<--- Score
27. What information should you gather?
<--- Score
28. What are (control) requirements for Web Design and Development Information?
<--- Score
29. Is data collected and displayed to better understand customer(s) critical needs and requirements.
<--- Score
30. How and when will the baselines be defined?
<--- Score
31. How will variation in the actual durations of each activity be dealt with to ensure that the expected Web Design and Development results are met?
<--- Score
32. What was the context?
<--- Score
33. What are the rough order estimates on cost savings/opportunities that Web Design and Development brings?
<--- Score
34. How does the Web Design and Development manager ensure against scope creep?
<--- Score
35. Has the direction changed at all during the course of Web Design and Development? If so, when did it change and why?
<--- Score
36. Do you have a Web Design and Development success story or case study ready to tell and share?
<--- Score
37. How do you keep key subject matter experts in the loop?
<--- Score
38. What is out-of-scope initially?
<--- Score
39. What are the core elements of the Web Design and Development business case?
<--- Score
40. Is scope creep really all bad news?
<--- Score
41. Are audit criteria, scope, frequency and methods defined?
<--- Score
42. Does the scope remain the same?
<--- Score
43. Is Web Design and Development currently on schedule according to the plan?
<--- Score
44. When is the estimated completion date?
<--- Score
45. What sort of initial information to gather?
<--- Score
46. Is the Web Design and Development scope complete and appropriately sized?
<--- Score
47. What are the dynamics of the communication plan?
<--- Score
48. Has a project plan, Gantt chart, or similar been developed/completed?
<--- Score
49. Scope of sensitive information?
