<--- Score
17. Are approval levels defined for contracts and supplements to contracts?
<--- Score
18. Are there any constraints known that bear on the ability to perform Organization behavior work? How is the team addressing them?
<--- Score
19. What intelligence can you gather?
<--- Score
20. What was the context?
<--- Score
21. Are there different segments of customers?
<--- Score
22. Do the problem and goal statements meet the SMART criteria (specific, measurable, attainable, relevant, and time-bound)?
<--- Score
23. What are (control) requirements for Organization behavior Information?
<--- Score
24. Have the customer needs been translated into specific, measurable requirements? How?
<--- Score
25. What system do you use for gathering Organization behavior information?
<--- Score
26. What defines best in class?
<--- Score
27. How often are the team meetings?
<--- Score
28. Has a project plan, Gantt chart, or similar been developed/completed?
<--- Score
29. Is Organization behavior required?
<--- Score
30. Are customer(s) identified and segmented according to their different needs and requirements?
<--- Score
31. Is the team equipped with available and reliable resources?
<--- Score
32. Is scope creep really all bad news?
<--- Score
33. What is out-of-scope initially?
<--- Score
34. What are the requirements for audit information?
<--- Score
35. Are the Organization behavior requirements testable?
<--- Score
36. Has a team charter been developed and communicated?
<--- Score
37. 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
38. Is data collected and displayed to better understand customer(s) critical needs and requirements.
<--- Score
39. Is Organization behavior currently on schedule according to the plan?
<--- Score
40. What gets examined?
<--- Score
41. What scope to assess?
<--- Score
42. How are consistent Organization behavior definitions important?
<--- Score
43. Will a Organization behavior production readiness review be required?
<--- Score
44. How can the value of Organization behavior be defined?
<--- Score
45. What are the boundaries of the scope? What is in bounds and what is not? What is the start point? What is the stop point?
<--- Score
46. How do you gather requirements?
<--- Score
47. Has everyone on the team, including the team leaders, been properly trained?
<--- Score
48. What are the compelling stakeholder reasons for embarking on Organization behavior?
<--- Score
49. Are the Organization behavior requirements complete?
<--- Score
50. What is the context?
<--- Score
51. Is there a Organization behavior management charter, including stakeholder case, problem and goal statements, scope, milestones, roles and responsibilities, communication plan?
<--- Score
52. Scope of sensitive information?
<--- Score
53. Is there a completed, verified, and validated high-level ‘as is’ (not ‘should be’ or ‘could be’) stakeholder process map?
<--- Score
54. Why are you doing Organization behavior and what is the scope?
<--- Score
55. What information should you gather?
<--- Score
56. Are different versions of process maps needed to account for the different types of inputs?
<--- Score
57. Is there a completed SIPOC representation, describing the Suppliers, Inputs, Process, Outputs, and Customers?
<--- Score
58. How do you hand over Organization behavior context?
<--- Score
59. In what way can you redefine the criteria of choice clients have in your category in your favor?
<--- Score
60. Is the Organization
