Читать книгу Agile Software A Complete Guide - 2020 Edition - Gerardus Blokdyk - Страница 8

CRITERION #2: DEFINE:

INTENT: Formulate the stakeholder problem. Define the problem, needs and objectives.

In my belief, the answer to this question is clearly defined:

5 Strongly Agree

4 Agree

3 Neutral

2 Disagree

1 Strongly Disagree

1. What constraints on components are imposed by non-functional requirements?

<--- Score

2. Is there a completed SIPOC representation, describing the Suppliers, Inputs, Process, Outputs, and Customers?

<--- Score

3. Does the team have regular meetings?

<--- Score

4. Who are the Agile software improvement team members, including Management Leads and Coaches?

<--- Score

5. Has everyone on the team, including the team leaders, been properly trained?

<--- Score

6. If substitutes have been appointed, have they been briefed on the Agile software goals and received regular communications as to the progress to date?

<--- Score

7. What are the rough order estimates on cost savings/opportunities that Agile software brings?

<--- Score

8. In what way can you redefine the criteria of choice clients have in your category in your favor?

<--- Score

9. How do you keep key subject matter experts in the loop?

<--- Score

10. Is Agile software linked to key stakeholder goals and objectives?

<--- Score

11. What would be the goal or target for a Agile software’s improvement team?

<--- Score

12. What critical content must be communicated – who, what, when, where, and how?

<--- Score

13. How will the Agile software team and the group measure complete success of Agile software?

<--- Score

14. How do you achieve a balance between the fixed and evolving quality requirements?

<--- Score

15. Is the team equipped with available and reliable resources?

<--- Score

16. What are the compelling stakeholder reasons for embarking on Agile software?

<--- Score

17. Is there regularly 100% attendance at the team meetings? If not, have appointed substitutes attended to preserve cross-functionality and full representation?

<--- Score

18. Do you have a Agile software success story or case study ready to tell and share?

<--- Score

19. Are accountability and ownership for Agile software clearly defined?

<--- Score

20. Are improvement team members fully trained on Agile software?

<--- Score

21. What is the definition of Agile software excellence?

<--- Score

22. How will that use case habit know which accounts to use?

<--- Score

23. Are customer(s) identified and segmented according to their different needs and requirements?

<--- Score

24. What are the record-keeping requirements of Agile software activities?

<--- Score

25. Has a team charter been developed and communicated?

<--- Score

26. Has/have the customer(s) been identified?

<--- Score

27. Do you have organizational privacy requirements?

<--- Score

28. How did the Agile software manager receive input to the development of a Agile software improvement plan and the estimated completion 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?

<--- Score

71. Why are you doing Agile software and what is the scope?

<--- Score

72. Which of might you use instead of use cases?

<--- Score

73. How is the team tracking and documenting its work?

<--- Score

74. How will variation in the actual durations of each activity be dealt with to ensure that the expected Agile software results are met?

<--- Score

75. Are customers identified and high impact areas defined?

<--- Score

76. Is a fully trained team formed, supported, and committed to work on the Agile software improvements?

<--- Score

77. How would you define Agile software leadership?

<--- Score

78. How are consistent Agile software definitions important?

<--- Score

79. How often are the team meetings?

<--- Score

80. Have all basic functions of Agile software been defined?

<--- Score

81. Have the customer needs been translated into specific, measurable requirements? How?

<--- Score

82. Are there different segments of customers?

<--- Score

83. Is data collected and displayed to better understand customer(s) critical needs and requirements.

<--- Score

84. What constraints exist that might impact the team?

<--- Score

85. How does the Agile software manager ensure against scope creep?

<--- Score

86. Has the Agile software 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

87. Is there a completed, verified, and validated high-level ‘as is’ (not ‘should be’ or ‘could be’) stakeholder process map?

<--- Score

88. What strategies can help to reduce or manage scope in real-world projects?

<--- Score

89. 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

90. How was the ‘as is’ process map developed, reviewed, verified and validated?

<--- Score

91. Do the problem and goal statements meet the SMART criteria (specific, measurable, attainable, relevant, and time-bound)?

<--- Score

92. When is/was the Agile software start date?

<--- Score

93. Is Agile software currently on schedule according to the plan?

<--- Score

Add up total points for this section: _____ = Total points for this section

Divided by: ______ (number of statements answered) = ______ Average score for this section

Transfer your score to the Agile software Index at the beginning of the Self-Assessment.