Requirements keep software development on track and heading in the right direction. They express stakeholder needs and ensure the developers build the right solution.
Requirements can represent high-level business outcomes, end-user functionality, technical constraints, and regulatory and compliance needs. They often interrelate and exist within a hierarchy, eg. lower technical requirements underpinning the functional requirements.
A good business analyst will be more than capable of gathering stakeholder needs and validating them as necessary, before documenting the requirements sufficiently for the technical team to work off.
Requirements capture can happen at different times and levels of detail, depending on factors like team maturity, delivery method, technical complexity, etc.
Stakeholders change their minds over time and as the project progresses, necessitating flexibility in the requirements approach.
The business analyst can oversee all proposed changes, expertly assessing their feasibility and impact and helping the stakeholders make informed decisions.
Iโm passionate about getting a project off to a good start, having previously worked as a developer and been on the receiving end of rubbish, incorrect or simply no requirements at all.
If you are unhappy with your development team, they may need more detailed guidance.
Better software requirements can help with this.
|
Frank Ray Consulting. Software requirements for agile development teams, particularly remote, outsourced and offshore development teams working in financial services. |