Describe a time you had to translate business requirements into technical requirements.

Show the interviewer your strong understanding of technical documentation. Understanding business requirements is important, but there is an even larger emphasis on technical documentation within the HRSD Module.

"As PM of a large ITSM Implementation, I was tasked with interpreting business requirements into technical. I began this process by taking the time to research my client's business. I wanted to know their customers (whether internal or external), market, and competitors. I then identified the internal and external stakeholders. I determined who would be involved with the solution and in what capacity. Next, I scheduled sessions with stakeholders and gathered information on the project's needs and expectations. I analyzed the requirements thoroughly, including considering different use cases where the solution would be applied and contrasting how end users would use the solution according to their role. I then defined the solution scope and presented it to the customer. After structuring, organizing, and sorting the requirements into categories, I developed my Process Flows. From there, I prioritized the requirements and aligned features with the technology that would be used. I presented my strategy to different stakeholders on my team, utilizing their feedback to identify any requirements needing revision. I created two different formats of these technical requirements then to present to technical and non-technical members of the team. I stressed during these meetings that though these requirements are what we initially feel provide the best outcome, requirements may change throughout as we continue to evaluate what changes can or should be included in the development of the current solution."