Project management
Software EngineeringCOMP 201Lecturer: Sebastian CoopeAshton Building, Room G.18E-mail: [email protected]
COMP 201 web-page:http://www.csc.liv.ac.uk/~coopes/comp201
Project Management
1COMP201 - Software Engineering1Project ManagementOrganising, planning and scheduling software projects2COMP201 - Software EngineeringObjectivesTo introduce software project management and to describe its distinctive characteristicsTo discuss project planning and the planning processTo show how graphical schedule representations are used by project managementTo discuss the notion of risks and the risk management process3COMP201 - Software EngineeringTopics CoveredManagement activitiesProject planningProject schedulingRisk management4COMP201 - Software EngineeringSoftware Project ManagementConcerned with activities involved in ensuring that software is delivered on time and on schedule and in accordance with the requirements of the organisations developing and procuring the softwareProject management is needed because software development is always subject to budget and schedule constraints that are set by the organisation developing the software5COMP201 - Software EngineeringSoftware Management DistinctionsThe product is intangible (cannot be seen or touched)Software engineering is not recognized as an engineering discipline with the same status as mechanical, electrical engineering, etc.The software development process is not standardisedMany software projects are 'one-off' projects6COMP201 - Software EngineeringManagement ActivitiesProposal writingProject planning and schedulingProject costingProject monitoring and reviewsPersonnel selection and evaluationReport writing and presentations7COMP201 - Software EngineeringManagement CommonalitiesThese activities are not peculiar to software managementMany techniques of engineering project management are equally applicable to software project managementTechnically complex engineering systems tend to suffer from the same problems as software systems8COMP201 - Software EngineeringProject StaffingMay not be possible to appoint the ideal people to work on a projectProject budget may not allow for the use of highly-paid staffStaff with the appropriate experience may not be availableAn organisation may wish to develop employee skills on a software projectManagers have to work within these constraints especially when (as is currently the case) there is an international shortage of skilled IT staff9COMP201 - Software EngineeringProject PlanningProbably the most time-consuming project management activityContinuous activity from initial concept through to system delivery. Plans must be regularly revised as new information becomes availableVarious different types of plan may be developed to support the main software project plan that is concerned with schedule and budget 10COMP201 - Software EngineeringTypes of Project Plan
11COMP201 - Software EngineeringProject Plan StructureIntroductionProject organisationRisk analysisHardware and software resource requirementsWork breakdownProject scheduleMonitoring and reporting mechanisms12COMP201 - Software EngineeringActivity OrganizationActivities in a project should be organised to produce tangible outputs for management to judge progressMilestones are the end-point of a process activityDeliverables are project results delivered to customersThe waterfall process allows for the straightforward definition of progress milestones13COMP201 - Software EngineeringMilestones in the RE Process
14COMP201 - Software EngineeringProject SchedulingSplit project into tasks and estimate time and resources required to complete each taskOrganize tasks concurrently to make optimal use of workforceMinimize task dependencies to avoid delays caused by one task waiting for another to completeDependent on project managers intuition and experience15COMP201 - Software EngineeringScheduling ProblemsEstimating the difficulty of problems and hence the cost of developing a solution is hardProductivity is not proportional to the number of people working on a taskAdding people to a late project can make it even later because of communication overheadsThe unexpected always happens. Always allow for contingency in planning16COMP201 - Software EngineeringBar Charts and Activity NetworksGraphical notations used to illustrate the project scheduleShow project breakdown into tasks. Tasks should not be too small. They should take about a week or twoActivity charts show task dependencies and the critical pathBar charts show schedule against calendar time17COMP201 - Software EngineeringTask Durations and Dependencies18COMP201 - Software EngineeringTaskDuration (days)DependenciesT18T215T315T1(M1)T410T510T2,T4 (M2)T65T1,T2 (M3)T720T1 (M1)T825T4 (M5)T915T3,T6 (M4)T1015T5,T7 (M7)T117T9(M6)T1210T11(M8)Activity Network
19COMP201 - Software EngineeringMinimal Time to finish -> Length of longest (critical) path -> 55 daysActivity Timeline
20COMP201 - Software EngineeringStaff Allocation
21COMP201 - Software EngineeringRisk ManagementRisk management is concerned with identifying risks and drawing up plans to minimise their effect on a project.A risk is a probability that some adverse circumstance will occur. Project risks affect schedule or resourcesProduct risks affect the quality or performance of the software being developedBusiness risks affect the organisation developing or procuring the software22COMP201 - Software EngineeringThe Risk Management ProcessRisk identificationIdentify project, product and business risksRisk analysisAssess the likelihood and consequences of these risksRisk planningDraw up plans to avoid or minimise the effects of the riskRisk monitoringMonitor the risks throughout the project23COMP201 - Software EngineeringRisk IdentificationTechnology risksPeople risksOrganisational risksRequirements risksEstimation risks24COMP201 - Software EngineeringRisks and Risk Types
25COMP201 - Software EngineeringRisk AnalysisAssess probability and seriousness of each riskProbability may be very low, low, moderate, high or very highRisk effects might be catastrophic, serious, tolerable or insignificant26COMP201 - Software EngineeringRisk Analysis
27COMP201 - Software EngineeringRisk PlanningConsider each risk and develop a strategy to manage that riskAvoidance strategiesThe probability that the risk will arise is reducedMinimisation strategiesThe impact of the risk on the project or product will be reducedContingency plansIf the risk arises, contingency plans are plans to deal with that risk28COMP201 - Software EngineeringRisk Factors
29COMP201 - Software EngineeringProject management ToolsThe best tools are online, sinceEasy to access anywhereDont require you to set up any softwareExample toolsToo many to list here.. But have a look at ZohoZoho is free and very powerfulIt has task handling, Gannt charts and milestonesFree for
