2009 - QS - HZ - RFP - OS FINAL

Capital One Request for Proposal:
Release Management, Software Configuration

Management, Test Data Management, and Test
Coordination Center services
Release Date:
March 2, 2009
RFP Point of Contact:

Charlie Flocco
Corporate Procurement
(804)284-9863
charles.flocco@capitalone.com
Statement of Confidentiality:
All information contained within this RFP package, as well as information which is
acquired by suppliers during the course of preparing a response to this Proposal, is
confidential and proprietary to Capital One. This information is provided for the
express purpose of preparing a Proposal and cost estimates. The information
contained within may not be used for any other purposes without the written
permission of Capital One. This information may only be disseminated to individuals
necessary for you to formulate your response.
Capital One Confidential 1

Section 1. Background
The intent of this RFP is to identify a key supplier who will engage with Capital One in
providing Release Management, Software Configuration Management, Test Data
Management, and Test Coordination Center services. Capital One seeks to engage
with the vendor in a “managed service” arrangement, and therefore supplier
responses should indicate:
• How the “measurable unit of work” will be identified and reported on to drive
cost of service and cost levers. Indicate the total cost for all services broken
out by service area via Measurable unit.
• Description of your on-site management techniques that will be provided for
these services.
• Which components of the service can be delivered on-site at Capital One vs.
utilization of off-site resources.
• How the vendor will manage increases or decreases in service scope as
business demand changes.
• How the vendor will allocate resources or time for Internal Projects,
Optimizations, service improvements, and automation while maintaining SLAs
for Scheduled or on-demand work.
The successful supplier will be able to provide services for all areas vs. a partial
solution.
Terms and abbreviations used in this document:

• CO: HP Service Desk Change Order
• CQ: ClearQuest
• HPSD: HP Service Desk (to be upgraded to HP Service Manager in 2009)
• KL: KnowledgeLink, which is the internal Capital One branding for the Livelink
implementation; KL is used as Capital One’s Enterprise document repository
• RM: Release Management
• SCM: Software Configuration Management
• SR&CM: Software Release & Configuration Management (name of both the
Capital One performing team and the service as known to Capital One
customers)
• TCC: Test Coordination Center
• TDM: Test Data Management
• WO: HP Service Desk Work Order

Section 2. Scope and Deliverables
Section 2.1: Release Management (RM) and Software Configuration

Management (SCM)
Section 2.1.1: Service Description
Deliver Software Release and Configuration Management (SR&CM) as a unified

service for IT changes arising from Business requests, as compliant with ITIL best
practices.
Additional background on current state:
RM and SCM Service

Organization Enterprise Processes Delivery
Capital One SR&CM team • Owns Enterprise • Service oversight
standards for RM for process
and SCM consistency
• Owns process • New service
documentation and engagement
artifact templates. customer
The team works interaction and
with other process stand-up
areas to ensure RM • Metrics and
and SCM integrate dashboard
properly with other reporting
key Capital One
processes
Vendor SR&CM team • Understands and • Deliver services for
comply with internal Capital One
Enterprise customers where
standards, they have been
processes and engaged (currently
artifact templates approximately 43%
when delivering the of registered
service business
applications)
General services responsibilities include the following:
• Ensuring consistency in service delivery across application portfolios,

including production and delivery of customer-facing artifacts. This includes
ensuring all required artifacts are collected and staged in the Enterprise
artifact repository appropriately as the service is delivered.
• Managing changes to systems and applications, including participating in
customer meetings, facilitating release scheduling and planning meetings,
and working with the customer to align changes with established release
dates, per the Release Strategy, to maintain the ongoing Release Schedule.
• Scheduling, planning and managing releases. This includes determining if a
detailed release plan is needed and, if so, managing development of the plan
and managing execution of release plan tasks.
• Managing code baselines in SCM tools via proper branching and merging
strategies as defined in the applicable Software Configuration Management

