Project Management
Organising, planning and scheduling software projects.
Software Management Distinctions
- Product is intangible (cannot be seen or touched)
- Software engineering is not recognised an an engineering discipline with same status as mechanical etc
- Software development process is not standardised
- Many software projects are one off projects.
Project Management Activies
- proposal writing
- project planning and scheduling
- project costing
- project monitoring and reviews
- personnel selection and evaluation
- report writing and presentations
Management Commonalities
- these activities are not peculiar to software management
- many techniques of engineering project management are equally applicable to software project management
- complex engineering systems tends to suffer from the same problems as software systems
Project Staffing
May not be possible to appoint the ideal people to work on a project due to budget.
Project Planning
Most time consuming project management activity.
Types of Project Plans
- quality plan
- validation plan
- configuration management plan
- maintenance plan
- staff development plan
Quality Plan
Describes the quality procedures and standards that will be used in the project.
Validation Plan
Describes the approach, resources and schedule used for the system validation.
Configuration Management Plan
Describes the configuration management procedures and structures to be used.
Maintanence Plan
Predicts the maintenance requirements of the system, maintenance costs and effort required.
Staff Development Plan
Describes how the skills and experience of the project team members will be developed.
Project Plan Structure
- introduction
- project organisation
- risk analysis
- hardware and software resource requirements
- work breakdown
- project schedule
- monitoring and reporting mechanisms
Activity Organisation
Activities in a project should be organised to produce tangible outputs for management to judge progress.
Milestones
End-point of process activity.
Deliverables
Project results delivered to customers.
Project Scheduling
Split project into tasks and estimate time and resources required to complete tasks.
Organise tasks concurrently to make optimal use of workforce.
Minimise task dependencies to avoid delays by one task on another task.
Scheduling Problems
Estimating the difficulty of problems and hence the cost of developing a solution is hard.
Productivity != number of people working on task.
Adding people late can make it even later due to communication overheads.
Always allow for contingency in planning.
Bar Charts and Activity Networks
Graphical notation used to illustrate the project schedule.
Activity charts show dependencies and the critical path.
Bar charts show schedule against calendar time.
Tasks should not be too small and should take a week or two.
Risk Management
Concerned with identifying risks and drawing up plans to minimise the effect of those risks on the project.
Product Risks
Affect quality or performance of the software being developed.
Business Risks
Affect the organisation developing or procuring the software.
Pert Charts
Project management tool used to schedule, organize and coordinate tasks within a project.
Includes time frames for tasks, like early start and late end.
Risk Management Process
- risk identification
- risk analysis
- risk planning
- risk monitoring
-
Software Processes22
-
Software Requirements20
-
Use Case Analysis15
-
Requirements Engineering Processes40
-
System Models27
-
Petri Nets16
-
Design Methodology46
-
Architectural Design22
-
Distributed System Architectures16
-
Object Orientated Design12
-
Class Models20
-
Essentials of Interaction Diagrams9
-
Verification and Validation24
-
Software Testing47
-
Project Management34
-
Software Cost Estimation30
