dates/times of each activity?
<--- Score
29. Is there any additional Agile software definition of success?
<--- Score
30. Which organizational model and culture changes are required?
<--- Score
31. Has the improvement team collected the ‘voice of the customer’ (obtained feedback – qualitative and quantitative)?
<--- Score
32. Is the team formed and are team leaders (Coaches and Management Leads) assigned?
<--- Score
33. Is the current ‘as is’ process being followed? If not, what are the discrepancies?
<--- Score
34. How do you estimate the roi of agile software requirements?
<--- Score
35. How do bounded contexts communicate?
<--- Score
36. What patterns can be obtained from the interaction of agile software delivery with its organizational context?
<--- Score
37. When is the estimated completion date?
<--- Score
38. Are stakeholder processes mapped?
<--- Score
39. Has a project plan, Gantt chart, or similar been developed/completed?
<--- Score
40. What do you do with the methods that support use cases?
<--- Score
41. What are the Roles and Responsibilities for each team member and its leadership? Where is this documented?
<--- Score
42. Will team members regularly document their Agile software work?
<--- Score
43. What are (control) requirements for Agile software Information?
<--- Score
44. Is the team sponsored by a champion or stakeholder leader?
<--- Score
45. What is in the scope and what is not in scope?
<--- Score
46. What customer feedback methods were used to solicit their input?
<--- Score
47. What key stakeholder process output measure(s) does Agile software leverage and how?
<--- Score
48. Is there a critical path to deliver Agile software results?
<--- Score
49. Is full participation by members in regularly held team meetings guaranteed?
<--- Score
50. How many user requirements were Delivered in the sprint?
<--- Score
51. Is the work to date meeting requirements?
<--- Score
52. Is the Agile software scope manageable?
<--- Score
53. Has the direction changed at all during the course of Agile software? If so, when did it change and why?
<--- Score
54. How do you manage unclear Agile software requirements?
<--- Score
55. Are different versions of process maps needed to account for the different types of inputs?
<--- Score
56. What knowledge or experience is required?
<--- Score
57. Has a high-level ‘as is’ process map been completed, verified and validated?
<--- Score
58. When are meeting minutes sent out? Who is on the distribution list?
<--- Score
59. What are the Agile software use cases?
<--- Score
60. 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
61. What are the dynamics of the communication plan?
<--- Score
62. Will team members perform Agile software work when assigned and in a timely fashion?
<--- Score
63. What is the objective of software specification (requirements engineering)?
<--- Score
64. Has anyone else (internal or external to the group) attempted to solve this problem or a similar one before? If so, what knowledge can be leveraged from these previous efforts?
<--- Score
65. Are team charters developed?
<--- Score
66. What specifically is the problem? Where does it occur? When does it occur? What is its extent?
<--- Score
67. Is there a Agile software management charter, including stakeholder case, problem and goal statements, scope, milestones, roles and responsibilities, communication plan?
<--- Score
68. Is the team adequately staffed with the desired cross-functionality? If not, what additional resources are available to the team?
<--- Score
69. Do you all define Agile software in the same way?
<--- Score
70. Are there any constraints known that bear on the ability to perform Agile software work? How is the team addressing them?
<---