Plan (SCMP), performing builds and migrating code baselines to non-
production and pre-production environments (final migrations to the
production environment during releases is handled by a different
organization).
• Executing and complying with Capital One’s internal policies and procedures
around “change and configuration management”, including utilization of HP
Service Desk and HP Service Manager.
• Collecting operational measures and metrics for inclusion and roll-up to
portfolio and divisional monthly dashboards.
• Identifying, recommending and implementing automation improvements to
increase service efficiency.
• Escalating issues to the appropriate Capital One “Divisional Release Manager”
(assigned per division to oversee service delivery and consistency, and report
out on monthly dashboards).
Section 2.1.2 Service Deliverables
This section describes the specific service activities and deliverables, grouped by
SR&CM service function:
• New application onboarding (service expansion)
• Identifying and organizing business Requests for Change
• Prioritizing business Requests for Change
• Scheduling releases and release content
• Managing release implementations
Note that at the present time ClearQuest is heavily used to log requests for change,
produce release schedules and generate service metrics. The current plan is to
migrate from CQ to HP Service Desk in April, to deliver all aspects of the service from
HPSD and discontinue use of CQ.
Service Deliverables – New application onboarding:
Vendor
Capital One Vendor Tactical
Divisional Lead/Tactical Software
Service Release Release Configuratio Vendor
Component Manager Manager n Manager Analyst
Customer - Provide
initiation service
overview and
Q&A to
customer

Vendor
Complete - Assist - Act as SME to - Act as SME to
customer customer with identify identify
questionnaire completing estimated estimated
questionnaire number of number of
(identify scope releases per application
of portfolios, month baselines to
systems and create and test
applications) per month
- Identify
system and
application
relationships
and
interdependen
cies
Establish service - Develop - Provide QA - Provide QA
levels and costs proposal on on proposed on proposed
service levels service levels service levels
- Negotiate for RM for SCM
agreement on
service levels
- Determine
funding
requirements
Change - Identify data
Management sources and
flow of
Requests for
Change
- Negotiate
with customer
on integration
points and
which portions
to facilitate
- Identify
Business, BIO
and
Development
Owners
- Identify key
approvers
- Identify key
resources in
Dev, Test,
Environment
Mgmt, Support

Vendor
Process - Establish sub- - Provide info - Provide info - Clone
Preparation portfolios and sessions on sessions on standard CCB
related CCB’s the RM service the SCM Operating
- Determine and customer service and Procedures to
rosters for interactions for customer create new
communicatio customer interactions for artifacts
ns and stakeholders customer
meetings as needed stakeholders
- Assign tasks as needed
to create CCB
Operating
Procedures
- Chair initial
CCB’s and
introduce
Tactical RM
Data Preparation - Assess state - Perform tasks - Create or - Set up KL
of customer or oversee update SCMP’s folder
CI’s Config Champ as assigned infrastructure
Assign tasks to tasks to close for new
close CI CI gaps customer
registration or - Create or artifacts
relationship update release - Organize
gaps strategies as artifacts in KL
- Assess state assigned (Release
of Release - Identify Strategies,
Strategies and release SCMP’s, CCB
SCMP’s schedule for Operating
- Assign tasks new systems Procedures)
to close - Update
Release Customer
Strategy and Artifact
SCMP gaps Navigator

Vendor
Tool Preparation - Assess gaps - Configure - Enter CQ
in CQ setup SCM tools as release records
and coordinate needed (e.g., to represent
requests for create new the release
additional ClearCase schedule for
systems, VOB’s) new systems
groups and - Enter CQ
group enhancement
members records to
- Determine represent the
cycles and known change
schedules for backlog
generating CQ - Clone
reports and standard CQ
staging on KL reports to
represent
reports for new
sub-portfolios
and systems,
and identify
locations in KL
where reports
will be staged
Service Deliverables – Identifying and organizing business Requests for

Change:
Vendor
CCB Facilitation - Provide - Provide
oversight for oversight for
discussion and discussion and
registration of registration of
new Requests new Requests
for Change (or for Change
delegate to
Lead RM)
Change - Review - Enter data for
Registration Change new requests
Request into tracking
Backlog with tool
customer - Perform QA
on new
requests to
ensure all
required data
is available

