Information Systems Security Engineering A Complete Guide - 2020 Edition. Gerardus Blokdyk

section

      Transfer your score to the Information systems security engineering Index at the beginning of the Self-Assessment.

      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. Is Information systems security engineering currently on schedule according to the plan?

      <--- Score

      2. Does the scope remain the same?

      <--- Score

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

      <--- Score

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

      <--- Score

      5. When is the estimated completion date?

      <--- Score

      6. How often are the team meetings?

      <--- Score

      7. What is in scope?

      <--- Score

      8. Where can you gather more information?

      <--- Score

      9. What is the scope?

      <--- Score

      10. What defines best in class?

      <--- Score

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

      <--- Score

      12. Who is gathering Information systems security engineering information?

      <--- Score

      13. Has a team charter been developed and communicated?

      <--- Score

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

      <--- Score

      15. Has the Information systems security engineering 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

      16. How do you gather requirements?

      <--- Score

      17. Are the Information systems security engineering requirements complete?

      <--- Score

      18. Have all basic functions of Information systems security engineering been defined?

      <--- Score

      19. When is/was the Information systems security engineering start date?

      <--- Score

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

      <--- Score

      21. Are required metrics defined, what are they?

      <--- Score

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

      <--- Score

      23. What are the requirements for audit information?

      <--- Score

      24. How does the Information systems security engineering manager ensure against scope creep?

      <--- Score

      25. Are all requirements met?

      <--- Score

      26. What are the compelling stakeholder reasons for embarking on Information systems security engineering?

      <--- Score

      27. Are there different segments of customers?

      <--- Score

      28. Have all of the relationships been defined properly?

      <--- Score

      29. What system do you use for gathering Information systems security engineering information?

      <--- Score

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

      <--- Score

      31. Do you have organizational privacy requirements?

      <--- Score

      32. How and when will the baselines be defined?

      <--- Score

      33. What was the context?

      <--- Score

      34. What Information systems security engineering services do you require?

      <--- Score

      35. Has the improvement team collected the ‘voice of the customer’ (obtained feedback – qualitative and quantitative)?

      <--- Score

      36. Is Information systems security engineering required?

      <--- Score

      37. How would you define Information systems security engineering leadership?

      <--- Score

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

      <--- Score

      39. How do you catch Information systems security engineering definition inconsistencies?

      <--- Score

      40. What gets examined?

      <--- Score

      41. Have specific policy objectives been defined?

      <--- Score

      42. Is there a critical path to deliver Information systems security engineering results?

      <--- Score

      43. How would you define the culture at your organization, how susceptible is it to Information systems security engineering changes?

      <--- Score

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

      <--- Score

      45. Why are you doing Information systems security engineering and what is the scope?

      <--- Score

      46. Has the direction changed at all during the course of Information systems security engineering? If so, when did it change and why?

      <--- Score

      47. What happens if Information systems security engineering’s scope changes?

      <--- Score

      48. What intelligence can you gather?

      <--- Score

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

      <--- Score

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

      <--- Score

      51. How do you manage unclear Information systems security engineering requirements?

      <--- Score

      52. Are resources adequate for the