Agile Requirements GATHERING

Who am I?

• Onur Demir, PMP, PSM• Beykent Uni Maths Computer Sc & MIS Double

Degree• ITU Business & Technology Management Master• 7 years of Business Analyst Experience• 1 year as SAP Consultant at Novigo

Agenda• What is Requirement Gathering

and why is it important?• Background for successful

requirements gathering• Agile Modeling Techniques

• Interface prototype• CRC• UML• User Stories• CASE Tools

• Agile Documentation

It's difficult to build a solution if you don't know the requirements 3 types of requirement:• Business• Functional• Technical

What is REQUIREMENTS

GATHERING

WHY IS ITIMPORTANT?

What is a good REQUIREMENT ? • «We must be able to change

an employee’s profile information»

• «System should be easy to use»

• «We should be able to enter the employee eye colour»

• «The system should automatically be updated when the government changes the law»

TIPs • Ask Questions• Listen• Feedback• Agreement

Agile MANIFEST

Individuals and interactions over processes and toolsWorking software over comprehensive documentationCustomer collaboration over contract negotiationResponding to change over following a plan

• Management Support• Techniques• Terminologies• Keep it fun

Stakeholder

MANAGEMENT

StakeholderMANAGEMENT

Breadth FirstAPPROACH

User Stories

Interface PROTOTYPE• Collaborative approach for

designing interfaces• Just use post-its/slicky

notes

CRC Cards

UML Modeling

• Basic UML modeling that customer understands

• User roles and scenarios can be modeled

CASE Tools

MoSCoW• Must have• Should have• Could have• Would have

Benefit Driven APPROACH

Scope VALIDATION

Agile Documentation

•“The Roman bridges of antiquity were very inefficient structures. By modern standards, they used too much stone, and as a result, far too much labour to build. Over the years we have learned to build bridges more efficiently, using fewer materials and less labor to perform the same task.”

Tom Clancy –Sum of All Fears