Score
17. 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
18. What are the core elements of the Tracking systems business case?
<--- Score
19. What specifically is the problem? Where does it occur? When does it occur? What is its extent?
<--- Score
20. What is out of scope?
<--- Score
21. What are the compelling stakeholder reasons for embarking on Tracking systems?
<--- Score
22. How do you manage unclear Tracking systems requirements?
<--- Score
23. What is the scope of the Tracking systems work?
<--- Score
24. Has a Tracking systems requirement not been met?
<--- Score
25. Has a high-level ‘as is’ process map been completed, verified and validated?
<--- Score
26. How do you gather Tracking systems requirements?
<--- Score
27. What are the Tracking systems tasks and definitions?
<--- Score
28. How do you catch Tracking systems definition inconsistencies?
<--- Score
29. Who approved the Tracking systems scope?
<--- Score
30. How is the team tracking and documenting its work?
<--- Score
31. Are accountability and ownership for Tracking systems clearly defined?
<--- Score
32. What scope do you want your strategy to cover?
<--- Score
33. Does the scope remain the same?
<--- Score
34. How do you gather the stories?
<--- Score
35. What is the context?
<--- Score
36. Where can you gather more information?
<--- Score
37. If substitutes have been appointed, have they been briefed on the Tracking systems goals and received regular communications as to the progress to date?
<--- Score
38. How are consistent Tracking systems definitions important?
<--- Score
39. Is the team adequately staffed with the desired cross-functionality? If not, what additional resources are available to the team?
<--- Score
40. The political context: who holds power?
<--- Score
41. Have the customer needs been translated into specific, measurable requirements? How?
<--- Score
42. Have specific policy objectives been defined?
<--- Score
43. What is the definition of success?
<--- Score
44. What is the scope of the Tracking systems effort?
<--- Score
45. What are the Tracking systems use cases?
<--- Score
46. How and when will the baselines be defined?
<--- Score
47. How will variation in the actual durations of each activity be dealt with to ensure that the expected Tracking systems results are met?
<--- Score
48. What are the dynamics of the communication plan?
<--- Score
49. Are there different segments of customers?
<--- Score
50. What is in scope?
<--- Score
51. What customer feedback methods were used to solicit their input?
<--- Score
52. Are audit criteria, scope, frequency and methods defined?
<--- Score
53. How do you gather requirements?
<--- Score
54. What would be the goal or target for a Tracking systems’s improvement team?
<--- Score
55. Is Tracking systems linked to key stakeholder goals and objectives?
<--- Score
56. How do you build the right business case?
<--- Score
57. Who is gathering information?
<--- Score
58. Is Tracking systems required?
<--- Score
59. In what way can you redefine the criteria of choice clients have in your category in your favor?
<--- Score
60. What are the Roles and Responsibilities for each team member and its leadership? Where is this documented?
<--- Score
61. How would you define Tracking systems leadership?
<--- Score
