Windows XP Migration Project Plan

Dan Thomasson
dthomasson@carolina.rr.com
TS5120 Project Management
March 24, 2004

Table of Contents
1. Executive Summary.
2. Definitions, Acronyms, and Abbreviations
3. Project Overview..
3.1. Business Case..
3.2. Windows XP Migration Benefits
3.2.1. Better Performance..
3.2.2. Enhanced Security
3.2.3. Better Mobile Experience
3.2.4. Real-Time Communications
3.2.5. Return on Investment...
3.3. Project Charter
3.3.1. Project Objectives
3.3.2. Project Budget Information..
3.3.3. Project Approach..
3.4. Project Roles and Responsibilities..
3.4.1. Roles and Responsibilities...
3.4.2. Responsibility Assignment Matrix...
4. Team Contract..
4.1. Code of Conduct.
4.2. Participation
4.3. Communication...
4.4. Problem Solving..
4.5. Meeting Guidelines.
5. Scope Statement...
5.1. Project Justification.
5.2. Product Characteristics and Requirements.
5.2.1. Minimum requirements to Use Windows XP Professional.
5.2.2. Additional Items or Services Required to Use Certain Windows XP Features...
5.3. Summary of Product Deliverables..
5.3.1. Project Management-Related Deliverables..
5.3.2. Product-Related Deliverables..
5.4. Milestones ..
5.5. Work Breakdown Structure
6. Contingency Plan.
7. Risk Plans.
7.1. Risk Management Plan...
7.2. Risk Response Plan.
7.3. Top Ten Risks in Information Technology.
7.4. Risk Assessment Matrix..
8. Project Communication Plan..
9. Quality Management Plan..
9.1. Quality Planning
9.1.1. IEEE 829..

4
5
5
5
6
6
6
6
6
7
7
7
7
7
8
8
9
11
11
11
11
11
11
12
12
12
12
12
14
14
14
15
16
17
17
17
17
17
18
18
20
20
20

9.1.2. Capability Maturity Model...

9.1.3. ISO 9001..
9.2. Quality Assurance...
9.2.1. IEEE 730..
9.2.2. IEEE Stoneman
9.3. Quality Control...
9.3.1. Monitoring Project Progress
9.3.2. IEEE 1028
9.4. Testing.
10.Cost and Benefit Analysis ..
10.1. Cost of Project Resources.
10.2. Benefits.
11. Project Sign-Off.
Appendix 1: Business Case for Project Name...
Appendix 2: Business Case for Financials.
Appendix 3: Project Charter..
Appendix 4: Project Name/Kick-off Meeting
Appendix 5: Scope Statement
Appendix 6: Weekly Status Report
Appendix 7: Milestone Report for Project Name..
Appendix 8: Quality Assurance Plan for Project Name
Appendix 9: Client Acceptance/Project Completion Form...
Appendix 10: Team Contract.
Appendix 11: Software Project Management Plan for Project Name
Appendix 12: Windows XP Migration Intranet Web Site
Appendix 13: IEEE Standards for Information Technology.
References..

20
20
21
21
21
21
21
21
22
22
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
39

Tables
Table 1: Roles and Responsibilities...
Table 2: Responsibility Assignment Matrix...
Table 3: Project Schedule.
Table 4: Milestones...
Table 5: Risk Assessment Matrix..
Table 6: Communication Plan..
Table 7: Windows XP Migration Cost Analysis

8
9
10
15
18
19
24

Figures
Figure 1: Work Breakdown Structure... 16
Figure 2: Testing Process. 22

1. Executive Summary
Bank of America has just incorporated 60,000 new employees with the merger of Fleet
Boston. Many of the banks long-time employees, and newly acquired employees, work on
various types of hardware (laptops and desktops) with different operating systems. The CEO of
Technology and Operations within the bank recognizes a need to consolidate all the different
operating systems down to only one: Microsoft Windows XP. His vision is to reduce processes,
cut costs, and follow Six Sigma to the letter. With his support, and the support of other senior
managers and business managers, a budget was set aside for the testing and migration of
Windows XP to all bank PCs. Therefore, a project needed to be created to realize his vision.
The purpose of the Windows XP Migration project is to bring about more PC security and
reliability by upgrading all desktop and laptop computers within Differentiated Service Platform
Engineering at Bank of America with one supportable operating system.

2. Definitions, Acronyms, and Abbreviations

AI Application Integration a software-packaging group that combines the application
source code into Microsoft Windows Installer (MSI) packages for software distribution
Baseline the original project plan plus approved changes
CM Change Management - generally includes management of the requirements and
functional specifications including policy, rules, procedures, information, activities, roles
authorization levels, and states relating to the creation, updates, approvals, tracking and
archiving of change requests and problem reports
CMM Capability Maturity Model a five-level model (1. Initial, 2. Repeatable, 3.
Defined, 4. Managed, and 5. Optimizing) laying out a generic path to process
improvement for software development organizations
Contingency Plans predefined actions that the project team will take if an identified
risk event occurs
Gantt Chart a standard format for displaying project schedule information by listing
project activities and their corresponding start and finish dates in a calendar format
IEEE Institute of Electrical and Electronics Engineers - a professional and technical
association that spans the globe with members representing nearly 50% of the worlds
individual countries. IEEE develops technical standards for computer engineering,
telecommunications, aerospace, software testing and quality, along with many other
technical arenas. See Appendix 13: IEEE Standards for Information Technology.
ISO International Organization for Standardization - provides over 13,700 International
Standards for business, government and society. ISO is a network of national standards
institutes in nearly 150 countries, and has a central location in Switzerland.
4

Milestone a significant event on a project with zero duration

PMBOK Project Management Body of Knowledge an inclusive term that describes
the sum of knowledge within the profession of project management
QA Quality Assurance periodically evaluating overall project performance to ensure
the project will satisfy the relevant quality standards
RAM Responsibility Assignment Matrix a matrix that maps the work of the project as
described in the WBS to the people responsible for performing the work as described in
an organizational breakdown structure
RM Release Management - the person responsible for the definition, tracking and
distribution of a product release
SD Software Distribution the delivery mechanism for distributing the completed
(developed and tested) software packages to the desktop
Six Sigma a comprehensive and flexible system for achieving, sustaining, and
maximizing business success that is uniquely driven by close understanding of customer
needs, disciplined use of facts, data, statistical analysis, and diligent attention to
managing, improving, and reinventing business process
Stakeholders people involved in or affected by project activities
SWBOK Software Engineering Body of Knowledge - an IEEE Stoneman (version 0.7)
standard for software developers and testers
WBS Work Breakdown Structure a deliverable-oriented grouping of the work
involved in a project that defines the total scope of the project

