Necessary work conditions for Requirements Engineer

Work conditions and work process determines the quality of documentation delivered by Requirements Engineer. It doesn’t make sense to deliver poor quality requirements because Software Developers and QAs will always find out any inconsistencies and any missing information.

To feel good and to be perceived as reliable person when serving as Requirements Engineer you need to have healthy work environment. This means you have certain rights that have to be honored by your boss and by your client. Here are necessary best practices that all of you have to follow:

• there is no multitasking for Requirements Engineer

  • work only on one project at any given time

• Requirements Engineer never switch context after starting the project

  • Requirements Engineer shall not participate in any other activities except the meetings necessary to create scope or requirements documentation

• every meeting shall take up to 30 minutes

• always record meetings and listen all recordings

  • Requirements Engineer shall record meetings with customer in order to not miss anything and to analyze them piece by piece as part of work on documentation

• conducting storytelling with customer

  • it is SME who shall explain to the Requirements Engineer how he understands his documentation

  • Requirements Engineer improves documentation based on what he/she learned during storytelling

• daily internal quality checks 

  • there is second Requirements Engineer who is checking quality of all requirements