170 likes | 188 Views
Art for Chapter 14, Project Management. Termination. do/Client Acceptance. do/Delivery. do/Post Mortem. Figure 14-1, Phases of a Software Project. ScopeDefined. GoAhead. Conception. Start. do/FormulateIdea. do/Infrastructure Setup. do/Cost-BenefitAnalysis. Definition.
E N D
Termination do/Client Acceptance do/Delivery do/Post Mortem Figure 14-1, Phases of a Software Project ScopeDefined GoAhead Conception Start do/FormulateIdea do/Infrastructure Setup do/Cost-BenefitAnalysis Definition do/Skill Identification do/FeasibilityStudy do/Team Formation do/Problem Statement do/Review do/Project Kickoff do/Software Architecture do/Software Plan Infrastructure Setup Completed New Need Steady State && Teams New Technology Assembled do/Develop System do/Controlling do/Risk Management do/Replanning System Done
Project Kick-off Formulate Idea Project Agreement Problem Statement Initial Software Definition Architecture Team assembly Infrastructure setup Figure 14-2, Management activities in a software project (continued on next slide). Conception Cost-Benefit Analysis Feasibility Study Definition Initial Software Project Management Plan Start Skill Identification
Figure 14-2, Management activities in a software project (continued). Steady state Controlling Risk management Project replanning Scope agreement Termination Installation Client acceptance test Postmortem
Figure 14-3, Tasks, Activities and Project Functions. Work * Task Activity «invariant» duration = project.duration Project Function
Figure 14-4, Relationship between Outcome, Work, and Work Packages. Work Package describes produced-by * * Outcome Work * Set of Work Products Work Product Task Activity Internal Work Product Project Deliverable Project Function
Figure 14-5, The Work Breakdown Structure is the aggregation of all the work to be performed in a project. Work Breakdown Structure Work * * Task Activity
Install Tubs & Sinks Figure 14-6, Partial work breakdown structure for a house. Build Foundation Build Structure Build Walls Build Roof Install Sewer Pipes Install Cold & Hot Water Pipes Build House:WBS Install Plumbing Install Heating Install Electric
Figure 14-7. An example of a task model with precedence dependencies Database subsystem req. elicitation Database subsystem design Database subsystem implementation Database subsystem test plan Database subsystem inspection Database subsystem test
Figure 14-8, An organization consists of organizational units, which consists of participants or groups of participants. Organization Organizational Unit * * Project Company Participant Staff Team Department Division
Line (Functional) Project-Based Organization Organization Matrix Organization Figure 14-9, Types of organizations.
Figure 14-10, Example of a organization chart for a team-based organization with three subsystem teams and two cross-functional teams. Management :Team reports to reports to reports to reports to reports to communicates with communicates with UserInterface Control :SubsystemTeam :SubsystemTeam Database :SubsystemTeam communicates with communicates with Architecture: Documentation: CrossFunctionalTeam CrossFunctionalTeam
Figure 14-11, Visualization of the organization structure from Figure 14-10 with an organization chart. The reporting and communication structure are not shown explicitly.
Figure 14-12, Model of a Project from a project manager’s point of view. This is a refinement of the model used in Chapter 3. Equipment Project * Facility Resource Fund * Organi- Work zation des- Breakdown Work Structure cribes Schedule Package con- * * sumes * * produces Organizational respon- Outcome Work Unit sible * * * plays for depends Role Set of Work Work Staff Activity Task Participant Products Product Project Internal Department Team Project Function Work Product Deliverable
Problem Statement Top-level Design Organization Software Project Task Model Management Plan (SPMP) Figure 14-14, Work products generated during project planning and their relationship with typical project deliverables. Deliverables Project Planning Products Project Agreement Requirements Analysis Document (RAD) System Design Document (SDD) Schedule
Figure 14-17, An example of an object-oriented work breakdown structure where the subsystem decomposition is used to identify high-level activities/tasks. Subsystem decomposition Work Breakdown Structure Develop UserInterface System Develop Control Develop Subsystem Control UserInterface Develop Database Database Subsystem
Figure 14-18, Assessing the financial status of a project using earned value. Planned cost Earned value Actual cost Time Current time