3. Project Overview
3.1. Business Case
Differentiated Service at Bank of America supports five different client operating
systems, and also supports over 78,000 employees. Security, reliability, and remote
troubleshooting of all five operating systems are extremely costly. With the Windows XP
Migration Project, the bank is seeking to reduce support costs while enhancing the user
computing experience. By consolidating the five operating systems down to one, Windows XP,
this project expects to provide savings in deployment at more than 60 percent, and overall
operating-cost savings at 22 percent per year (yielding a savings of over $330,000 per year) over
the next four years.

Maintaining and supporting multiple operating systems among offices worldwide is a

challenge. In order to maintain the required level of reliability and security demanded by todays
software applications and the Internet, reduction in complexity is a must. To keep support costs
at a reasonable level, uniformity (oneness) needs to be increased.
Besides the aforementioned reasons for migrating to Windows XP for the bank, there are
additional benefits.
3.2. Windows XP Migration Benefits
3.2.1. Better Performance
The bank's vision is to have "oneness" across all departments, and that includes using the
same operating system. Migrating to Windows XP will bring Differentiated Service up to speed
with the most current operating system. Windows XP offers superior performance in comparison
to Windows 2000 and all other versions of Windows. Not only does it boot and resume quickly,
it's also highly responsive when switching applications, starting new applications, and running a
wide variety of workloads. The performance improvements may seem incremental, but combined
they will deliver a much faster experience for the user.
3.2.2. Enhanced Security
Mobile computing and Internet communications have come at a cost - exposing
businesses to increasing security risks. Windows XP offers robust security features with the aim
of protecting sensitive data and providing support for managing users on the network. An
important feature of Windows XP is the Encrypting File System (EFS) that protects sensitive
data files and now works with Offline Files and Folders. Windows XP supports the latest security
standards and enhanced virus protection, protecting from some of the more common types of
Internet attack.
3.2.3. Better Mobile Experience
Enhanced wireless support is also a significant development with Windows XP. This new
operating system provides Zero Configuration support, allowing a laptop with a wireless adapter
card to automatically detect and connect to wireless access points that are within range. As highspeed wireless networks become more commonplace within corporate environments, airports
and hotels, this ease of connection will be essential, enabling remote users to stay productive,
regardless of their location.
3.2.4. Real-time Communications
Differentiated Service needs the flexibility to communicate using a number of
technologies in a seamless fashion. Windows XP includes support for real-time voice and video
communications, instant messaging and online collaboration, now fully integrated as Windows
Messenger. This enables users to communicate with their colleagues, customers and partners in
real-time using text, audio, video and other collaborative tools. Real-time communications will

extend to Pocket PCs, mobile phones, and other smart devices enabling more flexible working.
3.2.5. Return on Investment
Significant improvements to reliability, performance, and manageability witnessed in
Windows XP will ensure it offers an equal, if not better, return on investment compared to
Windows 2000.
Once all workstations are in line with one operating system (Windows XP), "oneness" for
the bank will finally be achieved. To put this project into action, a Project Charter must be
developed. The Charter discusses project objectives, beginning and ending dates for the project,
budget information, approaches, along with roles and responsibilities of the project members.
3.3. Project Charter
The Project Charters title is Windows XP Migration. The overall schedule of the project
from start to completion is January 18, 2004 to July 9, 2004.
3.3.1. Project Objectives
The objectives of the project are to migrate all laptops and desktops to Windows XP, and
upgrade all hardware\software to work with Windows XP for all Differentiated Service (DS)
employees (approximately 18,000, with an additional 60,000 from the Fleet Boston merger)
within 6 months based on new corporate standards.
3.3.2. Project Budget Information
A total of $1,500,000.00 is allocated to the Windows XP Migration project for resources
that include, project managers, team leads, testers, and other essential personnel labor costs. The
finances for upgrading the actual hardware of over 78,000 desktops, laptops, and servers, does
not come out of this budget, and will not be considered for this project.
3.3.3. Project Approach

Audit all Differentiated Service hardware and software to determine upgrade needs for
compatibility with Windows XP
Develop an initial plan to identify project manager, project team, and stakeholders
Prepare business case to identify reasons\risks for migrating to Windows XP
If not already existing, develop standards, testing and migration processes, along with test
cases for testing Line-of-Business (LOB) applications on hardware platforms migrated to
Windows XP
Decide on whether to lease or buy new PC hardware upgrades
Test all Vendor or Internally installed PCs with the new Windows XP operating system
Ensure Software Distribution of (LOB) applications function on Windows XP
Provide a Benefits measurement (security, speed, ease of use, etc.) of using Windows XP
over the previously installed OS
7

3.4. Project Roles and Responsibilities

3.4.1. Roles and Responsibilites
Table 1: Roles and Responsibilities
Role

Name

Organization/
Position

Contact
Information

Project Manager

Dan Thomasson

DS-East Project Lead

704-396-7965

Team Manager

Kristin Clark

DS-West Team Lead

925-435-6233

Vendor

John Franc

Compaq (PCs/Laptops)

704-537-1822

Team Member
Team Member
Team Member
Team Member
Software
Distribution
Release
Management
Change
Management
Application
Integration

Jim Farkas
Lee Huntinsger
Pete Mikalatos
Russ Eddy
Anthony Scavo

DS-East QA Tester
DS-East QA Tester
DS-West QA Tester
DS-West QA Tester
DS-East SD Analyst

704-396-7963
704-397-1034
925-435-6235
925-435-6237
704-398-1028

Judy Ferrara

DS-East RM

704-397-3254

Tracy Wells

DS-West CM

925-435-6239

Lisa Sedberry

DS-East AI Manager

704-396-4233

3.4.2. Responsibility Assignment Matrix (RAM)

Table 2: Responsibility Assignment Matrix (RAM)
STAKEHOLDERS
ITEMS
Business Case
Project Charter
Team Contract
Scope Statement
WBS Development
Schedule & Cost
Baseline
Analyze Risks
Contingency Plan
Survey
User Inputs
Standards & Processes
Design Testing
Templates
& Test Scripts
Vendor XP Installs
Internal XP Installs
Hardware/Windows
Testing
Hardware Upgrades
Software Distribution
Benefits Measurements
Status Reports
Final Project Review
A = Accountable

Clients

Project
Manager
s
AS
AS
AS
AS
AS
AS

Team
Manager
s
P
P
P
P
P
P

Standards &
Process
Developers
I
I
I
I
IP
IP

Vendor & Internal

XP Installers

Hardware
Upgraders

Testers

Software
Distributors

P
I
IP
I
I
I

P
P
I
I
I
I

I
I
I
I
I
IP

I
P
I
I
I
I

S
S
IP
IP
S

AS
AS
I
I
IRS
I

P
P
IP
I
IRP
AR