Vendor
Strategy - Identify - Create or - Create or - Organize
Maintenance needs to update release update SCMP’s artifacts in KL
update strategies as as assigned
Release assigned
Strategy,
SCMP’s or CCB
Operating
Procedures,
based on
analysis of
portfolio health
and future
demand
drivers
- Assign
tactical tasks
to maintain
artifacts
Service Deliverables – Prioritizing business Requests for Change:
Vendor
CCB Facilitation - Provide
oversight for
prioritization of
new and
existing
Requests for
Change
Change Bundling - Provide
oversight for
bundling
approved,
prioritized
changes as
input to
release
scheduling

Vendor
Change - Review - Enter data
Maintenance Change changes for
Request existing
Backlog with requests into
customer tracking tool
- Perform QA
on data
changes to
ensure all
required data
is available
Service Deliverables – Scheduling releases and release content:
Vendor
CCB Facilitation - Conduct - Capture
regular meeting
portfolio or minutes and
system release action items
scheduling
meeting
Initiate Release - Negotiate on - Facilitate - Add/maintain
to Prod requested scheduling of release records
exceptions to changes and in CQ per the
regular release bundled agreed upon
scheduling per changes into release
the Release standard schedule
Strategy release - Associate
windows Enhancement
records to
Release
records in CQ
to automate
the Release
Schedule
- Publish
Release
Schedule

Vendor
Initiate Release - Determine - Perform QA - Perform CQ
to Non-Prod and release dates review of Pre- updates to
Pre-Prod based on Prod Prod and Non- incorporate
release date in Prod releases Non-Prod and
conjunction to identify any Pre-Prod
with standard build conflicts releases
T-minus - Publish
schedule per Release
the Release Schedule
Strategy
- Send Release
Comm on
schedule
decision
Manage Change - Address - Monitor - Update CQ
to Release escalations progress on associations to
Schedules and related to changes move content
Content negotiated scheduled for between
changes to release releases based
release - Send Release on
content and Comm if rescheduling
schedules schedule or decisions
content - Publish
change Release
- Negotiate Schedule
changes to
release
content and
schedules
based on: new
superseding
priorities,
failure to
achieve Dev or
Test
Conditions of
Satisfaction
according to
established T-
minus dates

Vendor
Manage Issues - Escalate - Identify RM - Identify SCM - Capture
and Risks issues to dependencies dependencies meeting
customer and associated and associated minutes and
management conflicts and conflicts and action items
as needed for risks; risks;
resolution determine determine
mitigation mitigation
plans if plans if
possible possible
- Facilitate
stakeholder
discussions to
resolve
conflicts
Deploy Release - Determine - Perform RM - Create
to Non-Prod and level of RM oversight tasks application
Pre-Prod oversight as assigned baselines:
required and - Send Release branch/merge
assign tasks to Comm on compilation;
Lead RM status of code technical
baseline support
deployment - Manage
baselines in
SCM tools
- Migrate code
between Non-
Prod and Pre-
Prod
environments
Service Deliverables – Managing release implementations:
Vendor
Divisional Lead/Tactical Software Vendor
Service Release Release Configuratio SR&CM
CCB Facilitation - Conduct - Capture
release meeting
planning minutes and
meeting to action items
confirm final
release
contents

Vendor
Prod Release - Respond to - Determine
Planning issue level of
escalation Release and
Rollback Plan
needed
- If needed,
develop and
validate
Release and
Rollback Plan
- If needed,
manage
completion of
Release Plan
tasks

Vendor
Prod Release - Provide QA - Obtain - Confirm - Stage key
Prep oversight of Testing Signoff release artifacts in KL
release - Obtain contents are
readiness customer synchronized
tasks as release with target
needed approval code baselines
signoff
- Obtain CCM
Operational
Documentatio
n from Dev
Leads
- Create and
schedule CCM
Change Orders
(against logical
ENV or SYS CI)
and Work
Orders
(against
physical PAPP
CI), and align
with Release
Plan if needed
- Oversee
movement of
CO’s/WO’s
through
reviews and
approvals
- Represent
CO’s/WO’s in
CAB
- Send Release
Comm on
release
readiness

