bulletproof requirements for offshore projectsbaconvention.com/wp-content/uploads/2014/12/5...©...
Post on 03-Aug-2020
3 Views
Preview:
TRANSCRIPT
© 2014 BA Convention
Bulletproof Requirements for
Offshore Projects
Ashu Potnis
Content & images are Copyright TechnoSolutions Corp. © 2008-2014
© 2014 BA Convention 2
Why Bulletproof Requirements are Imperative for Project Success
A Quick Look at the Fundamentals
© 2014 TechnoSolutions Corp. 3
Click to edit Master text styles
Click to edit header
PROJECT
Requirements / Needs
Resources Time
Fundamental Factors of Project Management
© 2014 TechnoSolutions Corp. 5
Click to edit Master text styles
Click to edit header
Requirements - Foundation of Systems
Requirements are the very foundation of products, systems & applications
© 2014 TechnoSolutions Corp. 6
Click to edit Master text styles
Click to edit header
Cost of fixing Requirements Errors
Source: Boehm, Barry W., Software Engineering Economics : Study of 63 projects
from IBM, TRW, GTE etc.
Relative Cost for fixing Requirements Errors and
Omissions at different stages of the Project Lifecycle
200x
© 2014 TechnoSolutions Corp. 7
Click to edit Master text styles
Click to edit header
Discovery of Defects in the Project Lifecycle
Project Lifecycle
Rate
of
Dis
co
ve
ry o
f D
efe
cts
Requirements Design &
Build Release to Test
Release to Field
Common
Ideal
© 2014 TechnoSolutions Corp. 8
Click to edit Master text styles
Click to edit header
Requirements Analysis
Faithfully “communicate” user needs to all stakeholders
Needs
Business Analyst User
© 2014 TechnoSolutions Corp. 9
Click to edit Master text styles
Click to edit header
Who are these stakeholders?
Requirements
Business Users
Project Managers
Product Managers
Developers System
Architects
Quality Assurance
Peer Business Analysts
© 2014 BA Convention 10
Examining the unique requirements challenges in offshore projects
Peculiar Requirements Challenges
in Offshore Projects
© 2014 TechnoSolutions Corp. 11
Click to edit Master text styles
Click to edit header
Time Zone Difference
Problem? You can’t just ask questions or clarifications as and when you come across them
© 2014 TechnoSolutions Corp. 12
Click to edit Master text styles
Click to edit header
Language and Accent
© 2014 TechnoSolutions Corp. 13
Click to edit Master text styles
Click to edit header
Cultural Differences
© 2014 TechnoSolutions Corp. 14
Click to edit Master text styles
Click to edit header
Resource Mobility
• Employee Churn • Mobility of Resources
among Projects
Business Analyst Project Manager
Old Business Analyst
New Business Analyst
© 2014 TechnoSolutions Corp. 15
Click to edit Master text styles
Click to edit header
Challenges are compounded in Offshore Projects
Different Time Zones
Language and Accent
Cultural Differences
Resource Mobility / Non-Permanence
© 2014 BA Convention 16
Let’s Address the Problem
© 2014 TechnoSolutions Corp. 17
Click to edit Master text styles
Click to edit header
Typical Requirements Document
© 2014 BA Convention 18
Organizing Requirements to be easily understood
1. Structure Requirements for easy
consumption by all Stakeholders
© 2014 TechnoSolutions Corp. 19
Click to edit Master text styles
Click to edit header
Methods of Expressing Requirements
Requirements
Models &
Visual Requirements
Textual Requirements
Requirements
Documents can become
very large and difficult to
understand!
© 2014 TechnoSolutions Corp. 21
Click to edit Master text styles
Click to edit header
Requirements should be like an Onion!
© 2014 TechnoSolutions Corp. 22
Click to edit Master text styles
Click to edit header
…you peel it to get into the details!
Context Diagram
Use Case Diagram / Business Process Diagrams
Use Case Scenario
Use Story
Business Rules
Non-Functional Requirements
© 2014 TechnoSolutions Corp. 23
Click to edit Master text styles
Click to edit header
Structure Requirements in Layers
Context Diagram(s)
© 2014 TechnoSolutions Corp. 24
Click to edit Master text styles
Click to edit header
Context Diagrams
© 2014 TechnoSolutions Corp. 25
Click to edit Master text styles
Click to edit header
Structure Requirements in Layers
Context Diagram(s)
Business Process / Use
Case Diagrams
© 2014 TechnoSolutions Corp. 26
Click to edit Master text styles
Click to edit header
Business Process Diagrams
© 2014 TechnoSolutions Corp. 27
Click to edit Master text styles
Click to edit header
Use Case Diagrams
© 2014 TechnoSolutions Corp. 28
Click to edit Master text styles
Click to edit header
Requirements in Layers
Context Diagram(s)
Business Process / Use
Case Diagrams
Use Cases / User Stories
© 2014 TechnoSolutions Corp. 29
Click to edit Master text styles
Click to edit header
Use Case Scenarios
© 2014 TechnoSolutions Corp. 30
Click to edit Master text styles
Click to edit header
Activity Diagram for Scenario
© 2014 TechnoSolutions Corp. 31
Click to edit Master text styles
Click to edit header
User Story
© 2014 TechnoSolutions Corp. 32
Click to edit Master text styles
Click to edit header
Requirements in Layers
Context Diagram(s)
Business Process / Use
Case Diagrams
Use Cases / User Stories
Functional / Non-
Functional / Business
Rules
© 2014 TechnoSolutions Corp. 33
Click to edit Master text styles
Click to edit header
Detailed Textual Requirements
Textual Requirements
Functional Non-
Functional Business
Rules
Now that we have structured
requirements for easy consumption…
…how do we ensure that the Requirements truly
reflect user expectations?
I didn’t ask for that!
Communication Gap results in costly rework!
Application Delivered
© 2014 BA Convention 35
Are we Building the Right Thing?
2. Requirements Validation
© 2014 TechnoSolutions Corp. 36
Click to edit Master text styles
Click to edit header
Goal of Requirements Process
The main goal of the Requirements process is to establish a common understanding of the problem and its proposed solution among all
stakeholders
Requirements
Business Users
Business Analysts
Project Managers
Product Managers
Developers
System Architects
Quality Assurance
© 2014 TechnoSolutions Corp. 37
Click to edit Master text styles
Click to edit header
Requirements Visualization
From this…
…to this
Promote a common understanding of the
needs and the proposed solution
© 2014 TechnoSolutions Corp. 38
Click to edit Master text styles
Click to edit header
Screen Mockups
© 2014 TechnoSolutions Corp. 39
Click to edit Master text styles
Click to edit header
Conduct Application Walkthrough / Simulation
Visual Prototypes close the
communication gap
© 2014 TechnoSolutions Corp. 40
Click to edit Master text styles
Click to edit header
Visual Requirements Promote Understanding
Be more Visual (Diagrams)
“Show – not tell” (Application Prototypes)
Engage Users in reviews early in Project
© 2014 BA Convention 41
Important Sections of the Requirements Document
3.Factors that Impact the Project
Outcome but are Often Ignored
© 2014 TechnoSolutions Corp. 42
Click to edit Master text styles
Click to edit header
Assumptions
Assumptions are factors that are
believed to be true. Assumptions
may affect all aspects of the project
and pose a certain degree of risk if
they do not prove to be true.
Document assumptions to ensure that the “unsaid” things are formally documented.
© 2014 TechnoSolutions Corp. 43
Click to edit Master text styles
Click to edit header
Business Rules
Extract Business Rules and
maintain and independent catalog
of Business Rules.
Business Rules are very important for QA and are generally used across the system
© 2014 TechnoSolutions Corp. 44
Click to edit Master text styles
Click to edit header
Out-of-Scope
• Everyone documents what should
be done
• Equally important to identify
Requirements that are out of
scope. i.e. What won’t be done
© 2014 TechnoSolutions Corp. 45
Click to edit Master text styles
Click to edit header
Prioritize Requirements - MoSCoW
• Must be delivered
• Should be delivered
• Could be delivered
• Won’t be delivered
We always fall short of time, having prioritization helps put important things ahead of others.
© 2014 TechnoSolutions Corp. 46
Click to edit Master text styles
Click to edit header
Often Ignored Factors
Assumptions
Business Rules
Out-of-Scope
Requirements Prioritization
© 2014 TechnoSolutions Corp. 47
Click to edit Master text styles
Click to edit header
Summary
1. Structure Requirements for easy consumption by all Stakeholders
2. Validate Requirements
3.ConsiderOften Ignored Factors
© 2014 TechnoSolutions Corp. 48
Click to edit Master text styles
Click to edit header
Question & Answer Session
© 2014 BA Convention
Learn more. www.baconvention.com
Thank You!
top related