requirements gathering: what could possibly go wrong?

34
Requirements Gathering: What Could Possibly Go Wrong? Dr Eugene O’Loughlin Elicitation

Upload: eugene-oloughlin

Post on 15-Jan-2015

1.711 views

Category:

Education


2 download

DESCRIPTION

Slides form my talk to the Irish Computer Society/Business Analysts Association on 25th March 204.

TRANSCRIPT

Page 1: Requirements Gathering: What Could Possibly Go Wrong?

Requirements Gathering:What Could Possibly Go Wrong?

Dr Eugene O’Loughlin

Elicitation

Page 2: Requirements Gathering: What Could Possibly Go Wrong?

Agenda

• Perception• Planning• Common problems facing BA• Project failures• Poor requirements• Methodology• Overcome problems• Lessons learned

Page 3: Requirements Gathering: What Could Possibly Go Wrong?

Oops!

Page 4: Requirements Gathering: What Could Possibly Go Wrong?

What does your Business Card say about you?

Sorry!

Perfect Results Every Time!

I’m Imperfect!

Business Analyst

Oops!

Page 6: Requirements Gathering: What Could Possibly Go Wrong?

What do you see in this picture?

Page 7: Requirements Gathering: What Could Possibly Go Wrong?

Business Analysts are Organized People?

• Organized• Methodical• Planned

Page 8: Requirements Gathering: What Could Possibly Go Wrong?

Dive in and get started

Page 9: Requirements Gathering: What Could Possibly Go Wrong?

Fail to Plan, Plan to Fail

Page 10: Requirements Gathering: What Could Possibly Go Wrong?

• The best or “alpha” project managers spend more time on every PM process group than their counterparts except for execution, as follows:

• Initiating: 2% vs. 1%• Planning: 21% vs. 11%• Executing: 69% vs. 82%• Controlling: 5% vs. 4%• Closing: 3% vs. 2%1*

What the top 2% know that everyone else does not

Andy Crowe, Alpha Project Managers: What the Top 2% Know That Everyone Else Does Not, Velociteach Press (2006).

10

8 key areas were identified where alpha project managers shine:

1. Attitude and belief2. Communication3. Alignment with the organization4. Approach and organization5. Priority management skills6. Issue Management7. Relationships and conflict8. Leadership

Page 11: Requirements Gathering: What Could Possibly Go Wrong?

Competencies

Paul, Yeates & Cadle (2010) p17

Page 12: Requirements Gathering: What Could Possibly Go Wrong?

Six Common Problems Faced By A Business Analyst

1. Resistance in sharing information

2. Irregular attendance

3. Accountability for decisions

4. Resolving user conflicts

5. Real needs vs. perceived needs

6. Changing needs

Source: BA Times Overcome?

Page 13: Requirements Gathering: What Could Possibly Go Wrong?

The Top Challenges Facing Business Analysts

Source: Business Improvement Architects

Page 14: Requirements Gathering: What Could Possibly Go Wrong?

Project Failures

Source: http://www.pmsolutions.com/collateral/research/Strategies%20for%20Project%20Recovery%202011.pdf

Survey (2011)

Page 15: Requirements Gathering: What Could Possibly Go Wrong?

Federal Bureau of Investigation

Page 16: Requirements Gathering: What Could Possibly Go Wrong?

US Census Bureau – Field Data Collection Automation (FDCA)

Page 17: Requirements Gathering: What Could Possibly Go Wrong?

Swedish Navy

Page 18: Requirements Gathering: What Could Possibly Go Wrong?

Why Projects Fail – Poor Requirements

• Most business requirements approaches fail on two dimensions1. Lack of a true process orientation

2. Lack of understanding of the neuroscience involved in requirements definition

Being asked what you want out of a system is like being asked what you want out of life! Where do you start? What are the parameters?

Page 19: Requirements Gathering: What Could Possibly Go Wrong?

Impact of Poor Requirements

If business analysts provide subpar requirements, it causes a wide range of negative consequences not only for the current project but for the business as a whole.

Page 20: Requirements Gathering: What Could Possibly Go Wrong?

Methodologies

Page 21: Requirements Gathering: What Could Possibly Go Wrong?

Business Analysis Body of Knowledge

…BABOK Guide…should not be construed as a methodology for the performance of business analysis.

(BABOK p6)

Page 22: Requirements Gathering: What Could Possibly Go Wrong?

BABOK = Panacea?

Page 23: Requirements Gathering: What Could Possibly Go Wrong?

BABOK – works “most of the time”

Source: BABOK p1

Page 24: Requirements Gathering: What Could Possibly Go Wrong?

Some Strategies (Austin, Runk, & Waters 2009)

Page 25: Requirements Gathering: What Could Possibly Go Wrong?

Some Strategies (Austin, Runk, & Waters 2009)

Source: http://delphi.com/pdf/techpapers/2009-01-0529.pdf

Page 26: Requirements Gathering: What Could Possibly Go Wrong?

Flaws

Page 27: Requirements Gathering: What Could Possibly Go Wrong?

Five common errors in requirements analysis

1. Customers don't (really) know what they want

2. Requirements change during the course of the project

3. Customers have unreasonable timelines

4. Communication gaps exist between customers, engineers and project managers

5. The development team doesn't understand the politics of the customer's organization

Source: http://www.techrepublic.com/article/five-common-errors-in-requirements-analysis-and-how-to-avoid-them

Page 28: Requirements Gathering: What Could Possibly Go Wrong?

SAME O' SAME O'.…

• Every project is different, but…• Same people• Same Team Lead• Same Project Manager• Same agendas• Same customs• Same needs

Negotiate – Polite – Change

Page 29: Requirements Gathering: What Could Possibly Go Wrong?

Lessons Learned

• What works in Manufacturing will not work in Finance• One-to-one interviews “brilliant”, especially if you want

to know a process• Workshops only work if you bring in people from all

departments• Use Visio for step-by-step walkthroughs• Use templates• Read legislation• Get on with the Project Manager• Know the issues, risks, and dependencies

Page 30: Requirements Gathering: What Could Possibly Go Wrong?

Learning from our mistakes

• “The hardest mistakes to learn from are those that lack consequence.” 

Jasper Sole

• “No one is exempt from the rule that learning occurs through recognition of error.” 

Alexander Lowen

Page 31: Requirements Gathering: What Could Possibly Go Wrong?

QQI Certificate in Business Analysis

• More information at:• www.businessanalyst.ie• www.ncirl.ie

Page 32: Requirements Gathering: What Could Possibly Go Wrong?

My Book

Business Systems Analysis

Analysis Tools

Problem Identification

Improvement Priorities

Identification

Decision Making

Process Identification

Resource Planning

Process Improvement

Controlling and Improving Processes

Performance Measurement

Benchmarking Performance

Importance/Performance

Requirements

Elicitation Analysis

www.theliffeypress.com

Page 33: Requirements Gathering: What Could Possibly Go Wrong?

Contact Me

[email protected]

@eoloughlin

www.eugeneoloughlin.com

www.youtube.com/eoloughlin

www.slideshare.net/eoloughlin

Page 34: Requirements Gathering: What Could Possibly Go Wrong?

Questions/Comments