Software Performance Engineering A Complete Guide - 2020 Edition. Gerardus Blokdyk

Leads) assigned?

      <--- Score

      4. How does the Software Performance Engineering manager ensure against scope creep?

      <--- Score

      5. The political context: who holds power?

      <--- Score

      6. What customer feedback methods were used to solicit their input?

      <--- Score

      7. What is the definition of success?

      <--- Score

      8. Is Software Performance Engineering linked to key stakeholder goals and objectives?

      <--- Score

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

      <--- Score

      10. What baselines are required to be defined and managed?

      <--- Score

      11. What happens if Software Performance Engineering’s scope changes?

      <--- Score

      12. Has a project plan, Gantt chart, or similar been developed/completed?

      <--- Score

      13. What Software Performance Engineering requirements should be gathered?

      <--- Score

      14. Are required metrics defined, what are they?

      <--- Score

      15. Are task requirements clearly defined?

      <--- Score

      16. Scope of sensitive information?

      <--- Score

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

      <--- Score

      18. Who approved the Software Performance Engineering scope?

      <--- Score

      19. What information do you gather?

      <--- Score

      20. When is/was the Software Performance Engineering start date?

      <--- Score

      21. How do you think the partners involved in Software Performance Engineering would have defined success?

      <--- Score

      22. Is it clearly defined in and to your organization what you do?

      <--- Score

      23. How do you manage unclear Software Performance Engineering requirements?

      <--- Score

      24. What is the scope of Software Performance Engineering?

      <--- Score

      25. What knowledge or experience is required?

      <--- Score

      26. Has your scope been defined?

      <--- Score

      27. Is there a critical path to deliver Software Performance Engineering results?

      <--- Score

      28. Are audit criteria, scope, frequency and methods defined?

      <--- Score

      29. How do you catch Software Performance Engineering definition inconsistencies?

      <--- Score

      30. Who is gathering Software Performance Engineering information?

      <--- Score

      31. Does the team have regular meetings?

      <--- Score

      32. What are the Roles and Responsibilities for each team member and its leadership? Where is this documented?

      <--- Score

      33. How do you build the right business case?

      <--- Score

      34. Is there a clear Software Performance Engineering case definition?

      <--- Score

      35. What Software Performance Engineering services do you require?

      <--- Score

      36. What are the requirements for audit information?

      <--- Score

      37. Have all of the relationships been defined properly?

      <--- Score

      38. Are different versions of process maps needed to account for the different types of inputs?

      <--- Score

      39. What is the scope of the Software Performance Engineering work?

      <--- Score

      40. Who are the Software Performance Engineering improvement team members, including Management Leads and Coaches?

      <--- Score

      41. What scope do you want your strategy to cover?

      <--- Score

      42. Where can you gather more information?

      <--- Score

      43. If substitutes have been appointed, have they been briefed on the Software Performance Engineering goals and received regular communications as to the progress to date?

      <--- Score

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

      <--- Score

      45. What is the context?

      <--- Score

      46. What scope to assess?

      <--- Score

      47. Does the scope remain the same?

      <--- Score

      48. What defines best in class?

      <--- Score

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

      <--- Score

      50. Who is gathering information?

      <--- Score

      51. What system do you use for gathering Software Performance Engineering information?

      <--- Score

      52. Do you have a Software Performance Engineering success story or case study ready to tell and share?

      <--- Score

      53. Is Software Performance Engineering currently on schedule according to the plan?

      <--- Score

      54. Has the direction changed at all during the course of Software Performance Engineering? If so, when did it change and why?

      <--- Score

      55. Has a Software Performance Engineering requirement not been met?

      <--- Score

      56. Are resources adequate for the scope?

      <--- Score

      57. What are the Software Performance Engineering use cases?

      <--- Score

      58. How do you gather Software Performance Engineering requirements?

      <--- Score

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

      <---