The document outlines key aspects of understanding requirements for projects. It discusses: 1) Why requirements are important for achieving better solutions, lower costs, and improved implementation and adoption. 2) Factors to consider when choosing solutions like timescales, costs, risks. 3) The role of requirements in proposals, guiding solutions, pricing projects, and determining acceptance. 4) Ensuring milestones are met through tools like stakeholder identification, requirements gathering, and change management processes. 5) Common causes of delays like failing to prioritize, ignoring stakeholders, and complex undefined relationships.

1. 
Understanding Requirements

2. Presentation Outline:
 Why requirements matters ?!
 Matter to take into account when choosing the closest fit.
 The role of requirements.
 Key factors driving improved specifications.
 Five key milestones.
 Tools and techniques for ensuring milestones are met.
 Common cases of delay of failure.

3. Why requirements matters ?!
 Better solution.
 Lower costs.
 Improved implementation and adoption.
 Although at certain cases its impossible to achieve
the exact alignment , but the best possible outcome
will be achieved by choosing the closest fit .

4. Matter to take into account when choosing the closest fit
 Timescales for implementation.
 Cost of solution (external).
 Cost of solution (internal).
 Legal and contractual risks.
 Technical and implementation risks.
 The problem of not considering changes in requirements ,
while it normally happen specially in non-commodity
products.

5. The role of requirements :
 Basic for the request for proposal and responses.
 Framework for guiding appropriate solution.
 Basis for pricing the project.
 Foundation for negotiating the contract.
 Key component for communicating.
 Critical contract component or reference.
 Basis for determining acceptance of the project.
 Basis for change control later in the implementation phase of the
project.

6. Key factors driving
improved
specifications
Greater
complexity of
technical
environments
Growing users
sophistication

7. Five key milestones :
Requirement definition is a process which should be
managed with key milestones to enable those who are
involved to be informed about progress.
 Know your stakeholders.
 Know your business objectives.
 Understand the specification.
 Agree the acceptance procedures and criteria.
 Put in a place a robust change management process.

8. Tools and techniques for ensuring milestones are met
Know your stockholders. •Stakeholders identification process.
•Project management templates.
Know your business objectives. •Business objectives questionnaire.
•Structured business objectives interviews.
Understand the specification. •Requirements checklist.
•Requirements gathering questionnaires.
•Structured requirements interviews.
•Joint application development sessions.
•Research and benchmarking.
Agree the acceptance criteria. Acceptance criteria derived from. requirements and business
objectives.
Put in place a robust change management
Process.
•Prototyping.
•Change control documentation and sign off process.

9. Common cases of delay of failure:
 Failure to prioritize.
 Solution-driven answer.
 Forced solutions.
 Outsourced solutions.
 Ignorance of the range of stakeholders.
 Ignorance of the internal economy.
 Failure to understand complexity.
 Ignorance of standards.
 Ignorance of human impact.
 Aggressive use of competition to drive lowest price.
 Complex and poorly defined supply chain relationships.

10. 
ThankYou..