Caught in a COTS Project - Strategies for Requirements Success 2011MAY17
-
Upload
michael-roy -
Category
Documents
-
view
31 -
download
0
Transcript of Caught in a COTS Project - Strategies for Requirements Success 2011MAY17
Caught in a COTS Project ? Strategies for Requirements Success
Michael Roy
Requirements Practitioner/Coach
© 2011 Michael R Roy All Rights Reserved. © 2011 Michael R Roy All Rights Reserved.
To understand what a COTS project is and how
it differs from a regular project
To recognize requirement problems that are
common to a COTS project
To learn strategies that lead to success on a
COTS project
Session Objectives
2
© 2011 Michael R Roy All Rights Reserved.
Introduction
4
Michael Roy is an experienced requirements
professional. For more than 20 years, he has
been directly involved in the facilitation,
documentation and development of business
functional and systems requirements. He has a
passion for business analysis and helping others
flourish in the profession.
http://ca.linkedin.com/in/michaelrroy
© 2011 Michael R Roy All Rights Reserved.
Qualifications
5
Direct experience in a requirements role on multiple projects
implementing vendor products:
suspense account reconciliation system
accounting system implementation
global replacement of HR systems
Pragmatic, real-world COTS experience
© 2011 Michael R Roy All Rights Reserved. 6
Target Audience
Intermediate: Prior requirements knowledge and experience
presumed
© 2011 Michael R Roy All Rights Reserved.
Characteristics of a COTS product
1. Sold, leased, or licensed to the general public
2. Offered by a vendor trying to profit from it
3. Available in multiple, identical copies
4. Supported and evolved by the vendor, who retains the intellectual property rights
5. Used without modification of the internals
What is a COTS product ?
Source: SEI, CMU/SEI-2003-TR-017
9
© 2011 Michael R Roy All Rights Reserved.
Examples of COTS Products
Oracle
PeopleSoft SalesForce
SAP
Workday
Includes SaaS Products
Includes ERP solutions
10
© 2011 Michael R Roy All Rights Reserved.
What is a COTS Project ?
The term COTS project refers to a project that combines
existing commercial product(s) and other software to create a
new client system.
COTS projects are rarely labeled with the term „COTS‟; you
may have worked on a COTS project without knowing the
term applied. If you worked on installation of a enterprise
product not built in-house, you likely have worked on a COTS
project.
A COTS project is sometimes not considered a project but
rather an integration and implementation effort.
12
© 2011 Michael R Roy All Rights Reserved.
What makes a COTS project different?
13
Solution to a business need is determined up front
Upfront selection of the solution (product) is based on an
Request for Proposal (RFP)
RFP is generally written with requirements captured at
a high level (features)
RFP is often a checklist document
Vendor selection is based on an affirmation of feature
compatibility, possibly a demonstration, and multiple
assumptions
Different actors in the project environment (vendor or
product configuration team)
© 2011 Michael R Roy All Rights Reserved.
What makes a COTS project different?
14
Low visibility to product internals
Product configuration is a shared responsibility between
vendor product experts and internal resources
Strong emphasis on glue code (integrations) and conversion
tasks
Aggressive timelines (think “Death March” projects)
Configuration focus, not customization
© 2011 Michael R Roy All Rights Reserved.
Configuration vs. Customization
15
Configuration Configurable means the existing
software can be worked (via a
standard user interface) to reflect a
change
Configurations are made by using
tool sets built into the product
(No changes to software code)
Customization Customization means the
underlying software code has to be
changed so it can do what you
want it to
Changing code means the product
is now unique – different from
every other installation. (This can
cause problems with upgrades and
maintenance.)
© 2011 Michael R Roy All Rights Reserved. 17
Common Requirement Problems on a COTS Project
Lines of responsibility and accountability for requirements
are blurred
© 2011 Michael R Roy All Rights Reserved. 18
The Traditional Business Analyst Model
Business Development
Business Analyst
Let me find out what they want
© 2011 Michael R Roy All Rights Reserved. 19
Lines of responsibility and accountability for requirements are blurred
Common Requirement Problems on a COTS Project
© 2011 Michael R Roy All Rights Reserved. 20
Mismatch between the needs of the project and boilerplate
deliverables
Common Requirement Problems on a COTS Project
© 2011 Michael R Roy All Rights Reserved. 21
Mismatch between the needs of the project and boilerplate deliverables
Common Requirement Problems on a COTS Project
© 2011 Michael R Roy All Rights Reserved. 22
Gaps in understanding are leftover when using only
prescribed requirement techniques
Common Requirement Problems on a COTS Project
© 2011 Michael R Roy All Rights Reserved. 23
Prescribed techniques focus on requirements from a gathering
perspective
Common Requirement Problems on a COTS Project
© 2011 Michael R Roy All Rights Reserved. 24
Gaps in understanding are leftover when using only prescribed techniques
Where are my business rules ?
Common Requirement Problems on a COTS Project
Common Problems on a COTS project include:
© 2011 Michael R Roy All Rights Reserved. 25
Lines of responsibility and accountability are blurred
Mismatch between the needs of the project and boilerplate deliverables
Gaps in understanding are leftover when using only prescribed techniques
SUMMARY
Common Requirement Problems on a COTS Project
© 2011 Michael R Roy All Rights Reserved. 26
Unique ? No
Frequency is much higher and extent of
these problems are more accentuated
© 2011 Michael R Roy All Rights Reserved. 27
Using a paint-by-numbers approach for
business analysis is a recipe for failure when
working on a COTS project
© 2011 Michael R Roy All Rights Reserved. 30
Strategies for Success on a COTS Project
Customize the analyst engagement model
© 2011 Michael R Roy All Rights Reserved. 31
Understand the lineup of stakeholders in the requirements arena
Customize the Analyst Engagement Model
Strategies for Success on a COTS Project
© 2011 Michael R Roy All Rights Reserved. 32
Clarify requirements related roles and responsibilities
Customize the Analyst Engagement Model
Strategies for Success on a COTS Project
© 2011 Michael R Roy All Rights Reserved. 33
Typical outcome is move from requirements communication
conduit to facilitation and coordination
Strategies for Success on a COTS Project
Customize the Analyst Engagement Model
© 2011 Michael R Roy All Rights Reserved. 34
Strategies for Success on a COTS Project
Tailor the deliverables approach
© 2011 Michael R Roy All Rights Reserved. 35
Think Iteration
Tailor the Deliverables Approach
Deliverable
Client Feedback
Update Deliverable
Strategies for Success on a COTS Project
© 2011 Michael R Roy All Rights Reserved. 36
Think Innovation
Strategies for Success on a COTS Project
Tailor the Deliverables Approach
© 2011 Michael R Roy All Rights Reserved. 37
Think Shared Ownership
Strategies for Success on a COTS Project
Tailor the Deliverables Approach
© 2011 Michael R Roy All Rights Reserved. 38
Strategies for Success on a COTS Project
Leverage COTS friendly requirement techniques
© 2011 Michael R Roy All Rights Reserved. 39
Leverage Gap Analysis to ensure completeness and accuracy
Leverage COTS friendly requirement techniques
Strategies for Success on a COTS Project
© 2011 Michael R Roy All Rights Reserved. 40
Leverage Business Rules to support product configuration
Leverage COTS friendly requirement techniques
Source: Fairly Odd Parents, Nickelodeon © 2001
Strategies for Success on a COTS Project
© 2011 Michael R Roy All Rights Reserved. 41
Leverage Event Models to support product configuration
Leverage COTS friendly requirement techniques
Strategies for Success on a COTS Project
© 2011 Michael R Roy All Rights Reserved. 42
Customize the analyst engagement model
Tailor the deliverables
approach
Leverage COTS friendly
requirement techniques
SUMMARY
Strategies for Success on a COTS Project
© 2011 Michael R Roy All Rights Reserved. 44
The Not So-Secret Weapon
Behold …. The mighty Business Analysis Plan
© 2011 Michael R Roy All Rights Reserved.
Learning Objectives Revisited
© 2011 Michael R Roy All Rights Reserved.
Identify what a COTS project is and understand
how it differs from a regular project
List common requirement problems on a COTS
project
Understand changes to consider when engaged
on a COTS project
Can you now …….
46
© 2011 Michael R Roy All Rights Reserved.
Credits
© 2011 Michael R Roy All Rights Reserved.
Image Source(s):
FreeDigitalPhotos.net
jscreationzs
luigi diamonte
Paul Martin Eldridge
Arvind Balaraman
Paul
Filomena Scalise
Gregory Szarkiewicz
renjith krishnan
PresentorMedia
47