I
IP
IP
I
API
IP

I
P
IP
I
I

P
IP
I
I

I
IP
IP
I
P
AIPR

P
IP
I
I

S
S

IS
I
I

R
R
R

I
I
I

AIPR
AIPR
I

IP
IP
I

P
P
AIP

IP
IP
I

S
S
S

I
I
IR
APRS
SR

R
A

I
IP
I
AR
R

I
IP
I
AR
R

AIP
I
I
R
R

P
I
I
RP
R

I
AIP
I
R
R

S
S
S
S
S
S

P = Participant

APRS
SR

R = Review Required

I = Input Required

S= Sign-off Required

3.5. Project Schedule

The project schedule shown in Table 3 can be viewed in more detail in the Microsoft
Project file called TS5120_Project_Schedule_Thomasson.mpp.
Table 3: Project Schedule
Initiating
Determine/assign project manager
Identify key stakeholders
Prepare business case
Prepare project charter
Planning
Hold project kickoff meeting
Prepare team contract
Prepare scope statement
Prepare WBS
Prepare schedule and cost baseline
Determine task resources
Determine task durations
Determine task dependencies
Create draft Gantt chart
Review and finalize Gantt chart
Identify, discuss, and prioritize risks
Executing
Survey
User inputs
Develop Standards\Processes
Standards
Testing Processes
Migration Processes
Templates and Test Scripts
Vendor XP Installs
Internal XP Installs
Hardware\Windows XP Testing
Hardware Upgrades
Software Distribution
Project benefits measurement
Controlling
Status reports
Closing
Prepare final project report
Prepare final project presentation
Lessons learned

5 days
1 day
2 days
5 days
5 days
15 days
1 day
10 days
5 days
10 days
2 days
1 day
1 day
1 day
2 days
1 day
2 days
90 days
3 days
10 days
50 days
15 days
15 days
15 days
50 days
30 days
60 days
50 days
5 days
10 days
20 days
125 days
125 days
5 days
2 days
2 days
1 day

1/19/2004 8:00
1/19/2004 8:00
1/19/2004 8:00
1/19/2004 8:00
1/19/2004 8:00
1/19/2004 8:00
1/19/2004 8:00
1/26/2004 8:00
1/19/2004 8:00
1/19/2004 8:00
1/19/2004 8:00
1/19/2004 8:00
1/19/2004 8:00
1/19/2004 8:00
1/19/2004 8:00
1/19/2004 8:00
1/19/2004 8:00
1/19/2004 8:00
1/19/2004 8:00
1/19/2004 8:00
1/19/2004 8:00
1/19/2004 8:00
2/9/2004 8:00
2/9/2004 8:00
1/19/2004 8:00
1/19/2004 8:00
3/1/2004 8:00
3/1/2004 8:00
5/10/2004 8:00
5/10/2004 8:00
1/19/2004 8:00
1/19/2004 8:00
1/19/2004 8:00
7/5/2004 8:00
7/5/2004 8:00
7/7/2004 8:00
7/9/2004 8:00

10

1/23/2004 17:00
1/19/2004 17:00
1/20/2004 17:00
1/23/2004 17:00
1/23/2004 17:00
2/6/2004 17:00
1/19/2004 17:00
2/6/2004 17:00 9
1/23/2004 17:00
1/30/2004 17:00
1/20/2004 17:00
1/19/2004 17:00
1/19/2004 17:00
1/19/2004 17:00
1/20/2004 17:00
1/21/2004 17:00
1/20/2004 17:00
5/21/2004 17:00
1/21/2004 17:00
1/30/2004 17:00
3/26/2004 17:00
2/6/2004 17:00
2/27/2004 17:00 22
2/27/2004 17:00 22
3/26/2004 17:00
2/27/2004 17:00
5/21/2004 17:00 26
5/7/2004 17:00 22,24
5/14/2004 17:00 28
5/21/2004 17:00 28
2/13/2004 17:00
7/9/2004 17:00
7/9/2004 17:00
7/9/2004 17:00
7/6/2004 17:00
7/8/2004 17:00 35
7/9/2004 17:00 36

4. Team Contract
The Team Contract will consist of the project name: Windows XP
Migration, and a sign-off list of project team members as previously shown in
Table 1: Roles and Responsibilities. The following bulleted list comes from
Table 3-6: Team Contract in Chapter 3, page 82 of Information Technology
Project Management by Kathy Schwalbe, and will be incorporated into the
Windows XP Migration project.
4.1. Code of Conduct: As a project team, we will:

Work proactively, anticipating potential problems and working to prevent them

Keep other team members informed of information related to the project
Focus on what is best for the entire project team

4.2. Participation: We will:

Be honest and open during all project activities

Encourage diversity in teamwork
Provide the opportunity for equal participation
Be open to new approaches and consider new ideas
Have one discussion at a time
Let the project manager know well in advance if a team member has to miss a meeting or
may have trouble meeting a deadline for a given task

4.3. Communication: We will:

Decide as a team on the best way to communicate. Since a few team members cannot
meet often for face-to-face meetings, we will use e-mail, a project Web site, and other
technology to assist in communicating
Have the project manager facilitate all meetings and arrange for phone and
videoconferences, as needed
Work together to create the project schedule and enter actuals into our enterprise-wide
project management system by 4 PM every Friday
Present ideas clearly and concisely
Keep discussions on track and have one discussion at a time

4.4. Problem Solving: We will:

Encourage everyone to participate in solving problems

Only use constructive criticism and focus on solving problems, not blaming people
Strive to build on each others ideas

4.5. Meeting Guidelines: We will:

11

Plan to have a face-to-face meeting the first and third Tuesday morning of every month
Meet more frequently the first month
Arrange for telephone or videoconferencing for participants as needed
Hold other meetings as needed
Record meeting minutes and send them out via e-mail within 24 hours of all project
meetings, focusing on decisions made and action items from each meeting
Develop an agenda before all meetings with our project sponsor and client advisors
Document major issues and decisions related to the project and send them out via e-mail
to all team members and the project sponsor

5. Scope Statement
5.1. Project Justification
Over $330,000 can be saved annually for the next four years by going to one operating
system. Instead of training Help Desk analysts on five different operating systems, they would
only need to learn one: Windows XP. Besides increasing system security and reliability, there
are several good reasons to justify the Windows XP Migration Project. See the benefits of
upgrading to Windows XP in sections 3.2 and 10.2 of this paper.
5.2. Product Characteristics and Requirements
5.2.1. Minimum requirements to Use Windows XP Professional

PC with 300 megahertz or higher processor clock speed recommended; 233 MHz
minimum required (single or dual processor system);* Intel Pentium/Celeron family, or
AMD K6/Athlon/Duron family, or compatible processor recommended