Vendor
Deploy Release - Provide - Conduct - Stage key
to Prod implementatio release Go/No- artifacts in KL
n oversight Go decision
and respond to - Oversee
issue completion of
escalation as WO tasks
needed - Oversee
completion of
release
validation by
technical team
and customer
team
- Manage CCM
process for
Emergency
Changes, if
needed
- Send Release
Comm on
release
completion
disposition
Section 2.1.3: Required Skills
• Release Management:
o Understanding of ITIL Change and Release Management
o Project Manager skills to organize tasks across multiple performers,
including sequencing tasks based on dependencies and contingencies
o Process skills to understand and comply with processes currently in
place, and ability to apply critical thinking to identify and propose
process improvements (achieve greater efficiency or leverage
automation)
o Communication skills including written and oral statuses to senior
management, and ability to integrate with customers and performers
across multiple teams
o Analytical skills to derive impact assessments from proposed
application changes
o Tools: HP Service Desk and Service Manager, Microsoft Project and
Office
• Software Configuration Management:
o Understanding of SCM best practices including version baselining,
branching, merging and conflict resolution
o Ability to provide automation of manual processes where identified
o Tools: ClearCase, Ab Initio EME, STAT!, ChangeMan, Visual Source Safe,
CVS, TeamSite, KnowledgeLink
Section 2.1.4: Service Scope

Current Service Scope
The current scope of SR&CM services includes approximately 700 applications that
range in complexity, platform and release frequency. Current monthly metrics by
major portfolio are as follows (“n/a” indicates where the service has not been
procured):
Serviced Software
Portfolio Total Apps Apps Builds* Releases*
Bank 469 21 n/a <5
BTS 337 13 20 10
Card 286 196 825 105
COAF 383 383 150 n/a
eCommerce 50 38 120 100
ETO 26 3 n/a <5
ITRO 22 13 5 5
* For serviced apps only
Software builds range from 1-4 hours depending on complexity and automation.
Releases range from 2-16 hours depending on complexity (approximately 12 hours

per release on average including work to plan, schedule, implement and
communicate).
Anticipated Service Scope

The scope of services is expected to increase over the next 2 years and bidder
responses should describe how service delivery and associated costs will scale
accordingly:
• 2009:
o Service scope is anticipated to expand to approximately 900-1000
applications.
o Service scope may expand to include all IT infrastructure change (e.g.,
servers, firewalls), as Capital One is exploring the rollout of RM
practices to all changes. Currently there are approximately 15,000
non-software application changes per month (for comparison, there are
approximately 1,200 software application changes per month).
Bidders should provide a supplemental cost structure to
indicate how services and costs will scale to support this
potential increase.
• 2010: the SR&CM team should be positioned to acquire all applications in the
Enterprise (approximately 1,600). In addition to simply expanding team size,
to accomplish service growth the SR&CM team will continue to drive process
maturity in customer areas through Release Strategies to bundle changes
more effectively, and align change events at the system, portfolio and
business process levels to reduce the overall number of release events.

Section 2.2: Test Data Management (TDM)
• Data Conditioning
o Create and maintain test data for use in new functionality, integration,
regression, and system performance testing.
o Test data is often maintained in a ‘test-ready’ state for regression
testing using predefined requirements aligned with test cases. These
‘Test Data Optimizations’ are service improvement projects carried out
in collaboration with TDM customers to automate data conditioning.
o The strategy for Test Data Conditioning and Test Data Optimizations is
defined by the TDM service manager.
• NPI Data Scrubbing
o Ensure test data and methods employed meet Capital One Information
Security standards and GrammLeachBliley (GLB) Act requirements for
customer data protection.
o Use of standard data transformation tools to anonymize production
data (strategic data, customer personal data, associate personal data)
before loading into pre-production environments.
o This service requires on-site staff due to controlled access to
production data containing customer information.
Section 2.2.2: Service Deliverables
The Test Data Management service consists of two types of deliverables : On

