Field Applications Engineering A Complete Guide - 2020 Edition. Gerardus Blokdyk

What is the definition of success?

      <--- Score

      59. How will the Field applications engineering team and the group measure complete success of Field applications engineering?

      <--- Score

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

      61. How have you defined all Field applications engineering requirements first?

      <--- Score

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

      <--- Score

      63. When are meeting minutes sent out? Who is on the distribution list?

      <--- Score

      64. What is the scope?

      <--- Score

      65. Who approved the Field applications engineering scope?

      <--- Score

      66. What would be the goal or target for a Field applications engineering’s improvement team?

      <--- Score

      67. What are the rough order estimates on cost savings/opportunities that Field applications engineering brings?

      <--- Score

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

      <--- Score

      69. The political context: who holds power?

      <--- Score

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

      <--- Score

      71. How does the Field applications engineering manager ensure against scope creep?

      <--- Score

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

      73. Are required metrics defined, what are they?

      <--- Score

      74. Does the team have regular meetings?

      <--- Score

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

      <--- Score

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

      <--- Score

      77. What gets examined?

      <--- Score

      78. What was the context?

      <--- Score

      79. Who is gathering Field applications engineering information?

      <--- Score

      80. Who is gathering information?

      <--- Score

      81. Are roles and responsibilities formally defined?

      <--- Score

      82. What is out-of-scope initially?

      <--- Score

      83. How do you gather Field applications engineering requirements?

      <--- Score

      84. What are the Field applications engineering use cases?

      <--- Score

      85. Has the direction changed at all during the course of Field applications engineering? If so, when did it change and why?

      <--- Score

      86. What system do you use for gathering Field applications engineering information?

      <--- Score

      87. When is the estimated completion date?

      <--- Score

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

      <--- Score

      89. Is special Field applications engineering user knowledge required?

      <--- Score

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

      <--- Score

      91. How did the Field applications engineering manager receive input to the development of a Field applications engineering improvement plan and the estimated completion dates/times of each activity?

      <--- Score

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

      <--- Score

      93. What are the compelling stakeholder reasons for embarking on Field applications engineering?

      <--- Score

      94. Do you all define Field applications engineering in the same way?

      <--- Score

      95. What are the Field applications engineering tasks and definitions?

      <--- Score

      96. Are there any constraints known that bear on the ability to perform Field applications engineering work? How is the team addressing them?

      <--- Score

      97. What is the scope of the Field applications engineering work?

      <--- Score

      98. What are the tasks and definitions?

      <--- Score

      99. How do you gather requirements?

      <--- Score

      100. Are all requirements met?

      <--- Score

      101. How will variation in the actual durations of each activity be dealt with to ensure that the expected Field applications engineering results are met?

      <--- Score

      102. Has anyone else (internal or external to the group) attempted to solve this problem or a similar one before? If so, what knowledge can be leveraged from these previous efforts?

      <--- Score

      103. Has a Field applications engineering requirement not been met?

      <--- Score

      104. How are consistent Field applications engineering definitions important?

      <--- Score

      105. Has the Field applications 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

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

      <--- Score

      107. What is out of scope?

      <--- Score

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

      <--- Score

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

      <--- Score

      110. Is scope