128 megabytes (MB) of RAM or higher recommended (64 MB minimum supported; may
limit performance and some features)

1.5 gigabytes (GB) of available hard disk space*

Super VGA (800 600) or higher-resolution video adapter and monitor

CD-ROM or DVD drive

Keyboard and Microsoft Mouse or compatible pointing device

5.2.2. Additional Items or Services Required to Use Certain Windows XP Features

1. For Internet access:

12

Some Internet functionality may require Internet access, a Microsoft .NET Passport
account, and payment of a separate fee to a service provider; local and/or longdistance telephone toll charges may apply

14.4 kilobits per second (Kbps) or higher-speed modem

2. For networking:
Network adapter appropriate for the type of local-area, wide-area, wireless, or home
network you wish to connect to, and access to an appropriate network infrastructure;
access to third-party networks may require additional charges
3. For instant messaging, voice and videoconferencing, and application sharing, both
parties need:
Microsoft .NET Passport account and Internet access or Microsoft Exchange 2000 Server
instant messaging account and network access (some configurations may require
download of additional components)
4. For voice and videoconferencing, both parties also need:

33.6 Kbps or higher-speed modem, or a network connection

Microphone and sound card with speakers or headset

5. For videoconferencing, both parties also need:

Video conferencing camera

Windows XP

6. For application sharing, both parties also need:

33.6 Kbps or higher-speed modem, or a network connection

Windows XP

7. For remote assistance:

Both parties must be running Windows XP and be connected by a network
8. For remote desktop:
A Windows 95 or laterbased computer, and the two machines must be connected by a
network
9. For sound:
Sound card and speakers or headphones
10. For DVD video playback:

13

DVD drive and DVD decoder card or DVD decoder software

8 MB of video RAM

11. For Windows Movie Maker:

Video capture feature requires appropriate digital or analog video capture device
400 MHz or higher processor for digital video camera capture
* Actual requirements will vary based on your system configuration and the applications
and features you choose to install. Additional available hard disk space may be required if
you are installing over a network.
5.3. Summary of Product Deliverables
5.3.1. Project Management-Related Deliverables
The Windows XP Migration Project will contain the following deliverables: Business
case, project charter, team contract, scope statement, WBS, schedule and cost baseline, Gantt
chart, survey, standards, testing processes, migration processes, templates and test scripts,
benefits measurement, status reports, final project report, final project presentation, lessonslearned report, and any other documents required to manage the project.
5.3.2. Product-Related Deliverables
The product-related deliverables consist of research reports, design documents, software
code, defect-tracking reports and software requirement lists using the Mercury Interactives
TestDirector utility, Windows XP incremental build images, along with the following basic core
applications to come on the build images:

Adobe Acrobat Reader 6.0

Microsoft Internet Explorer 6.0
Microsoft Office Professional 2002
Microsoft Outlook 2002
QWS3270 (Mainframe connectivity)
Symantec Anti-Virus 8.0
Windows Media Player 9.0
WinDVD
WinZip 8.1

The various hardware platforms are divided into two groups: 1. Laptops and 2. Desktops,
and are further divided by vendor types:
1. Laptops:
a. Toshiba 7200CT
14

b.
c.
d.
e.
f.
g.

Toshiba 7200CTe
Toshiba 8100
Toshiba 8200
IBM T21
IBM T23
IBM T40

2. Desktops:
a.
b.
c.
d.
e.
f.
g.

Dell 450
Dell 530
Compaq EN800
Compaq 1Gig
Compaq EVO 330
Compaq EVO 500
Compaq EVO 530

5.4. Milestones
The following legend should be used for the Milestones in Table 4.

C = Clients
HU = Hardware Upgraders
PD = Process Developer
PM = Project Manger
SD = Software Distributors
TM = Team Manager
T = Testers
V = Vendors
ALL = All the above
Table 4: Milestones

Milestone
Initiating
Determine/assign project manager
Identify key stakeholders
Prepare business case
Prepare project charter
Planning
Hold project kickoff meeting
Prepare team contract
Prepare scope statement
Prepare WBS
Prepare schedule and cost baseline
Determine task resources
Determine task durations

Date

Status

Responsible

1/19/2004
1/20/2004
1/23/2004
1/23/2004

100%
100%
100%
100%

PM
PM
PM, TM
PM, TM, C

1/19/2004
2/6/2004
1/23/2004
1/30/2004
1/19/2004
1/19/2004
1/19/2004

100%
100%
100%
100%
100%
100%
100%

ALL
PM, TM
PM
PM
PM, TM
PM, TM
PM, TM

15

Issues/Comments

Determine task dependencies

Create draft Gantt chart
Review and finalize Gantt chart
Identify, discuss, and prioritize risks
Executing
Survey
User inputs
Develop Standards\Processes
Standards
Testing Processes
Migration Processes
Templates and Test Scripts
Vendor XP Installs
Internal XP Installs
Hardware/Windows XP Testing
Hardware Upgrades
Software Distribution
Project Benefits Measurement
Controlling
Status Reports
Closing
Prepare final project report
Prepare final project presentation
Lessons learned

1/19/2004
1/20/2004
1/21/2004
1/19/2004

100%
100%
100%
100%

PM, TM
PM
PM
ALL

1/21/2004
1/30/2004
3/26/2004
2/6/2004
2/27/2004
2/27/2004
3/26/2004
2/27/2004
5/21/2004
5/7/2004
5/14/2004
5/21/2004
2/13/2004

100%
100%
98%
100%
100%
100%
98%
100%
50%
60%
60%
50%
100%

TM, T, C
C
PD
PD
PD, T
PD, HU
T
V
T
V, T
HU
SD
PM, TM, V

7/9/2004

50%

PM, TM, V,
T, HU

7/5/2004
7/8/2004
7/9/2004

0%
0%
0%

PM, TM
PM
ALL

5.5. Work Breakdown Structure (WBS)

16

Windows XP
Migration Project

Initiating

Planning

Executing

Controlling

Closing

Select Project
Manager

Hold Project
Kickoff Meeting

Survey

Status Reports

Prepare Final
Project Report

Form Project
Team

Prepare Team
Contract

User Inputs

East-West
Communications

Prepare Final
Presentation

Identify Key
Stakeholders

Prepare Scope
Statement

Standards &
Processes

Prepare Business
Case

Prepare Schedule
& Cost Baseline

Hardware
Upgrades

Prepare Project
Charter

Identify, Discuss,
& Prioritize Risks

XP Installs Vendor & Internal

Document
Lessons Learned

XP Testing

Software
Distribution

Benefits
Measurement

Figure 1: WBS