Demand Requests and Project Requests. The typical mix of time spent is 60% on On-
Demand requests and 40% on Project requests.
On Demand Requests are typically predefined types of work requests that the team
fulfills. These mix of these requests rise and fall each month based on investment
project demand.
Range
of Average
request hours
s per per Level
Request Type month request Skills Required Required
TS2 Data 4-8 3 Windows, unix, MS Intermediate
Identification Office, relational
database knowledge
Database Data 40-60 5 Ab Initio, unix, Intermediate
Movement w/ data relational database
scrubbing knowledge
TS2 25 - 30 1 Windows, unix, MS Intermediate
Account/Transaction Office, relational
Creation database knowledge
Database/Transactio 30 - 60 1 Windows, unix, MS Intermediate
n Loads Office, relational
database knowledge
Simple Data 20 - 30 3 Windows, unix, MS Intermediate

Conditioning Office, relational
database knowledge
Complex Data 6-8 24 Windows, unix, MS Intermediate
Conditioning Office, relational
database knowledge
Simple Data/File 15 - 40 4 Windows, unix, MS Entry
Maintenance Office, relational
database knowledge
Complex Data/File 4-6 12 Windows, unix, MS Intermediate
database knowledge
Database 50 - 80 1 Windows, unix, MS Intermediate
database knowledge
Optimization 10 - 12 8 Windows, unix, MS Intermediate
database knowledge,
QTP
Account 4 2 Windows, MS Office Entry
Management
Reporting
Required Skills in support of On-Demand Requests
• Translation of business requirements into technical results

• Ability to validate quality of test data conditioning results and take action to
resolve discrepancies
• Ability to multi-task for handling several customer requests at once
• Strict adherence to standards regarding handling of confidential and sensitive
data
• Customer service mentality that supports collaboration
• Follows IT processes for service requests and works through process
breakdowns to deliver results
• Design, code, test, implement simple database scripts for data manipulation
• Coordinates work with customers and other IT groups to resolve issues
Project Requests are part of the delivered service and are undertaken to automate
manually executed tasks or for general service improvements to deliver test data
faster and cheaper. They can be either self-identified by the TDM team or by
customers. Projects are first aligned with the Test Data Optimization strategy and
are managed through to completion by the TDM service manager. These projects are
staffed by the team as permitted by the level of On-Demand requests.
Project requests are typified as the identification of test case-level data

requirements, design of an application using either existing technology skills on the
team or acquiring new skills , implementation of the solution, validation against the
requirements by the customer, and creation of operational documentation for ease of
knowledge transfer.

Typical range of
Request Type hours to deliver Skills Required Level
Set up of ‘small’ 20 to 60 hours Ab Initio, unix, Intermediate
test data DB2, Oracle, SQL
conditioning on Server, Teradata,
TSYS platform or MVS, QTP
Capital One
database
Set up of ‘large’ 60 to 400 hours Ab Initio, unix, Senior
test data DB2, Oracle, SQL
conditioning on Server, Teradata,
TSYS platform or MVS, QTP
Capital One
database
Automation of 80 to 400 hours Ab Initio, unix, Intermediate and
data moved DB2, Oracle, SQL Senior
through QA Server, Teradata,
environment MVS
integrated with
NPI data
scrubbing
Required Skills in support of Project Requests
• Translation of business requirements into technical solutions

• Creation of operational documentation
• Follow software lifecycle development methodology
• Strict adherence to standards regarding handling of confidential and sensitive
data
• Manage the version control needs for software assets
• Ability to validate quality of test data conditioning results and take action to
resolve discrepancies
• Design, code, test, implement complex database scripts and Extract-
Transform-Load (ETL) applications for data manipulation
• Monitor existing application performance and implement measures to improve
performance
• Troubleshoot application technical problems and lead efforts to resolve
• Coordinates work with customers and other IT groups to resolve issues

Section 2.3: Test Coordination Center (TCC)
• Provide metrics and reporting to the Enterprise on a variety of Quality

Assurance dimensions
• Support Control and Standard Testing for Investment Shared Services by
producing reports and data
• Develop and Maintain Management reports using an automated reporting tool
(IR 11)
The typical mix of time spent is 70% on Standard Requests such as Project reporting
and 30% on the development of the automated reports and other ad hoc requests.
Section 2.3.2: Service Deliverables
Project and Ad Hoc Requests:

