Mr Novia
Requirement Analysis and Gathering – a Primer
Putting Customer First
Presenter Profile
Ravi Ayyalaraju – Co-Founder & Chief Customer Advocate
SOAIS, (www.soais.com)
14+ Years of ERP Experience – started as PeopleSoft Technical Consultant in
1995.
Worked in PeopleSoft / Oracle for 12 Years.
Managed Oracle / PeopleSoft Consulting Practice.
Ravi has a
MBA from Northwestern University,
MS in Computer Science from Western Michigan University
Undergraduate degree from Bangalore University in India
Agenda
Introduction
Requirements Basics
Requirement s Gathering
Requirement s Analysis
Requirements Documentation
Requirements gathering during ERP Upgrades
Q&A
Introduction
Requirements Analysis & Gathering is the first step in a project lifecycle.
Considered the most complex aspect of the project.
Output of this phase form critical inputs to determine project schedules, budgets, resourcing, implementation / upgrade / development methodologies and testing strategies.
Errors introduced in this stage are costly to fix in later stages of the project lifecycle. Slide 4
Market research shows …
Challenges
It is difficult to articulate and envision what is needed
Users do not clearly understand what they want or need
Multiple stakeholders take time to freeze on business requirements
Bridging the gap between requirements understood between domain experts and product specialists or technical personnel
Focusing and influencing solutions to the business need rather than defining the need
Changes in requirements after scope and budgets are fixed
Analysis Paralysis
Slide 6
What happens if you don’t get requirements right?
Consequences of not beginning right
Expensive rework and cost overruns
A poor quality product
Late delivery
Dissatisfied customers
Exhausted and demoralized team members
Begin right to finish right !!
Cost of fixing defects escalates as the project progresses !
Phase
Relative
Putting Customer First
Presenter Profile
Ravi Ayyalaraju – Co-Founder & Chief Customer Advocate
SOAIS, (www.soais.com)
14+ Years of ERP Experience – started as PeopleSoft Technical Consultant in
1995.
Worked in PeopleSoft / Oracle for 12 Years.
Managed Oracle / PeopleSoft Consulting Practice.
Ravi has a
MBA from Northwestern University,
MS in Computer Science from Western Michigan University
Undergraduate degree from Bangalore University in India
Agenda
Introduction
Requirements Basics
Requirement s Gathering
Requirement s Analysis
Requirements Documentation
Requirements gathering during ERP Upgrades
Q&A
Introduction
Requirements Analysis & Gathering is the first step in a project lifecycle.
Considered the most complex aspect of the project.
Output of this phase form critical inputs to determine project schedules, budgets, resourcing, implementation / upgrade / development methodologies and testing strategies.
Errors introduced in this stage are costly to fix in later stages of the project lifecycle. Slide 4
Market research shows …
Challenges
It is difficult to articulate and envision what is needed
Users do not clearly understand what they want or need
Multiple stakeholders take time to freeze on business requirements
Bridging the gap between requirements understood between domain experts and product specialists or technical personnel
Focusing and influencing solutions to the business need rather than defining the need
Changes in requirements after scope and budgets are fixed
Analysis Paralysis
Slide 6
What happens if you don’t get requirements right?
Consequences of not beginning right
Expensive rework and cost overruns
A poor quality product
Late delivery
Dissatisfied customers
Exhausted and demoralized team members
Begin right to finish right !!
Cost of fixing defects escalates as the project progresses !
Phase
Relative