6. Contingency Plan
Additional days and funds will be set aside for the Windows XP Migration Project to act
as a buffer in case of project completion delays. The total timeframe for project completion is
six months, or 180 days. The actual work to complete the testing and migration of Windows XP
has been calculated to be 120 actual days based on previous migration projects. Therefore, 60
additional days can be used to mitigate possible risks of project delays.
In the case where certain departments do not receive the requested hardware upgrades by
the vendor on the date that Windows XP is to be installed, contingency plans are set in place to
have an alternate hardware vendor deliver the PCs.

7. Risk Plans

17

7.1. Windows XP Migration Project Risk Management Plan

It is important to establish a Risk Management Plan at the beginning of a project. Getting
all the stakeholders involved in identifying specific risks for their areas of the project is just the
first step.
7.2. Windows XP Migration Project Risk Response Plan
The second step would be to create a Risk Response Plan that includes risks that are
identified, people (stakeholders) assigned responsibilities for managing those risks, results from
risk analysis, response strategies, budget and schedule estimates for responses, and contingency
and fallback plans.
If new risks occur, but stakeholders do not acknowledge the risks, I would still update the
Risk Response Plan, and put the risks next to the responsible stakeholder's name. I would remind
the stakeholders that the Risk Response Plan is viewed by executive management. If the project
schedule becomes excessively delayed, over budget, or fails because of lack of
acknowledgement of the risks by the stakeholders, then the stakeholders will be held accountable
for their actions.
7.3. Top Ten Risks in Information Technology
The following top ten risks come from Intel, but pertain to Bank of America and
especially the XP Migration project.
1

Delaying your regular refresh cycle for desktop and notebook PCs in an effort to save
money
2 Using a desktop PC as a server.
3 Installing unauthorized wireless access points in a company building.
4 Using outdated or manual data storage methods as your primary data backup solution.
5 Giving employees the wrong machines for their jobs.
6 Maintaining multiple images in the client PC base.
7 Using illegal, unauthorized, pirated, or shared software.
8 Operating and maintaining multiple servers without considering consolidation.
9 Modifying or replacing internal PC hardware components to achieve better performance.
10 Sharing work e-mail addresses and other sensitive information on the Internet.
7.4. Risk Assessment Matrix (RAM)
Table 5: Risk Assessment Matrix (RAM)
Ranking
1
2

Potential Risk
Inadequate Planning
Poor definition of XP
Migration Project

Severity
H
M

Impact
4
3

18

Risk Resolution / Mitigation

Work on revising the entire project plan
(WBS).
Hold additional meetings with project
customer, sponsor, and other stakeholders to
clarify scope and Project Charter.

Insufficient testing
staff.

Under-estimated costs
because of Fleet
Boston merger.

Insufficient Time
Estimates

Too much focus on

one part of the project

Unable to order
hardware (PCs)
in time for migration
of XP

After merger with Fleet Boston, add 4

additional testing engineers to the testing
staff.
Revise cost estimates to include additional
60,000 PCs for a total of 78,000 PCs.
Increase budget for project from $1,000,000
to $1,500,000 for project resources.
Hardware costs comes from a different
budget of $156,000,000.
Revise schedule estimates to reflect
additional testing and migration time needed
to incorporate the upgrades of 78,000 PCs.
Emphasize team support and avoid standalone project structure.
Increase frequency of project monitoring.
Use WBS and CPM
Contact hardware vendors three months
prior to actual migration, to acquire
necessary PCs.

Severity: L= Low, M = Medium, H = High

Impact: 1 = Least Probable, 5 = Most Probable

8. Project Communication Plan

Excellent communication skills by project managers are essential, and can be the
influencing factor in the successful completion of major projects, within budget and on time.
Project managers must be able to:

Communicate ideas, problems, and solutions clearly

Create professional technical documentation, status reports, project plans, test
plans, defects, etc. with appropriate content
Communicate in a level of detail appropriate for their audience
Communicate a sense of urgency and competence
Follow up to ensure that communication was received and understood
Be receptive to exchanging ideas and being open minded

Project managers should also develop a strategy for making sure project deliverables are
conveyed to the right target audience using the most efficient delivery mechanism. To
accomplish this task, the project manager could prepare a Project Communication Plan as in
Table 6. This communication plan relates to the Windows XP Migration project.
Table 6 Project Communication Plan
Deliverable

Type

Target
Audience(s)

Who
Responsible?

19

Delivery
Method

Delivery
Frequency

Business Case

Mandatory

Project Charter

Mandatory

Shareholders,
CEO
Project Team

Project
Manager
Project
Manager
Project Team

Team Contract

Mandatory

Project Team

Scope Statement

Informational

Project Team

WBS

Mandatory

Project Team

Schedule and
Cost Baseline
Gantt Chart

Mandatory
Informational

Project Team,
CEO
Project Team

Survey

Informational

Clients

Team Managers

Standards

Informational

Project Team

Testing
Processes

Informational

Testing Team

Migration
Processes
Templates and
Test Scripts
Benefits
Measurement
Status Reports

Informational

Clients

Standards
Developer
Testing
Manager,
Testers
XP Upgraders

Informational

Testing Team

Testers

Informational
Mandatory

Shareholders,
CEO
Project Manager,
Shareholders,
CEO

Final Project
Report

Mandatory

CEO

Project
Manager
Project
Manager,
Team
Managers,
Testers
Project
Manager

Final Project
Presentation

Mandatory

CEO

Lessons-learned
Report

Informational

Company

Project
Manager
Project
Manager
Project
Manager
Project
Manager

Formal
Presentation
Formal
Presentation
Formal
Presentation
Intranet,
E-mail
Intranet,
Email
Intranet,
E-mail
Intranet,
E-mail
Intranet,
E-mail,
Fax,
Snail Mail
Intranet

Once
Once
Once
Once
Once
Weekly
Once with
occasional
updates.
On-going
throughout
project
Once

Intranet

Once

Intranet

Once

Intranet,
E-mail
Formal,
Presentation
Intranet,
E-mail,
Formal
Presentations

On-going

Formal
Presentation

Once

Project
Manager

Formal
Presentation

Once

Project
Manager

Intranet
E-mail

Once

Once
Weekly

9. Quality Management Plan

The Windows XP Migration project at Bank of America has expanded from 18,000
clients to 78,000 clients with the merger of Fleet Boston during the last couple of months. The
migration project team is determined to provide the best quality of service and testing of the
Windows XP operating system on all bank related hardware platforms. Our goal is to meet the
20

