Business and Technical Requirements of the Security Awareness Program
Many years ago, I was enlisted to take part in a total migration within the Department of Justice. The Department of Justice had a need for upgrading their network infrastructure because various departments used unsecure means for discussing secure topics. I also had the opportunity to work with an outstanding Project Manager with more than 20 years’ experience, and under his wing I learned early on about “keeping the stakeholders informed.” One of the initial tasks were to understand the needs of the stakeholder and collect data from during the one-on-one meetings. “One way to keep stakeholders focused is by prioritizing requirements with the constraints of time, quality, and budget” (Gale, 2013, p. 48). Therefore, developing and defining the mission of the project had to be established, so all concerned parties (stakeholders) are informed and answered all questions thoroughly. “Stakeholder interviews help get personal, in-depth analysis about requirements” (Gale, 2013, p. 48).
After careful review of the stakeholder requirements for the new technological upgrades, the big concern was security on all levels to overcome as the weekly reading discussed security fatigue and avenues not to follow. For example, the first step is to keep management abreast of any changes, and second don’t cry wolf. “Thirdly, it helps to place a realistic quantification on your projections” (Lacey, 2009, p. 256).
Training was another way of enhancing stakeholder knowledge about the complete change, and the transition ran smoothly, and the turnover was also smooth.

References
Gale, S. F. (2013). Setting the Course. Module Two Supplement: IT 552 – Human Factors in Security course website.
Lacey, D. (2009). Managing the Human Factor in Information Security. Hoboken, NJ: John Wiley & Sons,