90 likes | 254 Views
Managing Information System Development Projects. IS 460 Notes by Thomas Hilton. System Development Life Cycle (SDLC). Feasibility Study: Scope, Stakeholders, Make-buy, CBA Analysis: Present System, DFDs, etc. Design : General, Detailed
E N D
Managing Information System Development Projects IS 460 Notes by Thomas Hilton
System DevelopmentLife Cycle (SDLC) • Feasibility Study: Scope, Stakeholders, Make-buy, CBA • Analysis: Present System, DFDs, etc. • Design: General, Detailed • Construction: Hardware Acquisition, Software Coding, System Testing • Implementation: Direct, Phased, Site, Simultaneous • Maintenance: Errors, Changing Business Needs • Start Over when maintenance costs exceed new system costs.
Other Development Models • Waterfall vs. Spiral • Prototyping • Rapid Application Development (RAD) • Joint Application Development (JAD) • Agile • Extreme
Managing the Project: Teams and Roles • Team Lead • System Analyst • Programmer • User Documentation/Training Specialist • Project Librarian • Quality Assurance Specialist
Managing the Project: Schedules • Gantt Charts(MS Project) • PERT Charts(Visio) • Critical Path Charts(Rational Rose)
Managing the Project: Costs • Feasibility Study 5% • Analysis 10% • Design 10% • Construction 25%-50% • Implementation 25%-50% • Maintenance 5%* *annual cost as percent of initial project
Cost-Benefit Analysis • Quantify all Costs • Quantify all Benefits • If Benefits Exceed Costs, Do It. • CBA is Cost-Biased: • Many Costs are Present and Tangible • Many Benefits are Future and Intangible • Must Have a Champion!
Estimating Time & Cost • W.A.G. • Consult Past Projects • Break Down Phases into Tasks and Tasks into Steps • Average Best & Worst Case • Add a Fudge Factor from Experience
Ethics Issues • Pressure to Accept Unrealistic Parameters from Stakeholders • GroupThink • Working Conditions • Team Member Relationships • Vendor Relationships • Hiding Mistakes • Other?