MIS_446_Proj_Mgmt - So#ware
and
Project
 Management
 MIS
446
 Classic
Failures
 •  •  •  •  •  •  • 

Info iconThis preview shows page 1. Sign up to view the full content.

View Full Document Right Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: So#ware
and
Project
 Management
 MIS
446
 Classic
Failures
 •  •  •  •  •  •  •  FoxMeyer
Drug
 Hershey
 Sainsbury
 London
Stock
Exchange
 Airbus
 FAA
ATC
 FBI
 Two
Roles
of
MIS
 •  Run
the
business
 –  TransacIon
processing
 –  Help
desk
 –  Etc.
 •  Change
the
business
 –  Shi#
balance
of
compeIIve
advantage
in
a
market
 –  Shi#
cost
curves
 What
is
a
Project?
 •  •  •  •  •  Outside
usual
course
of
work
 Crosses
funcIons
 Changes
business
 Unclear
lines
of
commend
 Built
of
code
 –  Mythical
man‐month
 –  Intangible
 –  Not
done
when
wriSen,
done
when
tested
 Stages
in
a
Project
 •  •  •  •  Define
 Organize
 Manage
execuIon
 Close
 Cast
of
Characters
 •  •  •  •  •  Project
sponsor
 Project
manager
 Team
lead
 Team
members
 Steering
commiSee
 DefiniIon
 •  Project
charter
 –  Scope
(value
to
be
delivered)
 –  Time
 –  Resources
 •  People,
money
 Team
Issues
 •  •  •  •  •  •  Who’s
on?
 How
big?
 How
do
we
work?
 DistribuIon
of
authority
 Skills
mix
 Other
consideraIons
 Project
Plan
 •  •  •  •  •  Work
breakdown
structure
 Dependencies
 ProbabiliIes
 EsImate
are
not
commitments
 OpImizaIon
alternaIves
 Technical
Challenges
 •  Data,
applicaIon,
infrastructure,
interacIon
 layers
 •  Complexity
kills
 •  StandardizaIon
vs.
flexibility
 Management
Issues
 •  Code
is
poliIcal
 –  Embodies
decisions,
not
always
democraIcally
 •  Code
is
expressive
 –  “So#ware
factory”
is
o#en
a
contradicIon
 •  Code
behaves
nonlinearly
(1+1=3)
 –  TesIng
takes
longer
than
anyone
expects
 •  People
are
people
 •  EscalaIon
of
commitment
 ...
View Full Document

This note was uploaded on 04/06/2010 for the course MIS 446 at Pennsylvania State University, University Park.

Ask a homework question - tutors are online