project deadlines specified in the Project Charter and Project Plan. We will achieve these goals
through the following processes: quality planning, quality assurance, and quality control.
9.1. Quality Planning
Within quality planning, we will use the following standards: IEEE 829 Software
Documentation, Capability Maturity Model (CMM), and ISO 9001.
9.1.1. IEEE 829
IEEE 829-1998 Standard for Software Test Documentation provides a standard set of test
documents and templates that can be used by the technical community. Such documents are
frequently implemented into the working environment as checklists or guidelines for specific
testing processes. The basic emphasis of this standard is on test planning, test specification, and
test reporting.
9.1.2. CMM
One of the main methodologies used today for helping developers and testers improve
their application development and software-testing processes comes from a process maturity
framework called Capability Maturity Model (CMM). This model originated from the Software
Engineering Institute (SEI) at Carnegie-Mellon University in 1986. The CMM model defines
five levels of software maturity for an organization: 1) Initial, 2) Repeatable, 3) Defined, 4)
Managed, and 5) Optimizing.
9.1.3. ISO 9001
The International Organization for Standardization (ISO) provides over 13,700
International Standards for business, government and society. Our project team will use
ISO 9001:2000 Quality management systems: Requirements.
9.2. Quality Assurance
For quality assurance, our focus is on software testing as it pertains to Windows XP,
applications running on XP, and hardware platforms using XP. We will periodically evaluate the
overall project performance to ensure the project will satisfy the relevant quality standards that
include IEEE 730 and IEEE Stoneman.
9.2.1. IEEE 730
IEEE 730-2002 Standard for Software Quality Assurance Plans discusses standards,
practices, conventions, and metrics for software quality. It incorporates subjects covering basic
technical, design, and other programming activities by developers. Such activities include
writing documentation, defining variable and module names, executing code inspections, and
testing their products.
9.2.2. IEEE Stoneman

21

The IEEE Stoneman (version 0.7) Software Engineering Body of Knowledge (SWEBOK)
is an excellent standard for software developers and testers. Chapters 5 and 11 are very useful.
Chapter 5, Software Testing, describes the testing process that encompasses:

Testing basic concepts and definitions

Test levels
Test techniques
Test related measures
Managing the test process

Chapter 11, Software Quality, provides a comprehensive discussion on software quality

assurance and verification and validation of developed software. The chapter also covers
fundamentals of measurement (measuring the value of quality), metrics, measurement
techniques, and defect characterization.
9.3. Quality Control
9.3.1. Monitoring Project Progress
The project team will monitor specific project results to ensure that they comply with the
relevant quality standards while identifying ways to improve overall quality. We will use Gantt
charts and quality control charts to display data that illustrates the results of specific processes
over time. Periodic reviews will help identify possible problem areas. We will use the IEEE
1028 standard as a guide for our reviews.
9.3.2. IEEE 1028
IEEE 1028-1997 (R2002) Standard for Software Reviews defines the reviewing processes
for both critical and non-critical software. The IEEE 1028 standard provides instruction on how
to execute reviews. The best use of this standard is to apply its procedures early on in the
development of the softwares life cycle.
9.4. Testing
The IEEE 829 standard describes a framework within which the entire testing process can
be managed. We will use the testing process shown in Figure 2.

22

Figure 2: Testing Process

Testing teams are scheduled throughout the entire life cycle of the project. Each team
will test the following:

Windows XP operating system on all bank hardware platforms

All departmental applications running on XP

10. Cost/Benefit Analysis

10.1. Cost of Project Resources

23

Table 7: Windows XP Migration Cost Analysis

Resources

# of Resources

Hourly Pay Rate

# of Hours

Total

Project Managers

$85.00

1040

$176,800.00

Team Managers

$75.00

1040

$234,000.00

Testers

10

$55.00

750

$412,500.00

XP Installers

$65.00

100

$26,000.00

Software Distributors

$60.00

150

$18,000.00

Standards\Process
Developers

$65.00

250

$48,750.00

Hardware Upgraders

$55.00

100

$22,000.00

Total

$938,050.00

10.2. Benefits
Here is a final overview of some of the benefits that Bank of America will receive after
migrating to Windows XP.
1. Business-level Reliability - Windows XP delivers a new level of stability, so clients can
focus on their work. For example, in most cases, if one program crashes, the clients
computer will keep running.
2. Advanced Performance - Windows XP manages system resources efficiently, meeting
the performance standards set by Windows 2000 and exceeding those set by Windows 98
Second Edition.
3. Remote Desktop - Remote Desktop allows clients to create a virtual session and use their
desktop computer from another computer running Windows 95 or later, giving them
access to all of their data and applications even when they are not in their office.
4. New Task-Based Visual Design Allows clients to access their most commonly used
tasks quickly, because of a cleaner design and new visual cues within Windows XP.
5. Wireless 802.1x Networking Support - Wireless 802.1x Networking Support provides
support for secured access, as well as performance improvements for wireless networks.
6. Windows Messenger - Windows Messenger is the easy way to communicate and
collaborate in real time on a client computer. Clients can see the online status of their
contacts and choose to communicate with them through text, voice, or video with better
performance and higher quality.

24

7. Encrypting File System - Encrypting File System provides a high level of protection
from hackers and data theft by transparently encrypting files with a randomly generated
key.
8. Fast Resume from Hibernation or Standby Clients can save battery power when
working on the road. With Windows XP, their laptop can enter Standby or Hibernate
faster, and it can start working again faster after resuming from Standby or Hibernation.
9. Help and Support Center with Remote Assistance - In addition to a comprehensive set
of documentation, Help and Support Center in Windows XP includes Remote Assistance,
which allows clients to have a friend or IT professional who is also running Windows XP
remotely control their computers to demonstrate a process or help solve a problem.
10. System Restore - If something goes wrong with clients computers, they can revert the
system to a previous state.
Once again, the bottom line for migrating to Windows XP is to save money.

11. Project Sign-Off

The project will be considered complete when all the stakeholders have signed off the
project.

25

Appendix 1: Business Case for Project Name

Date
Prepared by:
1.0 Introduction/ Background

2.0 Business Objective

3.0 Current Situation and Problem/Opportunity Statement

4.0 Critical Assumption and Constraints

.
5.0 Analysis of Options and Recommendation

6.0 Preliminary Project Requirements

7.0 Budget Estimate and Financial Analysis

8.0 Schedule Estimate

9.0 Potential Risks

10.0 Exhibits
Exhibit A: Financial Analysis

26

Appendix 2: Financial Analysis for Project Name

Created by:
Date:
Note: Change the inputs, such as interest rate, number of years, costs, and benefits. Formulas are
entered in the Excel file used to create this template. Be sure to double-check the formulas based
on the inputs.
Discount rate

8%

Assume the project is completed in Year 0

Costs
Discount factor
Discounted costs
Benefits
Discount factor
Discounted benefits

Discounted benefits - costs

Cumulative benefits - costs

ROI

0
100
1.00
100
0
1.00
0

(100)
(100)

Year
1
2
100
100
0.93
0.86
93
86
200
0.93
185

