1 / 37

SOFTWARE PROJECT MANAGEMENT

Learn the tasks of a project manager, steps in project planning, organizing activities, staffing, directing projects, and controlling software projects effectively. Discover strategies for handling risks, project constraints, and different management structures.

crawley
Download Presentation

SOFTWARE PROJECT MANAGEMENT

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. SOFTWARE PROJECT MANAGEMENT Rochelle Elva

  2. OVERVIEW • Introduction to project management • Tasks of SPM • Characteristics of good SPM • Types of management structures • Project constraints and management tools • Summary and questions

  3. INTRODUCTION SOFTWARE PROJECT MANAGEMENT

  4. Tasks of the Project Manager • Planning • Organizing • Staffing • Directing • Controlling

  5. Steps in project planning • Set objectives • Develop project strategies • Develop project policies • Conduct Risk assessment • Identify alternate solutions or courses of action • Develop project plan(tasks, size, schedule)

  6. Organizing activities • Identification and grouping functions and activities • Creating organizational positions • Definition of responsibilities • Documentation of organizational decisions

  7. Staffing of Software Project Requirements Analysis Analysis System Design Designer Program Design Programmer Program Implementation Unit Testing Integration Testing Testing Team System Testing System Delivery Trainer Maintenance

  8. Directing Project • Build teams • Provide leadership • Coordinate and facilitate communication between stakeholders • Supervise and motivate personnel • Resolve conflict

  9. Controlling software projects • Develop standards of performance • Establish monitoring and reporting systems • Task Milestones • Work products • Quality assurance • Measure and analyze results • Initiate corrective actions • Reward and discipline • Document controlling methods

  10. Strategies for handling Risk • Crisis management: fight fires after risks turn into full-blown problems • Fix on failure: early detection and quick reaction when risks materialize • Risk mitigation: have contingency plans, but do nothing to eliminate them in the first place • Risk prevention: identify risks and prevent them from becoming problems • Elimination of root causes: remove factors that make risks possible

  11. Question • You are at an interview for a job as a SPM • Interviewer asks what is philosophy for risk management • What do you say? • What is your rationale for your answer?

  12. CHARACTERISTICS OF GOOD SPM • Leadership • Communications (verbal, written) • Problem Solving • Negotiating • Influencing the organization • Mentoring • Process and technical expertise • Need to be an expert in software engineering and project management

  13. Types of Management • Democratic decentralize • Rotates the task coordinators • Decisions are made by group consensus • Controlled decentralized • There is a permanent team lead • Whole group is involved in problem solving • Subgroup implements solutions • Controlled centralized • Top level problem solving is used • Internal coordination is managed by the team lead

  14. Centralized management • Hierarchical structure of communication • Highly structured • Definite team lead • Communications are vertical • Narrow span of control • Employees tend to work in departments

  15. Decentralized management • Communications are mostly horizontal • There is no real leader • All group members participate in problem solving and decision making

  16. Pros of Centralized Management • There is an obvious point of reference to solve problems • Less time wasted in useless discussions • Decisions are made quickly • Tasks are completed on schedule • Best for simple projects

  17. Cons of Centralized Management • Group morale and goal motivation are low • Quality of project depends greatly on leadership qualities of lead • Untapped creativity of other group members • Not appropriate for large innovative projects

  18. Pros of Decentralized management • Good for long-term continuing projects • Good where there are no time constraints • Good for difficult problems where pooling of ideas is essential • Exhibit greatest job satisfaction • Generate more and better solutions to problems • Encourage creativity

  19. Cons of Decentralized Management • Not good for rushed, or crucial projects • Because there is no one point of failure, individuals participate in more risky behaviour • Group performance is negatively correlated with co-operation requirements

  20. Project Constraints

  21. Critical part of project success is to meet the deadline!

  22. Scheduling tools • (CPA) Critical Path Analysis • Mathematical algorithm for scheduling project activities • How • List activities necessary for project • List time for each activity • Identify dependencies • Graph information • Find longest path to completion- this is CP

  23. Sample Critical Path Analysis(Make Coffee)

  24. Sample Critical Path Analysis(Make Coffee)

  25. Graph G A E D B F C

  26. Node Layout ESTi EFTi ti i LFTi LSTi

  27. CPA is done in 2 steps • Forward pass • Backward pass

  28. Forward Pass • Determines earliest time each activity can start and finish • Determines total duration of project

  29. EST and EFT

  30. EST and EFT

  31. Backward Pass • Determines latest time each activity can start and finish without delaying completion. • Helps determine where slack can be permitted.

  32. LFT and LST

  33. LFT and LST

  34. Cost Control Tools • COCOMO • Lines of code • Function point analysis

  35. Quality Assurance Tools • Audits • Trend Data • Direct measure of software metrics • Failure analysis • Software testing

  36. Quick Summary

  37. Resources • http://www.cs.toronto.edu/~sme/CSC444F/slides/L03-ProjectManagement.pdf • http://www.comp.glam.ac.uk/Teaching/projectmanagement/principles2f.htm • http://www.engin.umd.umich.edu/CIS/course.des/cis375/lectures/lec2_files/frame.htm • http://ubiety.uwaterloo.ca/~tveldhui/teaching/SE362.S2008/slides/1.pdf

More Related