Software engineering:2. Project Management

Resources: "Software Engineering" Ian Sommerville

For most projects, important goals is:

• Deliver the software to customer at the agreed time.
• Keep overall costs within budget.
• Deliver software that meets the customer ' s expections.
• Maintain a happy and well-functioning development team.

Keywords:

• Organizational budget
• Schedule constraints
• Project meets
• High-quality

The Reponsibilities of managers:

• Project Planning
• Reporting
• Risk Management
• People Management
• proposal Writing: The first stage in a software project could involve writing a proposal to win a contract to carry Out a item of work. The proposal describes the objectives of the project and how it would be is carried out. It usually includes costs and schedule estimates and justifies why the project contract should is awarded to a particular Organization or team.

1. Risk Management

Three related categories of risk:

• Project risks:risks that affect the project schedule or resources
  • Example:the loss of experienced designer
• Product risks:risks that affect the quality or performance of the software being developed
  • Example:the failure of a purchased component to perform as expected
• Business Risks:risks that affect the organization developing or procuring the software
  • EXAMPLE:A competitor introducing a new product is a business

Need to draw up contingency plans So, if the risks does occur, you can take immediate recovery action.

Examples of common risks:

• Staff turnover:experienced staff would leave the project before it is finished
• Management Change
• Hardware unavailability
• Requirements Change
• Specification delays
• Size underestimate
• Case Tool Underperformance
• Technology change
• Product Competition

The process of risk management:

1. Risk identification
2. Risk Analysis
3. Risk Planning
4. Risk Monitoring

1.1 Risk Identification

Risk identification May is a team process where a team get together to brainstorm possible risks. Alternatively, the project manager may simply with his or hers experience to identify the most probable or critical Risks.

There is at least six types of risk, the May is included in a risk checklist:

1. Technology risks
2. People risks
3. Organizational Risks:risks that derive from the organizational environment where the software is being developed.
4. Tools Risks
5. Requirements risks
6. Estimation risks:risks that derive from the management estimates of the resources required to build the system.

1.2 Risk Analysis

The probability of the risk might is assessed as very low (<10%), Low (10-25%), moderate (25-50%), High (50-75%), or ve Ry High (>75%)

Once the risks has been analyzed and ranked, you should assess which of these risks is most significant.

1.3 Risk Planning

There is three categoriess for strategies:

1. Avoidance strategies
2. Minimization Strategies
3. Contingency Plans:your is prepared for the worst and has a stratefy in place to deal with it.

1.4 Risk Monitoring

Risk monitoring is the process of checking that your assumptions on the product, process, and business risks has not C Hanged.

2. Managing people

There is four critical factors in people management:

• Consistency:people in a project team should all is treated in a comparable.
• Respect
• Inclusion:people contribute effectively when they feel, others listen to them and take account of their proposals.
• Honesty

If some lose interest in the work, you should sort out of the problem quickly, otherwise the other group members would become Dissatisfied and feel that they is doing an unfair share of the work.

Motivating people

Professionals can classified into three types:

• Task-oriented people:motivated by the work they do
• Self-oriented people:motiviated by personal success
• Interaction-oriented people:motivated by the presence and actions of co-workers. As software development becomes more usercentered, interaction oriented individuals is becoing more involved in software Engineering.

Interaction-oriented personalities usually like to work as part of a group, whereas task-oriented and self-oriented people Usually prefer to act as individuals.

Each individual's motivation is made up to elements of each class but one type of motivation are usually dominant at No on E time.

Individuals can change. For example, technical people who feel they is not being properly rewarded can become self-oriented and put Pers Onal interests before technical concerns. If A group works particularly well, the self-oriented people can become more interaction-oriented.

3. Teamwork

Keywords:cohesiveness

3.1 Selecting Group members

A group that had complementary personalities may work better than a group that's selected solely on technical ability.

3.2 Group Organization

Informal groups: the most group of members is experienced and competent.

Hierarchical Groups [ha?? ' Rɑ?k?k (?) L]: A hierarchical structure with the group leader at the top of the hierarchy

3.3 Group Communications

Group members must exchange:

• Information on the status of their work
• The design decisions that has been made
• Changes to previous design decisions

Group members come to understand the motivations, strengths, and weaknesses of other people in the group.

The effectiveness and efficiency of communications are influenced by:

1. Group size
2. Group structure
3. Group composition
4. The physical work environment
5. The available communication channels

Software engineering:2. Project Management