200
0.86
171

93
(7)

86
78

44%
Payback before Year X

Assumptions
Enter assumptions here

27

3Total
100
0.79
79
358
200
0.79
159

79
158

515

158

NPV

Appendix 3: Project Charter

Project Title:
Project Start Date:
Budget Information:

Projected Finish Date:

Project Manager: Name, phone, e-mail

Project Objectives:

Approach:

Roles and Responsibilities

Role

Name

Organization/
Position

Contact
Information

Sign-off: (Signatures of all above stakeholders. Can sign by their names in table above.)
Comments: (Handwritten or typed comments from above stakeholders, if applicable)

28

Appendix 4: Project Name/Kick-off Meeting

Date
Meeting Objective:
Agenda:

Introductions of attendees
Background of project
Review of project-related documents (i.e. business case, project request, contract)
Discussion of project organizational structure
Discussion of project scope, time, and cost goals
Discussion of other important topics
List of action items from meeting

Action Item

Assigned To

Due Date

Date and time of next meeting:

29

Appendix 5: Scope Statement

Project Title:
Date:
Prepared by:
Project Justification:

.
Product Characteristics and Requirements:
1.
2.
3.
4.
Summary of Project Deliverables
Project management-related deliverables: business case, charter, team contract, scope
statement, WBS, schedule, cost baseline, status reports, final project presentation, final
project report, lessons-learned report, and any other documents required to manage the
project.
Product-related deliverables: research reports, design documents, software code,
hardware, etc.
1.
2.
3.
4.

Project Success Criteria:

30

Appendix 6: Weekly Status Report

Project Name:
Team Member Name:
Date:
Work completed this week:

Work to complete next week:

Whats going well and why:

Whats not going well and why:

Suggestions/Issues:

Project changes

31

Appendix 7 Milestone Report for Project Name

Prepared by:
Milestone
Initiating

Date:
Date

Status

Responsible

Planning

Executing

Controlling

Closing

32

Issues/Comments

Appendix 8: Quality Assurance Plan for Project Name

Prepared by:

Date:

1.0 Draft Quality Assurance Plan

1.1 Introduction
1.2 Purpose
1.3 Policy Statement
1.4 Scope
2.0 Management
2.1 Organizational Structure
2.2 Roles and Responsibilities
2.2.1 Technical Monitor/Senior Management
2.2.2 Task Leader
2.2.3 Quality Assurance Team
2.2.3 Technical Staff
3.0 Required Documentation
4.0 Quality Assurance Procedures
4.1 Walkthrough Procedure
4.2 Review Process
4.2.1 Review Procedures
4.3 Audit Process
4.3.1 Audit Procedures
4.4 Evaluation Process
4.5 Process Improvement
5.0 Problem Reporting Procedures
5.1 Noncompliance Reporting Procedures
6.0 Quality Assurance Metrics
Appendix
Quality Assurance Check List Forms

33

Appendix 9: Client Acceptance/Project Completion Form

Project Name:
Project Manager:

________________________________________________
________________________________________________

I (We), the undersigned, acknowledge and accept delivery of the work completed for this project on behalf of
our organization. My (Our) signature(s) attest to my (our) agreement that this project has been completed.
No further work should be done on this project.
Name

Title

Signature

1. Was this project completed to your satisfaction?

Date

Yes

No

2. Please provide the main reasons for your satisfaction or dissatisfaction with this project.
3. Please provide suggestions on how our organization could improve its project delivery
capability in the future.

Thank you for your inputs.

34

Appendix 10: Team Contract

Project Name:
Project Team Members Names and Sign-off:
Name

Sign-off on Team Contract

Code of Conduct: As a project team, we will:

Participation: We will:

Communication: We will:

Problem Solving: We will:

Meeting Guidelines: We will:

35

Appendix 11: Software Project Management Plan

for Project Name
Prepared by:

Date:

1. Introduction

Project Overview
Project Deliverables
Evolution of the SPMP
Reference Materials
Definitions and Acronyms

2. Project Organization

Process Model
Organizational Structure
Organizational Boundaries and Interfaces
Project Responsibilities

3. Managerial Process

Management Objectives and Priorities

Assumptions, Dependencies, and Constraints
Risk Management
Monitoring and Controlling Mechanisms
Staffing Plan

4. Technical Process

Methods, Tools, and Techniques

Software Documentation
Project Support Functions

5. Work Packages, Schedule, and Budget

Work Packages
Dependencies
Resource Requirements
Budget and Resource Allocation
Schedule

36

Appendix 12: Windows XP Migration Intranet Web Site

The following project related documents and additional resources would be available via
the Windows XP Migration Intranet Web Site:
1. Project Charter
2. Project Timeline
3. Initial Budget
4. Project Description
5. Project Approach
6. Project Members Contact Information
7. Business Case
8. Quality Statement
9. Scope Statement
10. Project Deliverables
11. Benefits Measurement
12. Work Breakdown Structure (WBS)
13. Team Contract
14. Project Responsibility Assignment Matrix
15. Project Gantt Chart
16. Project Schedule
17. Additional Cost Estimate Analysis
18. Meeting Calendar
19. Status Reports
20. Surveys
21. Risk Assessments
22. Standards
23. Processes
24. Methodologies
25. Templates
26. Vendor Lists
27. Lessons Learned Report
28. Question & Answer Forum - Discussions
29. Final Report
Not everyone working on the project would have access to all of the 24 items listed
above. Access to cost estimates and other sensitive financial information will be provided to the
project managers and executive management that have a need to know. No reason to provide
financial information to the actual project testers.
The Project Responsibility Assignment Matrix, previously listed under section 3.4.2, can
be used as a guide for assigning stakeholders the proper access to the various 24 listed resources.

37

Appendix 13: IEEE Standards for Information Technology

