Functional Database Model A Complete Guide - 2020 Edition. Gerardus Blokdyk

Model in the same way?

      <--- Score

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

      <--- Score

      11. What are the compelling stakeholder reasons for embarking on Functional Database Model?

      <--- Score

      12. What are the Functional Database Model use cases?

      <--- Score

      13. What is the scope of the Functional Database Model work?

      <--- Score

      14. What scope to assess?

      <--- Score

      15. What is in scope?

      <--- Score

      16. How do you manage scope?

      <--- Score

      17. What are the Functional Database Model tasks and definitions?

      <--- Score

      18. Are task requirements clearly defined?

      <--- Score

      19. Where can you gather more information?

      <--- Score

      20. Is there a clear Functional Database Model case definition?

      <--- Score

      21. When is/was the Functional Database Model start date?

      <--- Score

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

      <--- Score

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

      <--- Score

      24. What would be the goal or target for a Functional Database Model’s improvement team?

      <--- Score

      25. Is there a critical path to deliver Functional Database Model results?

      <--- Score

      26. Who are the Functional Database Model improvement team members, including Management Leads and Coaches?

      <--- Score

      27. How do you gather requirements?

      <--- Score

      28. How can the value of Functional Database Model be defined?

      <--- Score

      29. Are there any constraints known that bear on the ability to perform Functional Database Model work? How is the team addressing them?

      <--- Score

      30. Is scope creep really all bad news?

      <--- Score

      31. What sources do you use to gather information for a Functional Database Model study?

      <--- Score

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

      <--- Score

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

      <--- Score

      34. What are the record-keeping requirements of Functional Database Model activities?

      <--- Score

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

      <--- Score

      36. What is the worst case scenario?

      <--- Score

      37. What are the rough order estimates on cost savings/opportunities that Functional Database Model brings?

      <--- Score

      38. Has your scope been defined?

      <--- Score

      39. What Functional Database Model requirements should be gathered?

      <--- Score

      40. How do you manage unclear Functional Database Model requirements?

      <--- Score

      41. The political context: who holds power?

      <--- Score

      42. What knowledge or experience is required?

      <--- Score

      43. Is the scope of Functional Database Model defined?

      <--- Score

      44. Are resources adequate for the scope?

      <--- Score

      45. When is the estimated completion date?

      <--- Score

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

      <--- Score

      47. Are the Functional Database Model requirements complete?

      <--- Score

      48. What sort of initial information to gather?

      <--- Score

      49. How do you catch Functional Database Model definition inconsistencies?

      <--- Score

      50. Has the direction changed at all during the course of Functional Database Model? If so, when did it change and why?

      <--- Score

      51. What are the core elements of the Functional Database Model business case?

      <--- Score

      52. What are the tasks and definitions?

      <--- Score

      53. What was the context?

      <--- Score

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

      <--- Score

      55. Are required metrics defined, what are they?

      <--- Score

      56. Does the scope remain the same?

      <--- Score

      57. How and when will the baselines be defined?

      <--- Score

      58. Is the Functional Database Model scope complete and appropriately sized?

      <--- Score

      59. Scope of sensitive information?

      <--- Score

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

      <--- Score

      61. How will the Functional Database Model team and the group measure complete success of Functional Database Model?

      <--- Score

      62. What are (control) requirements for Functional Database Model Information?

      <--- Score

      63. Do you have organizational privacy requirements?

      <--- Score

      64. How would you define the culture at your organization, how susceptible is it to Functional Database Model changes?

      <--- Score

      65. How does the Functional Database Model manager ensure against scope creep?

      <--- Score

      66. What