Lecture Introduction to software engineering - Week 3: Project management

Lecture Introduction to software engineering - Week 3: Project management. In this chapter, you will learn to: Project planning, risk management, managing people, teamwork. Invite you to find out the detailed content.
Nội dung trích xuất từ tài liệu:
Lecture Introduction to software engineering - Week 3: Project management Week 3: Project management Nguyễn Thị Minh Tuyền Adapted from slides of Ian Sommerville CuuDuongThanCong.com https://fb.com/tailieudientucntt Topics covered 1. Project planning 2. Risk management 3. Managing people 4. Teamwork 2 CuuDuongThanCong.com https://fb.com/tailieudientucntt Software project management £ Concerned with activities involved in p ensuring that software is delivered on time and on schedule and p accordance with the requirements of the organisations developing and p procuring the software. £ Is needed because ... p software development is always subject to budget and schedule constraints that are set by the organisation developing the software. £ Good management cannot guarantee project success. However, bad management usually results in project 3 failure. CuuDuongThanCong.com https://fb.com/tailieudientucntt Success criteria £ Important goals for most projects: p Deliver the software to the customer at the agreed time. p Keep overall costs within budget. p Deliver software that meets the customer’s expectations. p Maintain a happy and well-functioning development team. 4 CuuDuongThanCong.com https://fb.com/tailieudientucntt Software management distinctions £ The product is intangible. p Software cannot be seen or touched. £ Many software projects are 'one-off' projects. p Large software projects are usually different in some ways from previous projects. £ Software processes are variable and organization- specific. p We still cannot reliably predict when a particular software process is likely to lead to development problems. 5 CuuDuongThanCong.com https://fb.com/tailieudientucntt Factors influencing project management £ Company size £ Software customers £ Software size £ Software type £ Organizational culture £ Software development processes These factors mean that project managers in different organizations may work in quite different ways. 6 CuuDuongThanCong.com https://fb.com/tailieudientucntt Universal management activities £ Project planning p Project managers are responsible for planning, estimating and scheduling project development and assigning people to tasks. £ Reporting p Project managers are usually responsible for reporting on the progress of a project to customers and to the managers of the company developing the software. £ Proposal writing p Project managers write a proposal to win a contract to carry out an item of work. The proposal describes the objectives of the project and how it will be carried out. 7 CuuDuongThanCong.com https://fb.com/tailieudientucntt Universal management activities £ Risk management p Project managers assess the risks that may affect a project, monitor these risks and take action when problems arise. £ People management p Project managers have to choose people for their team and establish ways of working that leads to effective team performance. 8 CuuDuongThanCong.com https://fb.com/tailieudientucntt Topics covered 1. Project planning 2. Risk management 3. Managing people 4. Teamwork 9 CuuDuongThanCong.com https://fb.com/tailieudientucntt Project planning £ One of the most important jobs of a software project manager. £ Project planning involves p break down the work into parts and assign these to project team members, p anticipate problems that might arise and prepare tentative solutions to those problems. £ The project plan p created at the start of a project, p used to communicate how the work will be done to the project team and customers, and to help assess progress on the project. 10 CuuDuongThanCong.com https://fb.com/tailieudientucntt Planning stages £ At the proposal stage p when you are bidding for a contract to develop or provide a software system. £ During the project startup phase p when you have to plan who will work on the project, how the project will be broken down into increments, how resources will be allocated across your company, etc. £ Periodically throughout the project p when you modify your plan in the light of experience gained and information from monitoring the progress of the work. 11 CuuDuongThanCong.com https://fb.com/tailieudientucntt Proposal planning £ Planning may be necessary with only outline software requirements. £ The aim is to provide information that will be used in setting a price for the system to customers. £ Project pricing involv ...