Chapter Extension 18
Large-Scale Systems
Development
© 2008 Pearson Prentice Hall, Experiencing MIS, David Kroenke
Study Questions







CE18-2
What characterizes large-scale information systems
development projects?
What are the trade-offs in requirements, cost, and time?
What is the PMBOK® Guide for project management?
How does a work-breakdown structure drive project
management?
What are the biggest challenges for planning a large-scale
systems development project?
What are the biggest challenges for managing a large-scale
systems development project?
What is the single most important task for users on a largescale systems development project?
© 2008 Pearson Prentice Hall, Experiencing MIS, David Kroenke
Large-Scale Information Systems






CE18-3
Many functions and features
Necessitate creation of large, complex
computer programs
Process multiple relationship databases
Support hundreds of users
Require large development teams
May be localized for different languages
© 2008 Pearson Prentice Hall, Experiencing MIS, David Kroenke
Development of Large-Scale
Systems

Requires large development teams
–




CE18-4
Systems analysts, programmers, PQA engineers, managers
Often simultaneously developed at multiple sites
May involve integration of products and services
from different companies
Localized for different languages
Require extended development intervals
© 2008 Pearson Prentice Hall, Experiencing MIS, David Kroenke
Characteristics of Large-Scale
Systems Development Projects
Figure CE 18-1
CE18-5
© 2008 Pearson Prentice Hall, Experiencing MIS, David Kroenke
Emerson Pharmaceuticals


Large-scale project to modernize order system
Existing system is a thick-client system
–

New system is thin-client, Web browser version
–
–

CE18-6
Required installation of software on clients’ computers
Changes way orders are received and processed
Localized for three languages
Development team consists of more than 75 people
and several contractors
© 2008 Pearson Prentice Hall, Experiencing MIS, David Kroenke
Balancing Drivers

Three critical drivers
–

Trade-offs exist in any project against time
and costs
–
–
–
CE18-7
Requirements (scope), cost, and time
Time can only be reduced to a point
Adding more people can create diseconomies of
scale
Increasing time may reduce or increase costs
© 2008 Pearson Prentice Hall, Experiencing MIS, David Kroenke
Baseline Plan

Consists of:
–
–
–

Things don’t always go according to plan
–
CE18-8
Tasks to accomplish
Resources (human and materials)
Schedule for completion
Requires project managers to re-assess tradeoffs between requirements, costs, and time
© 2008 Pearson Prentice Hall, Experiencing MIS, David Kroenke
®
PMBOK Project Management
Guide

Project Management Institute (PMI) compiled best
practices, processes, techniques
–
–

Five process groups
–

Stages in life of project
Nine knowledge areas
–
CE18-9
Endorsed by ANSI and ISO
PMP certification
Factors that must be managed throughout life of project
© 2008 Pearson Prentice Hall, Experiencing MIS, David Kroenke
Structure of PMBOK Guide 2004
®
Figure CE 18-4
CE18-10
© 2008 Pearson Prentice Hall, Experiencing MIS, David Kroenke
PMI Knowledge Areas









CE18-11
Project integration
Scope (requirements)
Time
Cost
Quality
Human resources
Communications
Risk
Procurement
© 2008 Pearson Prentice Hall, Experiencing MIS, David Kroenke
PMI Project Management Processes





CE18-12
Initiating
Planning
Executing
Monitoring and Controlling
Closing
© 2008 Pearson Prentice Hall, Experiencing MIS, David Kroenke
Work-Breakdown Structure

WBS
–
–
–
–
–

CE18-13
Hierarchy of tasks required to complete project
Each task is broken into smaller tasks that can be
managed and estimated
Define task dependencies
Estimate task durations
May be inputted into project management
software
Final WBS plan is baseline WBS
© 2008 Pearson Prentice Hall, Experiencing MIS, David Kroenke
Sample WBS
Figure CE 18-4
CE18-14
© 2008 Pearson Prentice Hall, Experiencing MIS, David Kroenke
Gantt Chart of WBS
Figure CE 18-5
CE18-15
© 2008 Pearson Prentice Hall, Experiencing MIS, David Kroenke
Critical Path Analysis



Sequence of activities charted
Used to determine the earliest date a project
can be finished
Longest path through the network of
activities
–
–
CE18-16
Task dependencies compressed as much as
possible
Tasks may be moved to non-critical paths to
shorten critical path
© 2008 Pearson Prentice Hall, Experiencing MIS, David Kroenke
Planning Large-Scale Systems
Development Projects

Biggest challenge is scheduling
–
–
–

Errors accumulate
Difficult to do credible planning
Every task may be on critical path
Software development solutions
–
–
–
Don’t develop in-house
Abandon SDLC and invest resources in project, managing
as well as possible, accepting schedule
Schedule using estimation techniques

CE18-17
Base on data from similar projects, estimate lines of code,
estimate function points
© 2008 Pearson Prentice Hall, Experiencing MIS, David Kroenke
Managing Large-Scale Systems
Development Project

Challenges
–
Coordination

–
Diseconomies of scale

–
Changes must be carefully manages and monitored
Unexpected events

CE18-18
Adding people increases coordination requirements
Configuration control

–
Projects often organized into independent groups
Chance of disruption due to unanticipated events
© 2008 Pearson Prentice Hall, Experiencing MIS, David Kroenke
Taking Responsibility for
Requirements


Single most important task that can be performed
Understand the system is built for business function
–

Users
–
–
–
CE18-19
Manage requirements
Responsible for ensuring complete and accurate
requirements
Must manage requirements creep
Define test conditions
© 2008 Pearson Prentice Hall, Experiencing MIS, David Kroenke
Dealing with Uncertainty

Policies and procedures implemented to instill these
principles:
–
–
–
–
–
–
CE18-20
Business users take responsibility for new systems’ success
Users work with IS throughout systems development
Users take active role in project planning, management, and
reviews
Development phase not complete until work reviewed and
approved
Users actively test system
Future systems developed in small increments
© 2008 Pearson Prentice Hall, Experiencing MIS, David Kroenke
Active Review







CE18-21
What characterizes large-scale information systems
development projects?
What are the trade-offs in requirements, cost, and time?
What is the PMBOK® Guide for project management?
How does a work-breakdown structure drive project
management?
What are the biggest challenges for planning a large-scale
systems development project?
What are the biggest challenges for managing a large-scale
systems development project?
What is the single most important task for users on a largescale systems development project?
© 2008 Pearson Prentice Hall, Experiencing MIS, David Kroenke