INF3708 - Software Project Management_Summary.

INF3708 - Software Project Management_Summary.*Characteristics that distinguish projects: [10]1 Non-routine tasks are involved. Planning is required. Specific objectives are to be met or a specified product is to be created. The project has a predetermined time span. Work is carried out for someone other than yourself. Work involves several specialisms. People are formed into a temporary work group to carry out the task. Work is carried out in several phases. The resources that are available for use on the project are constrained. The project is large or complex. *Characteristics of software projects which make them particularly difficult (as identified by Fred Brooks): [4]2 Invisibility – When a physical artefact (e.g. a bridge) is constructed the progress can actually be seen. With software, progress is not immediately visible. Complexity – Software products contain more complexity than other engineered artefacts per dollar/pound/euro/rand spent. Conformity – ‘Traditional’ engineers work with physical systems and materials which are governed by consistent physical laws. Software developers have to conform to the requirements of human clients. Flexibility – Software is easy to change (which is one of its greatest strengths) and must therefore change to accommodate the physical or organizational system it interfaces with, not the other way around. Successive processes that bring a new system into being: [3]3 1. Feasibility Study (Is it worth doing?) 2. Plan (How do we do it?) 3. Project Execution (Do it!) 1 p. 3 2 pp. 4-5 3 pp. 5-6 5 ISO 12207 Software Development Life Cycle: [13]4 Requirements: o Requirements analysis. o Architecture design. o Requirements analysis. Design: o Architecture design. o Requirements analysis. Code and Test: o Detailed design. o Code and test. o Integration. o Qualification test. o Integration. o Qualification test. Installation/Acceptance Support: o Installation. o Acceptance Support. Types of Stakeholders: [3]5 A: Internal to the project team (and implicitly to the organization). B: External to the project team, but within the same organization. C: External to both the project team and the organization. 4 pp. 6-8 5 p. 11 Organization Project Team 6 Well-defined objectives are described by: [5]6 SMART: Specific Measurable Achievable Relevant Time constrained Software project objectives: [4]7 The agreed functionality is delivered To the required level of quality On time Within budget Management Activities: [8]8 Planning – Deciding what is to be done. Organizing – Making arrangements. Staffing – Selecting the right people for the job. Directing – Giving instructions. Monitoring – Checking on progress. Controlling – Taking action to remedy hold-ups. Innovating – Coming up with new solutions. Representing – Liaising with clients, users, developer, suppliers and other stakeholders. 6 p. 12 7 p. 14 8 p. 15 7 CHAPTER 2 Business case (for a feasibility study) document contains: [10]9 1. Introduction and background to the proposal 2. The proposed project 3. The market 4. Organizational and operational infrastructure 5. The benefits 6. Outline implementation plan 7. Costs 8. The financial case 9. Risks 10. Management plan Key aspects of project portfolio management: [3]10 Portfolio definition Portfolio management Portfolio optimization Categories of direct costs: [3]11 Development costs – including development staff costs Setup costs – the costs of putting the system into place (new hardware, file conversion, recruitment, staff training). Operational costs – cost of operating the system after installation. *Net Profit12: