Scribd
Upload
14 views

Lecture 4 - Project Management Case Study

Uploaded by

hjade7255
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
14 views

Lecture 4 - Project Management Case Study

Uploaded by

hjade7255
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 19

Systems

Analysis & Design


Case Study: IT Project Management
Introduction
• Information systems are the support structure for
meeting the company’s strategies and goals
• Billions of dollars spent yearly on acquisition, design,
development, implementation, and maintenance of
IT systems
• Companies depend on information more than ever
• These slides are about how organizations acquire
new information systems

Computer Information Systems


Introduction
• So, you need a new system… 2 questions
– What functionality does the system need?
– Where are you going to get it?
Buy a customizable package?
Pay someone to build it for you?
Build it yourself?
• Answering these questions is the job of the
Systems Analyst, IT Manager, CIO, …

Computer Information Systems


Do It Yourself
• Systems development life cycle (SDLC) a
structured step-by-step approach for developing
information systems
– There are 7 general phases in the System
Development Life Cycle (SDLC)
– There are a variety of approaches, each with
advantages and disadvantages

Computer Information Systems


SYSTEMS DEVELOPMENT LIFE CYCLE
SDLC PHASE ACTIVITIES
1. Planning •Define the system to be developed
•Set the project scope
•Develop the project plan

2. Analysis •Gather business requirements


3. Design •Design the technical architecture
•Design system models
4. Development •Build technical architecture
•Build databases and programs
5. Testing •Write test conditions
•Perform testing
6. Implementation •Write user documentation
•Provide training
7. Maintenance •Build a help desk
•Support system changes

Computer Information Systems


Project Management Case Study
• What’s going in this case?
– Projects are over-time and over-budget
• Why?
– We don’t know
– Planning?

Computer Information Systems CIDM3330 Management of IS


Project Management Case Study
• How did Davies solve this problem?
• What is Huerta’s position?
• What is Calder’s position?

• Which solution would you recommend to


Barton? Why?
– Write down on a piece of paper and turn it in

Computer Information Systems CIDM3330 Management of IS


Phase 1: Planning
Set the project scope
• Project scope - clearly identifies high level
objectives… what activities will be supported
– Scope creep - occurs when the scope of the
project increases
• Features – clearly defines what functionality the
system can perform
– Feature creep - occurs when developers add
extra features that were not part of the initial
requirements

Computer Information Systems


Scope vs. Features
• Scope refers to which business processes are
supported. High level and business focused.
– Scope tells us: what problem are we solving.
• Features refer to what the system does. More
specific and system focused.
– Features tell us: what will the system actually
do.

9
Computer Information Systems
Systems development methodologies
• Developers have different development
methodologies, we’ll just focus on two:
– Waterfall methodology
• Who recommended this approach?
– Rapid application development (RAD, AKA
prototyping)

Computer Information Systems


Waterfall Methodology
• Waterfall methodology - a sequential, linear,
activity-based process in which each phase in the
SDLC is performed sequentially

Computer Information Systems


Where does Waterfall work?
• Mission Critical Applications
• Manufacturing, Construction, Medical, NASA
• Where cost of prototyping is too high

Computer Information Systems CIDM3330 Management of IS


Rapid Application Development (RAD)
• Rapid application development (RAD) (also
called rapid prototyping) - emphasizes extensive user
involvement in the rapid and evolutionary construction of
working prototypes of a system to accelerate the systems
development process
– Prototype - a smaller-scale, representation, or working
model of the user’s requirements or a proposed design for
an information system

Computer Information Systems


Rapid Application Development (RAD)

Computer Information Systems


Prototyping
• Prototyping - the process of building a model
that demonstrates the features of a proposed
product, service, or system
– The prototyping process involves four steps:
1. Identify basic requirements
2. Develop initial prototype
3. User review
4. Revise and enhance the prototype

Computer Information Systems


The Prototyping Process

Computer Information Systems


Advantages of Prototyping
• Encourages Active User Participation
• Helps Resolve Discrepancies Among Users
• Gives Users a Feel for the Final System
• Helps Determine Technical Feasibility
• Helps Sell the Idea of a Proposed System

Computer Information Systems


Disadvantages of Prototyping
• Leads People to Believe the Final System Will
Follow Shortly
• Does not give a good indication of Performance
under Operational Conditions
• Leads the Project Team to Forgo Proper Testing
and Documentation

Computer Information Systems


Death March
• Lack of upward
information
• Lack of discipline early
on
• Rush at end to meet
deadline
• Long hours, low morale
• Can Agile/Prototyping
suffer from Death
Marches?
• School projects???

Computer Information Systems CIDM3330 Management of IS

You might also like