Testers, developers, project managers, resource managers, and other professionals in the
Information Technology field should be aware of industry standards that apply to their
profession. It is important that these professionals understand when and how to apply such
standards, and where to access the most current versions.
The following IEEE standards encompass the software testing process (IEEE, 2003).
Additional IEEE standards, not listed here, focus on software engineering and maintenance.
Besides IEEE, testers should also be familiar with standards developed by the International
Organization for Standardization and the Department of Defense.
When ordering IEEE standards, do one of the following:
1) Online Order: Go to http://standards.ieee.org/catalog/olis/index.html
2) Phone Order: Dial 201-981-0060 (IEEE Standards Sales office in New Jersey)
3) Mail Order: Computer Society of the IEEE
P.O. Box 80452
Worldway Postal Center
Los Angeles, CA 90080
IEEE Software Engineering Standards (standards.ieee.org/catalog/olis/se.html)
1. 610.12-1990(R2002) IEEE Standard Glossary of Software Engineering Terminology
2. 730-2002
IEEE Standard for Software Quality Assurance Plans
3. 828-1998
IEEE Standard for Software Configuration Management Plans
4. 829-1998
IEEE Standard for Software Test Documentation
5. 830-1998
IEEE Recommended Practice for Software Requirements Specifications
6. 982.1-1988
IEEE Standard Dictionary of Measures to Produce Reliable Software
7. 1008-1987(R1993, R2002) IEEE Standard for Software Unit Testing
8. 1012-1998
IEEE Standard for Software Verification and Validation
9. 1012a-1998
IEEE Standard for Software Verification and Validation Supplement to 1012-1998 Content Map to IEEE 12207.1
10. 1016-1998
IEEE Recommended Practice for Software Design Descriptions
11. 1028-1997(R2002)
IEEE Standard for Software Reviews
12. 1044-1993(R2002)
IEEE Standard Classification for Anomalies
13. 1045-1992(R2002)
IEEE Standard for Software Productivity Metrics
14. 1058-1998
IEEE Standard for Software Project Management Plans
15. 1061-1998
IEEE Standard for Software Quality Metrics Methodology
16. 1062, 1998(R2002) IEEE Recommended Practice for Software Acquisition (includes IEEE 1062a)
17. 1063-2001
IEEE Standard for Software User Documentation
18. 1074-1997
IEEE Standard for Developing Software Life Cycle Processes
19. 1175.1-2002
IEEE Guide for Computer-Aided Software Engineering (CASE) Tool Interconnections Classification and Description
20. 1219-1998
IEEE Standard for Software Maintenance
21. 1220-1998
IEEE Standard for the Application and Management of the Systems Engineering Process
22. 1228-1994 (2002)
IEEE Standard for Software Safety Plans
23. 1233, 1998(R2002) IEEE Guide for Developing System Requirements Specifications (including IEEE
1233a)
24 .1320.1-1998
IEEE Standard for Functional Modeling Language - Syntax and
Semantics for IDEF0

38

25. 1320.2-1998

IEEE Standard for Conceptual Modeling Language Syntax and Semantics for IDEF1X97
(IDEFobject)
26. 1362-1998
IEEE Guide for Information Technology - System Definition - Concept of Operation
Document
27. 1420.1-1995(R2002) IEEE Standard for Information Technology - Software Reuse - Data Model for Reuse
Library Interoperability: Basic Interoperability Data Model (BIDM)
28. 1420.1a-1996(R2002) IEEE Supplement to Standard for Information Technology - Software Reuse - Data
Model or Reuse Library Interoperability: Asset Certification Framework
29. 1420.1b-1999(R2002) IEEE Supplement to IEEE Standard for Information Technology -Software Reuse - Data
Model for Reuse Library Interoperability: Intellectual Property Rights Framework
30. 1462-1998
[Adoption of International Standard ISO/IEC 14102:1995(E)], Information technology Guideline for the evaluation and selection of CASE tools
31. 1465-1998
[Adoption of ISO/IEC 12119: 1994(E)], IEEE Standard Adoption of International
Standard ISO/IEC 12119: 1994(E) Information Technology - Software packages Quality
requirements and testing
32. 1471-2000
IEEE Recommended Practice for Architectural Description of Software-Intensive
Systems
33. 1490-1998
IEEE Guide (IEEE) - Adoption of PMI Standard- A Guide to the Project Management
Body of Knowledge (PMI)
34. 1517-1999
IEEE Standard for Information Technology - Software Life Cycle Processes - Reuse
Processes
35. 2001-2002
IEEE Recommended Practice for the Internet-Web Site Engineering, Web Site
Management, and Web Site Life Cycle
36. 1540-2001
IEEE Standard for Software Life Cycle Processes-Risk Management
37. J-Std-016-1995
EIA/IEEE Interim Standard for Information Technology Software Life Cycle Processes Software Development Acquirer-Supplier Agreement (Issued for Trial Use)
38. 12207.0-1996
IEEE/EIA Standard: Industry Implementation of International Standard ISO/IEC
12207:1995 Standard for Information Technology - Software Life Cycle Processes.
40. 12207.1-1997
IEEE/EIA Standard: Industry Implementation of International Standard ISO/IEC
12207:1995 Standard for Information Technology - Software Life Cycle Processes - Life
cycle data
41. 12207.2-1997
IEEE/EIA Standard: Industry Implementation of International Standard ISO/IEC
12207:1995 Standard for Information Technology - Software Life Cycle Processes
Implementation considerations
42. 14143.1-2000
Implementation Note for IEEE Adoption of ISO/IEC 14143- 1:1998, Information
Technology - Software Measurement - Functional Size Measurement - Part 1: Definition
of Concept

39

References
Bertolino, A. (2000, April). Chapter 5, software testing. IEEE Stoneman (Version 0.7), The
Institute of Electrical and Electronics Engineers, Inc., pp. 1-18.
CarnegieMellon. Capability Maturity Model for Software. Retrieved February 3, 2004,
from http://www.sei.cmu.edu/cmm/cmm.html
IEEE. (1998). Standard for software test documentation. ANSI/IEEE 829. New York: ANSI.
IEEE. (2000). Software Engineering Body of Knowledge (SWEBOK). ANSI/IEEE Stoneman
(version 0.7). New York: ANSI.
IEEE. (2002). Standard for reviews. ANSI/IEEE 1028. New York: ANSI.
IEEE. (2002). Standard for software quality assurance plans. ANSI/IEEE 730. New York:
ANSI.
IEEE. (2003). IEEE Standards Online. Retrieved February 3, 2004,
from http://standards.ieee.org/catalog/olis/se.html
Intel. (2004) Top 10 Technology Risks. Retrieved March 5, 2004,
from http://www.intel.com/business/tech_risks/demo/launch.htm
ISO. (2003). ISO Standards Online. Retrieved February 2, 2004,
from http://www.iso.ch/iso/en/ISOOnline.openerpage
Microsoft. Top 10 Reasons for Moving to Windows XP Professional. Retrieved March 23, 2004,
from http://www.microsoft.com/windowsxp/pro/evaluation/whyupgrade/top10.asp
Perry, W. E. (2000). Effective methods for software testing (2nd ed.). New York: John Wiley &
Sons.
PMBOK. (2000). PMBOK guide (2000 ed). Pennsylvania: Project Management Institute,
Inc.
Reeker, L., & Wallace, D. (2000, April). Chapter 11, software quality. IEEE Stoneman (Version
0.7), The Institute of Electrical and Electronics Engineers, Inc., pp. 1-20.
Schwalbe, K. (2004). Information technology project management (3rd ed.). Canada: Thomas
Learning, Inc.

40