1 / 32

Project

Project. What is a project A temporary endeavor undertaken to create a unique product, service or result. What is a Project?. Temporary Goal-directed Collaborative Constrained Endeavor. What is Project Management?.

guillermina
Download Presentation

Project

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Project • What is a project • A temporary endeavor undertaken to create a unique product, service or result

  2. What is a Project? • Temporary • Goal-directed • Collaborative • Constrained • Endeavor

  3. What is Project Management? • Project management is the applicationof knowledge, skills, tools and techniques to project activities in order to meet or exceedstakeholder needs and expectations from a project.

  4. PM Development Objective • On Schedule • Within Budget • According to specification

  5. Project Management Process • Initiating Processes • Planning Processes • Executing Processes • Controlling Processes • Closing Processes

  6. Project Management Problems • Requirements • Incomplete • Unclear • Inadequate • External dependencies

  7. Project Management Problems • Poor estimates • Inadequate tracking or supervision • Uncontrolled changes • Inadequate testing procedures • Inadequate documentation • Politics

  8. Role of the Project Manager • Leadership and Guidance • Planning • Customer Relations • Technical Leadership • Senior Management Liaison

  9. Handling Large Projects • Project Decomposition • Stepwise Refinement • Functional Decomposition • Design Decomposition • Work Breakdown Structures (WBS)

  10. Why to Project Decomposition • Project Decomposition • F(xyz)q = F(x)q + (y)q + (z)q • A complex project can be divided into simpler components. Each component is easier to handle. • System development projects are decomposed into smaller components in order to provide better estimates of the amount of the amount of work involved and to monitor and manage the various activities of the development team.

  11. Stepwise Refinement • Stepwise Refinement • Stepwise refinement are iterative methods because each iteration decomposes the system further. Systems Component 1 Component 2 Component 3 2.1 2.2 2.3 2.1.1 2.1.2 2.2.1 2.2.2 2.3.1 2.3.2

  12. Functional Decomposition • Functional Decomposition • Functional decomposition of a software project is a division of the system into its operational components as they are seen by the user. • The objective is to define all the characteristics of the system from the user’s perspective.

  13. Functional Decomposition

  14. Design Decomposition • Design Decomposition • Is a division of the system into lower level components that coincide with the actual software components of the systems. • In a full design decomposition of a software system, the lowest components correspond to programming modules (e.g. procedures, subroutines, or program functions) • Requirement Functional decomposition Design Decomposition.

  15. Design Decomposition The best design would strive to produce independent software components or modules. Good design will strive for low coupling, high cohesion and information hiding.

  16. Work Breakdown structure • WBS • This is the division of the IT project into basic work components • The sum total of these work components covers all the tasks that need to be performed in order to complete the project successfully. • Materials • Functions • People

  17. WBS • Project Decomposition • Development tasks • Managerial tasks • Support tasks • Administrative tasks

  18. WBS

  19. WBS

  20. Managing Large Projects

  21. Project Reporting Techniques • Period written status report • Verbal reports • Status meetings • Product demonstrations (demo)

  22. Status Reports • Status Reports Format • Red flags • Problems that require the immediate attention of the PM. • Activities during the report period (2 weeks). • This should be linked to WBS • Planned activities for the next report period • Major activity planned for the next report period • Problems and general issues • Issues not yet resolved from the last period • Holidays, Vacation, • New project members, etc. • Date, report period, Name of report, Who is submitting the report.

  23. Some Basic Problems(management errors) • Poor estimates • Budget, Schedule, development resources, technical estimates • Inadequate tracking and supervision • Uncontrolled changes • Poor testing procedures • Poor development documentation

  24. Risk • Foresight is an excellent PM quality • Ability to anticipate problem • What is Risk? • An uncertain event or condition that, if it occurs, has a positive or negative effect on a project’s objectives. • PMI (project management institute)

  25. Risk Analysis • Risk analysis includes estimating its probability, evaluating its impact and preparing for solution in advance. • Risk analysis is not free • Project size/complexity vs. risk

  26. Risk and system complexity Risk Technical Cost Schedule System Complexity

  27. Successful Risk Management • SEI summaries successful risk management as follows • A successful risk management practice is one in which risks are continuously identified and analyzed . • Risks are mitigated, tracked, and controlled to effectively use program resources. • Problems are prevented before they occur and personnel consciously focus on what could affect product quality and schedules

  28. Common risk factors • Risk factors • Lack of top management commitment to the project • Failure to gain user commitment • Misunderstanding the requirement • Lack of adequate user involvement • Failure to manage end user expectation • Changing scope and objectives • Lack of required knowledge/skill in the project personnel • New technology • Insufficient / inappropriate staffing • Conflict between user departments

  29. Anticipating Problems • Step One • Do a review of all project technical and administrative plans • Project development plan • Requirement specifications • Design specification • Personnel • External sources • Etc • Step two • Compile a list of all anticipated problems and describe the potential effect of each problem on the project.

  30. Late delivery of hardware Communication and Networks problem Staff … …. If vendor don’t deliver the system by date the integration will be delayed and it will have effect on cost and schedule. Too slow to support the new system upgrade must be completed before testing Problem with so and so with respect to bla bla. Especially the resources from other the “side” Problem and Description

  31. Risk Analysis Stage • Evaluation of the anticipated risk • Estimate the probability that the risk will occur • Estimate the impact of the problem on the project • Attribute a measure of severity to the problem • Contingency plan

More Related