In what way can you redefine the criteria of choice clients have in your category in your favor?
<--- Score
17. What happens if On-demand software’s scope changes?
<--- Score
18. Is the work to date meeting requirements?
<--- Score
19. Why are you doing On-demand software and what is the scope?
<--- Score
20. Are task requirements clearly defined?
<--- Score
21. Have the customer needs been translated into specific, measurable requirements? How?
<--- Score
22. What are the rough order estimates on cost savings/opportunities that On-demand software brings?
<--- Score
23. How do you manage changes in On-demand software requirements?
<--- Score
24. Are there different segments of customers?
<--- Score
25. Are audit criteria, scope, frequency and methods defined?
<--- Score
26. What is in the scope and what is not in scope?
<--- Score
27. What constraints exist that might impact the team?
<--- Score
28. What information should you gather?
<--- Score
29. Do you have a On-demand software success story or case study ready to tell and share?
<--- Score
30. Is there a completed, verified, and validated high-level ‘as is’ (not ‘should be’ or ‘could be’) stakeholder process map?
<--- Score
31. Has a On-demand software requirement not been met?
<--- Score
32. Has the direction changed at all during the course of On-demand software? If so, when did it change and why?
<--- Score
33. Is there a On-demand software management charter, including stakeholder case, problem and goal statements, scope, milestones, roles and responsibilities, communication plan?
<--- Score
34. What information do you gather?
<--- Score
35. How does the On-demand software manager ensure against scope creep?
<--- Score
36. Are customer(s) identified and segmented according to their different needs and requirements?
<--- Score
37. What intelligence can you gather?
<--- Score
38. What is the scope of the On-demand software effort?
<--- Score
39. When are meeting minutes sent out? Who is on the distribution list?
<--- Score
40. What is the scope of On-demand software?
<--- Score
41. The political context: who holds power?
<--- Score
42. What is the worst case scenario?
<--- Score
43. What specifically is the problem? Where does it occur? When does it occur? What is its extent?
<--- Score
44. How do you think the partners involved in On-demand software would have defined success?
<--- Score
45. If substitutes have been appointed, have they been briefed on the On-demand software goals and received regular communications as to the progress to date?
<--- Score
46. Is the current ‘as is’ process being followed? If not, what are the discrepancies?
<--- Score
47. When is the estimated completion date?
<--- Score
48. What are the On-demand software tasks and definitions?
<--- Score
49. What baselines are required to be defined and managed?
<--- Score
50. Will team members regularly document their On-demand software work?
<--- Score
51. What are the core elements of the On-demand software business case?
<--- Score
52. Is it clearly defined in and to your organization what you do?
<--- Score
53. Are approval levels defined for contracts and supplements to contracts?
<--- Score
54. Will team members perform On-demand software work when assigned and in a timely fashion?
<--- Score
55. Is On-demand software linked to key stakeholder goals and objectives?
<--- Score
56. What customer feedback methods were used to solicit their input?
<--- Score
57. Is On-demand software currently on schedule according to the plan?
<--- Score
58. Are the On-demand software requirements testable?
<--- Score
59. Has a project plan, Gantt chart, or similar been developed/completed?
<---