Request Type Range of Range of Skills Required Skill Level
Average # Average
of hours per
requests request
per month
Project Reporting 2-5 20- 30 Windows, MS Intermediate
Setup Office, relational
database
knowledge
Project Reporting 5 - 15 20 – 60 Windows, Excel, Intermediate
MS Access, to Junior
relational
database
knowledge, VBA
Program Reporting 1-2 100 – 140 Windows, Excel, Intermediate
MS Access,
relational
database
knowledge, VBA
MBR Reporting 10 – 15 2–4 Windows, Excel, Junior
MS Access,
relational
database
knowledge, VBA
Ad Hoc Requests – 10- 20 10 - 20 Windows, Excel, Intermediate
Includes Optimizations MS Access,
and Service relational
Improvement database
initiatives knowledge, VBA
• Leverages Data from Testing system of record to produce reports for Projects
and programs on a daily or weekly basis depending on the project needs.
Reports include:
o Initial Setup
o Test Planning Report
o Test Execution Status

o Defect Trending
o Requirements Traceability
o Misc Custom views
o Project Work may flex up and flex down depending on what projects
are currently active in the enterprise.
o After initial setup of Metrics Reports should be automated and easily
produced for projects in-flight
• On a monthly basis provides metrics for Monthly Business Reviews. These
metrics include:
o Tests Executed by Category (New Functionality vs Regression)
o Defects Found by Phase and Severity
o All Grouped by LOB and Business Assurance Risk
• Create or enhance Management Reports using automated Reporting tools
(Currently BRIO moving to IR 11)
o Requirements for reporting will be developed based on Customer
Requests
o Leverages Testing System of Record and Data Mart to present Graphs
and Tables with the data requested
• Ad Hoc Reporting
o Pulls data together from Datamart or system or record for ad hoc
requests that are not currently covered by other reports available
o Identifies if ad hoc request should become part of the standard reports
available in the above section on Management Reports
o Provides Optimization work as means of driving towards service
improvements or enhancing service offerings
• Supports the Control Testing on a Quarterly basis
o Accountable for controls and standards adherence testing for the
Investment Shared Services organization
Section 2.3.3: Required Skills
• Proficient with writing SQL statements

• Hands On experience with MS Access, Excel, Visual Basic for Applications
(VBA) and , PowerPoint
• Experience with Database design in Oracle and/or MS Access
• Strong written and verbal communication skills
• Solid Problem solving skills, able to indentify data discrepancies and solve the
reasons for those discrepancies
• Experience with BRIO, Hyperion, or Oracle IR 11 reporting tools (or other
similar products)

Section 3. RFP Process & Timeline
March 2, 2009 • Request for proposal dispatched to bidders
March 4, 2009 • Bidders’ Intent to Respond to be emailed to

charles.flocco@capitalone.com no later than
1pm.
• In this Intent submission email, please confirm
your firm's POC.
March 6, 2009 • Conference call with Capital One for bidder
Q&A session.
March 20, 2009 • Bidders RFP Status Check in (exact times
TBD)
March 27, 2009 • Proposals due by 1pm.
• Proposal Submittal Requirements
o See Section 4 below for additional RFP
requirements.
o In a single email, email all proposal
documentation to
charles.flocco@capitalone.com
o The total size of the documents/email
being submitted must not exceed 8MB
and cannot contain zipped files (COF
firewall requirements).

Section 4. Proposal Requirements
Section 4.1: Proposal Content
Include in your response answers to the following questions:
General questions applicable to all service areas:

