LITMIR.BIZ

Скачать книгу

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.

      CRITERION #3: MEASURE:

      INTENT: Gather the correct data. Measure the current performance and evolution of the situation.

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

      5 Strongly Agree

      4 Agree

      3 Neutral

      2 Disagree

      1 Strongly Disagree

      1. Is data collection planned and executed?

      <--- Score

      2. Who participated in the data collection for measurements?

      <--- Score

      3. What particular quality tools did the team find helpful in establishing measurements?

      <--- Score

      4. Is the scope of Agile software cost analysis cost-effective?

      <--- Score

      5. What kind of factors impact the performance measurement of agile software business?

      <--- Score

      6. How is software quality measured?

      <--- Score

      7. When should you focus on architecture?

      <--- Score

      8. How will success or failure be measured?

      <--- Score

      9. What are the performance measurement characteristics of Agile models?

      <--- Score

      10. Is it possible to estimate the impact of unanticipated complexity such as wrong or failed assumptions, feedback, etcetera on proposed reforms?

      <--- Score

      11. Is long term and short term variability accounted for?

      <--- Score

      12. How do Agile projects prioritize work?

      <--- Score

      13. What was the overall impact of the changes that were made?

      <--- Score

      14. Do you afford to lock your business into a rigid long-term project where the cost of change grows exponentially?

      <--- Score

      15. Is key measure data collection planned and executed, process variation displayed and communicated and performance baselined?

      <--- Score

      16. Which Agile software impacts are significant?

      <--- Score

      17. What are the costs?

      <--- Score

      18. What are the current costs of the Agile software process?

      <--- Score

      19. Why to measure performance in organization?

      <--- Score

      20. What are the key input variables? What are the key process variables? What are the key output variables?

      <--- Score

      21. Is a solid data collection plan established that includes measurement systems analysis?

      <--- Score

      22. What are the primary factors that make software cost estimation challenging and what can be done to improve your cost

Скачать книгу