Requirements communication is the process of informing the project team ,suppliers, sponsor and stakeholders of the content, meaning and status of requirements.
- The first stage of requirements communication is identifying and inviting people to participate in the requirements elicitation process . This continues when managing the constraints identification and analysis activities.
- When requirements are defined and documented they should be communicated back to the people who provided inputs to ensure the information has been property captured, interpreted and analyzed.
- Requirements documents should also be validated by the sponsor of their representatives.
- Requirements are then provided to solution teams (e.g. programmers), either within the project team or externally. Often external suppliers are external to the client organization, but they can also be other departments within the same client organization.
- Projects are often completed with certain requirements unmet. As requirements are dropped from the delivery plan people need to be informed and expectations managed. Sometimes this results in a scope change for a project.
- A requirements traceability matrix (RTM) is often used to track individual requirements through the development life cycle.
Solution design often influences requirements. Pragmatic requirements communication reduces the likelihood of wrong requirements understanding by allowing the customer to choose among alternative solutions. Handshaking with implementation propopsals reduces specification effort and ensures solution acceptance.
This article is a stub. You know the drill. We'd love you to expand it.