I'm not a coder, but I do work on technical teams that are responsible for configuring software based on client requirements. My team uses a UI with buttons and drop-downs, but the painful process of extracting and defining business requirements still applies.
As anyone who is familiar with this type of work knows, we operate where the rubber meets the road. Executives can bark out what they want the system to do or hand over an audit finding. Business stakeholders and internal customers can provide some additional detail. At the end of the day, all of this boils down to where the rubber meets the road. Is this system configuration going to meet the requirements?
The other problem with where the rubber meets the road is there is usually some sort of urgent deadline. Rarely does my team get a few weeks or months to work on a build, even though other people within the organization know full well what the timelines are.
Take for example a recent project kick-off when I asked the business what the deadline was for the configuration and the answer was "the sooner the better." On top of that, we just received new requirements yesterday, discussed them today, and we don't have approval yet for our approach, yet the team wants the configuration built and deployed to testing environments by Friday.
Sometimes I'd like to far up on the hills where somehow I don't have the responsibility of providing detailed requirements and can crack the whip and say get it done instead of working where the rubber meets the road.
As anyone who is familiar with this type of work knows, we operate where the rubber meets the road. Executives can bark out what they want the system to do or hand over an audit finding. Business stakeholders and internal customers can provide some additional detail. At the end of the day, all of this boils down to where the rubber meets the road. Is this system configuration going to meet the requirements?
The other problem with where the rubber meets the road is there is usually some sort of urgent deadline. Rarely does my team get a few weeks or months to work on a build, even though other people within the organization know full well what the timelines are.
Take for example a recent project kick-off when I asked the business what the deadline was for the configuration and the answer was "the sooner the better." On top of that, we just received new requirements yesterday, discussed them today, and we don't have approval yet for our approach, yet the team wants the configuration built and deployed to testing environments by Friday.
Sometimes I'd like to far up on the hills where somehow I don't have the responsibility of providing detailed requirements and can crack the whip and say get it done instead of working where the rubber meets the road.
