Project Pressure, It Happens!

Anyone who has worked on Software Development Projects can relate to project pressure because of somebody changing requirements. Whether the change comes from upper management, peers, customers, or even self-inflicted, it exists, and it's not going anywhere. One thing that I've learned is that as project pressures increase (because of changes in requirements), it's easy to forget the one thing that unites the project that all stakeholders share a common objective; to build a product that will provide business value to the customers and will reward all stakeholders upon successful completion. I like to go into projects with an understanding at the beginning of all projects that the requirements will change as it's a part of our trade and the harsh reality of software projects. This helps me mentally prepare for the ad hoc changes and the specification modifications as the project progresses.

I've learned that when I accept that you can't know all the requirements early on and that software requirements evolve, and that change is something we have to deal with as software engineers. Lastly, try to work with your customers. Show your customers how their participation is not only in their personal best interest but also will lead to collectively better results. Remember that it is critical to agree on a set of requirements planned for a specific release or development iteration. Still, it is also vital that, afterward, all parties understand that these requirements are subject to change and evolve. Extensive and ongoing customer engagement from the start with the customer is an essential part of the software requirements and development process. And even if the end doesn't look clear, nor does it feel like it's near, don't lose sight of your responsibility and why you matter to the project's success.