• Describe how your firm performs background checks on potential workers.
• If proposing an off-shore component or model, please indicate whether your
firm has met Capital One Information Protection standards and passed an
Information Technology Risk Office audit.
• Please described your proposed staffing model for each segment and detail on
a cost/hr. basis behind the overall fixed price proposed
• Please describe activity drivers behind pricing scenarios and how pricing is
proposed to change based on changes in activity drivers
• Describe how SLA's would be communicated to the supplier resources and
enforced.
• Detail proposed SLA penalty mechanism(s)
• Describe how new resources are trained.
• Describe how you will execute knowledge transfer and timeframe required.
• Describe how new tasks are added to the service agreement.
• Describe how increases or decreases in demand are handled.
• Describe typical status reporting to client management.
• Provide up to three references where these types of services have been
performed before.
• Describe your experience with following database platforms : DB2, Oracle,
SQLServer, Teradata.
• Describe your experience with following operating systems : Unix, MVS,
Windows, Linux.
• Describe your experience with following tools :Ab Initio, QTP, QualityCenter,
HP Service Desk.
• Describe the personal productivity tools you provide to your resources.
Specific questions related to Software Release and Configuration Management:

• Describe your firm’s methodology or process framework related to Change or
Release Management.
• For the following key artifacts describe the content and usage (from your
firm’s perspective):
o Software Configuration Management Strategy or Plan
o CCB (Change Control Boards or Change Advisory Board) Operating
Procedures
o Release Strategy
o Release Plan
Specific questions related to Test Data Management

• Describe your experience with the anonymization of customer data to comply
with Gramm Leach Bliley Act of 1999.
Specific questions related to Test Coordination Center

• Describe your experience with creating metrics reports and providing data
analysis on those reports

Section 4.2: Proposal Format
Incorporate responses to the above service scope, objectives,

requirements and deliverables into a draft SOW. Please use the
following or other approved SOW format:
G:\1 RFP Tools\

SOW_Template_Nov2007.doc

2009 - QS - HZ - RFP - OS FINAL

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

2009 - QS - HZ - RFP - OS FINAL

Загружено:

Авторское право:

Доступные форматы

Capital One Request for Proposal:

Release Management, Software Configuration

RFP Point of Contact:

Capital One Confidential 1

Terms and abbreviations used in this document:

Capital One Confidential 2

Section 2.1: Release Management (RM) and Software Configuration

Deliver Software Release and Configuration Management (SR&CM) as a unified

Additional background on current state:

RM and SCM Service

General services responsibilities include the following:

• Ensuring consistency in service delivery across application portfolios,

Capital One Confidential 3

Section 2.1.2 Service Deliverables

Service Deliverables – New application onboarding:

Capital One Confidential 4

Capital One Confidential 5

Capital One Confidential 6

Service Deliverables – Identifying and organizing business Requests for

Capital One Confidential 7

Service Deliverables – Prioritizing business Requests for Change:

Capital One Confidential 8

Service Deliverables – Scheduling releases and release content:

Capital One Confidential 9

Capital One Confidential 10

Service Deliverables – Managing release implementations:

Capital One Confidential 11

Capital One Confidential 12

Capital One Confidential 13

Section 2.1.3: Required Skills

Section 2.1.4: Service Scope

Capital One Confidential 14

Releases range from 2-16 hours depending on complexity (approximately 12 hours

Anticipated Service Scope

Capital One Confidential 15

Section 2.2.2: Service Deliverables

The Test Data Management service consists of two types of deliverables : On

Capital One Confidential 16

Required Skills in support of On-Demand Requests

• Translation of business requirements into technical results

Project requests are typified as the identification of test case-level data

Capital One Confidential 17

Required Skills in support of Project Requests

• Translation of business requirements into technical solutions

Capital One Confidential 18

• Provide metrics and reporting to the Enterprise on a variety of Quality

Section 2.3.2: Service Deliverables

Project and Ad Hoc Requests:

Capital One Confidential 19

Section 2.3.3: Required Skills

• Proficient with writing SQL statements

Capital One Confidential 20

March 2, 2009 • Request for proposal dispatched to bidders

March 4, 2009 • Bidders’ Intent to Respond to be emailed to

Capital One Confidential 21

Section 4.1: Proposal Content

Include in your response answers to the following questions:

General questions applicable to all service areas:

Specific questions related to Software Release and Configuration Management:

Specific questions related to Test Data Management

Specific questions related to Test Coordination Center

Capital One Confidential 22