1 Software Testing and Quality Assurance Lecture 35 – SWE 205 Course Objective: Basics of Programming Languages & Software Construction Techniques.

Slides:



Advertisements
Similar presentations
1 Note content copyright © 2004 Ian Sommerville. NU-specific content copyright © 2004 M. E. Kabay. All rights reserved. Managing People IS301 – Software.
Advertisements

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 25 Slide 1 Managing people l Managing people working as individuals and in groups.
Drafting your Dream-Team
©Ian Sommerville 2000 Software Engineering, 7th edition. Chapter 25Slide 1 Managing people l Managing people working as individuals and in groups l People.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 25 Slide 1 Managing people (individuals and in groups)
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 25 Slide 1 CHAPTER 25: Managing people l Managing people working as individuals and in.
SWEN 5130 Requirements EngineeringSlide 1 Software Prototyping u Animating and demonstrating system requirements.
1 CS 501 Spring 2005 CS 501: Software Engineering Lecture 23 People 1.
How to survive an Interview
The team Definition: a group of people working together. Everyone who is to be part of a software development team, must have a good understanding of the.
MOTIVATION. A Talk With The Director of A Research Institute What has been the hardest job for you as a director? How to convince people that by cooperating.
Software Engineering Process - II
People in the process People are an organisation’s most important assets The tasks of a manager are essentially people oriented. Unless there is some.
1 R&D SDM 1 Software Project Management Team Management Project organizations 2009 Theo Schouten.
R&D SDM 1 Software Project Management Team Management Project organizations 2010 Theo Schouten.
CS CS 5150 Software Engineering Lecture 23 People 1.
1 SWE Introduction to Software Engineering Lecture 6 - Software Project Management.
1 CS 501 Spring 2003 CS 501: Software Engineering Lecture 24 People I.
1 Software Testing and Quality Assurance Lecture 35 – SWE 205 Course Objective: Basics of Programming Languages & Software Construction Techniques.
1 Lecture 6 The Systems Analyst (Role and activities) Systems Analysis & Design Academic Year 2008/9.
Chapter 22 – Project Management Lecture 1 1Chapter 22 Project management.
Effective Groups and Teams by Suhel Khan McGraw-Hill/Irwin Contemporary Management, 5/e Copyright © 2008 The McGraw-Hill Companies, Inc. All rights reserved.
Effective Groups and Teams
Succeeding as a Systems Analyst, Roles Class 2. First, some definitions Systems Development Specifying in detail how the many components of the information.
Chapter 22 Project management
1 The leadership role of the supervisor The primary role of the supervisor is to ensure that a group of people work together to achieve the goals set by.
Managing people Managing people working as individuals and in groups.
Effective Team Management
Software Engineering Muhammad Fahad Khan
Chapter 22 – Project Management Lecture 1 1Chapter 22 Project management.
Level 2 Unit 6 Application of Manufacturing Techniques in Engineering Engineering Diploma Level 2 Unit 6 Application of Manufacturing Techniques in Engineering.
Objectives 4 Understand the importance of communication in projects 4 Understand the need and importance of project management.
People Management Mrs. K. Gooljar.
Chapter 22 – Project Management 1Chapter 22 Project management Ian Sommerville, Software Engineering, 9 th Edition Pearson Education, Addison-Wesley Note:
Managing people l Managing people working as individuals and in groups.
Managing people Managing people working as individuals and in groups People are an organisation’s most important assets 1.
1 CS 501 Spring 2002 CS 501: Software Engineering Lecture 20 Managing People.
Software Engineering, 8th edition Chapter 25 1 Courtesy: ©Ian Somerville 2006 May 04 th, 2009 Lecture # 20 Managing people l Managing people working.
Applied Software Project Management Andrew Stellman & Jennifer Greene Applied Software Project Management Applied Software.
Software Prototyping Rapid software development to validate requirements.
Chapter 22 – Project Management
Chapter 22 – Project Management 04/12/2014Chapter 22 Project management1.
Chapter 6 – Project Management Lecture 1 1Chapter 22 Project management.
UELSU Programme Representatives Using your experience to demonstrate key skills Wed 25 th Nov 2015.
CS 240, Prof. Sarwar Slide 1 CS 240: Software Project Fall 2003 Sections 1 & 2 Dr. Badrul M. Sarwar San Jose State University Lecture #19.
Effective Teamwork Team Building
1 / 28 CS 425/625 Software Engineering Managing People Based on Chapter 22 of the textbook [Somm00] Ian Sommerville, Software Engineering, 6 th Ed., Addison-Wesley,
Effective Groups and Teams Handout # Explain why groups and teams are key contributors to organizational effectiveness. Identify the different.
Systems Analyst (Module V) Ashima Wadhwa. The Systems Analyst - A Key Resource Many organizations consider information systems and computer applications.
1 TEAM BUILDING & MANAGEMENT. 2 CONTENTS Generalities The individual The individual in the group To manage the group The group manager The group facing.
Effective Groups and Teams chapter fifteen Copyright © 2014 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill/Irwin.
Lecturer: Eng. Mohamed Adam Isak PH.D Researcher in CS M.Sc. and B.Sc. of Information Technology Engineering, Lecturer in University of Somalia and Mogadishu.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 25 Slide 1 Managing people l Managing people working as individuals and in groups.
PROJECT MANAGEMENT Software Engineering CSE
Managing people working as individuals and in groups Managing people.
1 Note content copyright © 2004 Ian Sommerville. NU-specific content copyright © 2004 M. E. Kabay. All rights reserved. Managing People IS301 – Software.
CSC 480 Software Engineering
People and organizational issues in Testing
Chapter 22 – Project Management
CSE 403 Software Engineering
Chapter 22 – Project Management
Chapter 22 – Project Management
Overview Why do we need software project management?
CSE305 Software Engineering
Chapter 22 – Project Management
Chapter 22 – Project Management
Managing People Managing people working as individuals and in group
CHAPTER 25: Managing people
Introduction Software maintenance:
Presentation transcript:

1 Software Testing and Quality Assurance Lecture 35 – SWE 205 Course Objective: Basics of Programming Languages & Software Construction Techniques

2 Lecture Outline To explain some of the issues involved in selecting and retaining staff To describe factors that influence individual motivation To discuss key issues of team working including composition, cohesiveness and communications

3 People in the process People are an organisation’s most important assets. The tasks of a manager are essentially people-oriented. Unless there is some understanding of people, management will be unsuccessful. Poor people management is an important contributor to project failure.

4 People management factors Consistency Team members should all be treated in a comparable way without favourites or discrimination. Respect Different team members have different skills and these differences should be respected. Inclusion Involve all team members and make sure that people’s views are considered. Honesty You should always be honest about what is going well and what is going badly in a project.

5 Selecting staff An important project management task is team selection. Information on selection comes from: Information provided by the candidates. Information gained by interviewing and talking with candidates. Recommendations and comments from other people who know or who have worked with the candidates.

6 Staff selection case study 1

7 Staff selection case study 2

8 Lessons Managers in a company may not wish to lose people to a new project. Part- time involvement may be inevitable. Skills such as UI design and hardware interfacing are in short supply. Recent graduates may not have specific skills but may be a way of introducing new skills. Technical proficiency may be less important than social skills.

9 Staff selection factors FactorsDescription Application Domain Experience The developers must understand the application domain. It is essential that some members of a development team have some domain experience. Platform Experience Important, if role involves low- level programming.

10 Staff selection factors FactorsDescription Problem solving ability Important for software engineer Constantly involved in solving technical problems. Communicat ion ability Need for project staff to communicate orally and writing with other engineers, mangers and customers.

11 Motivating people An important role of a manager is to motivate the people working on a project. Motivation is a complex issue but it appears that their are different types of motivation based on: Basic needs (e.g. food, sleep, etc.); Personal needs (e.g. respect, self-esteem); Social needs (e.g. to be accepted as part of a group).

12 Individual motivation

13 Personality types The needs hierarchy is almost certainly an over-simplification of motivation in practice. Motivation should also take into account different personality types: Task-oriented; Self-oriented; Interaction-oriented.

14 Personality types Task-oriented. The motivation for doing the work is the work itself; Self-oriented. The work is a means to an end which is the achievement of individual goals - e.g. to get rich, to play tennis, to travel etc.; Interaction-oriented The principal motivation is the presence and actions of co-workers. People go to work because they like to go to work.

15 Managing groups Most software engineering is a group activity The development schedule for most non- trivial software projects is such that they cannot be completed by one person working alone. Group interaction is a key determinant of group performance. Flexibility in group composition is limited Managers must do the best they can with available people.

16 Factors influencing group working Group composition. Group cohesiveness. Group communications. Group organisation.

17 Group composition Group composed of members who share the same motivation can be problematic Task-oriented - everyone wants to do their own thing; Self-oriented - everyone wants to be the boss; Interaction-oriented - too much chatting, not enough work. An effective group has a balance of all types. This can be difficult to achieve software engineers are often task-oriented. Interaction-oriented people are very important as they can detect and defuse tensions that arise.

18 Group cohesiveness In a cohesive group, members consider the group to be more important than any individual in it. The advantages of a cohesive group are: Group quality standards can be developed; Group members work closely together so inhibitions caused by ignorance are reduced;

19 Group cohesiveness Team members learn from each other and get to know each other’s work; Egoless programming where members strive to improve each other’s programs can be practised.

20 Key Points Staff selection factors include education, domain experience, adaptability and personality. People are motivated by interaction, recognition and personal development. Software development groups should be small and cohesive.