LITMIR.BIZ

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

Score

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

      <--- Score

      61. What would be the goal or target for a Software Performance Engineering’s improvement team?

      <--- Score

      62. Is Software Performance Engineering required?

      <--- Score

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

      <--- Score

      64. Is the team adequately staffed with the desired cross-functionality? If not, what additional resources are available to the team?

      <--- Score

      65. Is the Software Performance Engineering scope manageable?

      <--- Score

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

      67. How are consistent Software Performance Engineering definitions important?

      <--- Score

      68. What is a worst-case scenario for losses?

      <--- Score

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

      <--- Score

      70. What are (control) requirements for Software Performance Engineering Information?

      <--- Score

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

      <--- Score

      72. What gets examined?

      <--- Score

      73. What are the record-keeping requirements of Software Performance Engineering activities?

      <--- Score

      74. What was the context?

      <--- Score

      75. Will team members regularly document their Software Performance Engineering work?

      <--- Score

      76. Who defines (or who defined) the rules and roles?

      <--- Score

      77. How do you manage changes in Software Performance Engineering requirements?

      <--- Score

      78. What sources do you use to gather information for a Software Performance Engineering study?

      <--- Score

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

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

      <--- Score

      81. How can the value of Software Performance Engineering be defined?

      <--- Score

      82. Has a team charter been developed and communicated?

      <--- Score

      83. What is the definition of Software Performance Engineering excellence?

      <--- Score

      84. Are all requirements met?

      <--- Score

      85. What is in the scope and what is not in scope?

      <--- Score

      86. How would you define the culture at your organization, how susceptible is it to Software Performance Engineering changes?

      <--- Score

      87. Is the current ‘as is’ process being followed? If not, what are the discrepancies?

      <--- Score

      88. Are the Software Performance Engineering requirements complete?

      <--- Score

      89. When is the estimated completion date?

      <--- Score

      90. How do you gather requirements?

      <--- Score

      91. How and when will the baselines be defined?

      <--- Score

      92. How will the Software Performance Engineering team and the group measure complete success of Software Performance Engineering?

      <--- Score

      93. What is in scope?

      <--- Score

      94. What specifically is the problem? Where does it occur? When does it occur? What is its extent?

      <--- Score

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

      <--- Score

      96. Are approval levels defined for contracts and supplements to contracts?

      <--- Score

      97. What is out-of-scope initially?

      <--- Score

      98. What sort of initial information to gather?

      <--- Score

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

      <--- Score

      100. Is there any additional Software Performance Engineering definition of success?

      <--- Score

      101. What information should you gather?

      <--- Score

      102. What is the scope of the Software Performance Engineering effort?

      <--- Score

      103. Is there a Software Performance Engineering management charter, including stakeholder case, problem and goal statements, scope, milestones, roles and responsibilities, communication plan?

      <--- Score

      104. Are there different segments of customers?

      <--- Score

      105. What constraints exist that might impact the team?

      <--- Score

      106. How do you gather the stories?

      <--- Score

      107. Is full participation by members in regularly held team meetings guaranteed?

      <--- Score

      108. What intelligence can you gather?

      <--- Score

      109. Is the work to date meeting requirements?

      <--- Score

      110. Is special Software Performance Engineering user knowledge required?

      <--- Score

      111. Why are you doing Software Performance Engineering and what is the scope?

      <--- Score

      112. What are the dynamics of the communication plan?

      <--- Score

      113. What are the compelling stakeholder reasons for embarking on Software Performance Engineering?

      <--- Score

      114. What is out of scope?

      <--- Score

      115.

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