Project Planning Project ManagementPlan for TonightPowerPoint PresentationWhy Project Planning?Project Initiation and Planning – In a nutshellInitiating the projectProject Planning stepsGraphProject Planning Steps continuedSlide 10Economic FeasibilityCosts and BenefitsSlide 13Project ManagementProject success factorsReadingsExpect problemsTriple ConstraintsThinking of EverythingProject TrackingPMBOKFor Next Session…Project PlanningProject ManagementWeek 3CMIS570Plan for TonightPick up Homework #1 – Problem statementProject PlanningFeasibility AnalysesProject ManagementSDLCProject Planning***AnalysisDesignImplementationSupportWhy Project Planning?Transforms a vague system request document into a tangible project description.Set up communication plan – SA&D requires effective communication between the systems analysts, users, and management.Essential for successful projectsProject Initiation and Planning – In a nutshellThis is the point where a systems analyst begins to play a major role in the systems development process.Initiating the projectEstablish the teamInitial plan/scopeInitial project scopeInitial feasibilityProject Planning stepsDefine the problemGraphInclude figure 3-8Project Planning Steps continuedProduce the project scheduleProject Planning Steps continuedConfirm project feasibilityEconomicOrganizational/CulturalTechnologicalScheduleResourceEconomic FeasibilityIdentifying the financial benefits and costs associated with the project (CBA)At this point, probably do not know enough to complete in detail.What can be done: list tangible and intangible costs and benefits.Costs and BenefitsTangible BenefitsIntangible BenefitsTangible CostsOne-timeRecurringIntangible CostsProject Planning Steps continuedStaff and launch the projectProject ManagementCharacteristics of a ProjectProject success factorsClear system requirement definitionsSubstantial user involvementSupport from upper managementThorough and detailed project plansRealistic work schedules and milestonesReadingsMore on Project ManagementFive steps:DefinePlanImplementControlCloseExpect problems“Sure, if everyone got along, showed up, worked hard, had no accidents, stayed on task, wasn’t interrupted, didn’t have 10 other important responsibilities, and our friend Murphy never showed up, this project might be a piece of cake.” (p. 27)Triple ConstraintsWhen problems arise, consider the triple constraints carefully before acting.Your new role: Detective! See page 32 for good questions.Thinking of EverythingDeals with setting up the WBS and Project SchedulingQuality of WBS will depend on how well you defined your project.Project TrackingAmbiguity is your friendEscalating commitment is notHow much and what are you collecting?PMBOKGet slides from Appendix AFor Next Session…Gantt chart dueRead chapter 4Read chapter 5 pp.
View Full Document