Requirements Engineering.
Agreeing requirements in clear terms.
Eliciting and agreeing business requirements.Managing changes and decisions transparently.Eliciting and clarifying requirements.Managing changes in a targeted way.
Starting point
Requirements engineering covers eliciting, analysing, documenting and agreeing business requirements. Requirements management keeps them traceable throughout a project and takes account of changes and dependencies.
When software is selected or developed, those involved often have different expectations. Unclear terms, missing priorities and uncoordinated changes make decisions more difficult and lead to avoidable queries during implementation.
Jointly understood objectives, verifiable criteria and a defined change process make sound decisions possible.
From business need to verifiable requirements
Need for clarification
Objectives, stakeholders, terms and system boundaries
Deliverables
Prioritised requirements, acceptance criteria and change decisions
Which documents are produced depends on the scope and subject of the project.
Consulting and approach
In interviews and workshops, I clarify stakeholders, objectives and system boundaries. This results in a prioritised requirements baseline with verifiable acceptance criteria and a defined change process.
Possible outcomes
Typical deliverables are an agreed requirements baseline, documented decisions and a defined change procedure. They support system selection, development and acceptance.
I advise mid-sized companies as well as universities and other educational institutions on this topic. An enquiry only needs a brief outline of the current situation and the desired outcome; we can discuss everything else in a conversation.