NJIT 1 Managing Technical People Ian Sommerville, Software Engineering, Chapter 22 Gerald Weinberg, The Psychology of Computer Programming, and many other.

Slides:



Advertisements
Similar presentations
Motivation at Work.
Advertisements

©Ian Sommerville 2000 Software Engineering, 7th edition. Chapter 25Slide 1 Managing people l Managing people working as individuals and in groups l People.
Development Process. Four Factors People –10 to 1 variation in programmer productivity with the same experience Process –Methodology Product –Size Technology.
Software Project Management.  Leadership  Communications  Problem Solving  Negotiating  Influencing the Organization  Mentoring  Process.
Motivation One of the most critical skills for effective leadership and management is the ability to motivate others. A motive is a need, desire, or other.
Managing Small Business Chapter 16. Management What do manager do?  Plan – Developing management strategy, business plans, organizational goals, etc.
CSE Senior Design I Classic Mistakes Instructor: Mike O’Dell This presentations was derived from the textbook used for this class, McConnell, Steve, Rapid.
CSE Senior Design I Classic Mistakes Instructor: Vassilis Athitsos This presentation was derived from the textbook used for this class, McConnell, Steve,
Learning Objectives Be able to discuss the motivational theories of Taylor, Maslow, McGregor and Herzberg Discuss motivational theorists relevance to.
Leading, Motivating and Controlling
Copyright 2005 Northrop Grumman Corporation Measuring the Benefits of Mature Processes 20th International Forum on COCOMO and Software Cost Modeling 24.
CSE 403 Lecture 8 Risk assessment. Lecture goals Understand risk management and assessment techniques Guarding against failure to meet delivery deadline,
Session 1: Introduction to Project Management
1 Software Project Management Session 1: Introduction, Fundamentals, Classic Mistakes.
Unit 7 University of Sunderland CSEM04 ROSCO Risk & Opportunity Identification: Brainstorming (and Risk Checklists) CSEM04: Risk and Opportunities of Systems.
Unit 4 University of Sunderland COMM80 Risk Assessment of Systems Change Risk Identification: Concept and Generic Techniques COMM80: Risk Assessment of.
Introduction to Project Management II March 10 th, 2015.
Dr. Nguyen Hai Quan.  Overview  Classic Mistakes  Project Manager Requirements  Project Management Phases.
Namaste Staff Motivation Matrika Prasad Rijal Matrika Prasad Rijal Nepal Administrative Staff college.
Rapid Development (Part 1) Mihail V. Mihaylov RammSoft.
Ass. Prof. Dr. Özgür KÖKALAN İstanbul Sabahattin Zaim University.
Chapter 1 Leadership.
Today’s Warm-Up! What are basic skills? Give a few examples. Why are these skills important?
why information systems?
1 CSE 403 Classic Mistakes Reading: Rapid Development Ch3 These lecture slides are copyright (C) Marty Stepp, 2007, with significant content taken from.
Rapid Development.
PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 3rd Edition Copyright © 2009 John Wiley & Sons, Inc. All rights.
Project Management Chapter 3. Objectives Become familiar with estimation. Be able to create a project workplan. Understand why project teams use timeboxing.
Night 1 – Tuesday February 10, 2015 Session I An Overview of Management and Leadership.
Teams – Benefits, Team Formation, and Design features Lecture 1.
Chapter 10 LEADERSHIP. 2 Types of Power 1. Legitimate (authentic right) 2. Reward (control of valuable rewards) 3. Coercive (control over punishments)
1 CSE 403 Introduction Reading: Rapid Development Ch3.3 These lecture slides are copyright (C) Marty Stepp, 2007, with significant content taken from slides.
CSE 403, Spring 2007, Alverson Software Projects – the challenges we face RD:McConnell.
KarcUlrYm nig karpþl;GMNacdl;nieyaCit Employee Involvement and Empowerment emero nTI5.
It’s All About The People
Lecture 1 Introduction, Fundamentals, Classic Mistakes 1.
IT3101- Rapid Application Development. Course Details Lectures – 30 hours Practical - 60 hours.
CSE 490RA Richard Anderson Chris Mason. Course goals For students  Programming experience on Tablet PC  UI and Design experience  Work in team  Develop.
Unit 2 – Chapter 9 (Maslow and Mayo)
Applied Software Project Management Andrew Stellman & Jennifer Greene Applied Software Project Management Applied Software.
Chapter 5 DIRECTING By :Nasser A. Kadasah. Chapter 5 will cover: 5.1 Supervision and Leadership 5.7 Need Theories.
Chapter 2 : Attitude, Motivation, and Integrity. The Importance of Positive and Motivated Attitudes A positive attitude encourages: Higher productivity.
IB Business and Management
Project Management. Projects and Project Managers Project – a [temporary] sequence of unique, complex, and connected activities having one goal or purpose.
IT3101: Rapid Application Development Lec-1. What is Rapid Application Development? Software development process that allows usable systems to be built.
1.01 Understand individual characteristics/traits, interests/preferences, ability levels, skill acquisition, talents/aptitudes, learning styles and values.
1 Software Project Management Introduction, Fundamentals, Classic Mistakes.
Motivation By:- Ranjana Singh. Motivation Motivation:- Motivation refers to the process by which a person’s efforts are energized, directed and sustained.
Introduction to Project management and Principles.
1 Chapter 2 Fundamentals of Motivation. 2 Learning Objectives Describe the two sides of motivation: movement and motive. Identify the five basic needs.
1 Software Project Management Lecture # 3. 2 Today Administrative items Fundamentals Project Management Dimensions Classic Mistakes.
1 Project Management Skills Leadership Communications Problem Solving Negotiating Influencing the Organization Mentoring Process and technical expertise.
HNDIT23073 : Rapid Application Development
9.01 Summarize factors of interpersonal relationships
Software Project Management
Chapter 8 DIRECTING.
CHAPTER 8 MOTIVATION.
Classic Mistakes chapter22
slides created by Marty Stepp
Motivating Employees Chapter 10
Essentials of Management CHAPTER 1
Unit 6 Principles of Management
Instructor: Mike O’Dell
How to fail at delivering software
why information systems?
Chapter 5 DIRECTING By :Nasser A. Kadasah.
Motivating Employees ©William Klinger. This work is licensed under a Creative Commons Attribution 4.0 license  Adapted from Fundamentals of Business  Download.
Instructor: Mike O’Dell
Instructor: Manfred Huber
Presentation transcript:

NJIT 1 Managing Technical People Ian Sommerville, Software Engineering, Chapter 22 Gerald Weinberg, The Psychology of Computer Programming, and many other sources

2 Management Management is planning, organizing, communicating, and controlling Measurement is the key to management-- “You manage what you measure.”

3 Leadership Leadership is the art of making and keeping commitments. Form of a commitment: I commit to a specific person that I will complete a specific act by a specific time.

4 Motivation Motivators Achievement, Power, Recognition, Teamwork, Fulfilling Work Demotivators Money, Benefits, Supervision, Security, Safety, Perks, Titles Motivators bring satisfaction, while demotivators bring dissatisfaction if the underlying needs or expectations are not met. Once that need is met, it no longer motivates. (Once you get a raise, you are no longer satisfied--you want another one.)

5 Maslow’s Hierarchy of Needs Self Actualization Self Esteem Social Safety Physiological

6 Bass and Dunteman Classification of Professional Workers Task Oriented (motivated by the work itself) Self Oriented (motivated by success and recognition) Interaction Oriented (motivated by the presence and actions of team members)

7 Team Building Teams allow for weaknesses in each team member to be compensated by strengths in other members. Diversity in people, roles, skills, interests and personality are important for a team Ideal team size is 3 to 8 persons

8 Selecting Team Members Application Domain Experience Platform Experience Programming Language Experience Educational Background Communication Skills Adaptability Attitude Personality Character

9 Personal Character (McConnell, Chapter 31) Intelligence and Humility Curiosity Intellectual Honesty Communication and Cooperation Creativity and Discipline Laziness (Frederick Taylor’s secret) Good Habits Not important: Hustle, Persistence, Experience, Gonzo Programming

10 Types of Intelligence Verbal/Linguistic (written and spoken language) Logical/Mathematical (scientific thinking) Visual/Spatial (visualize & create mental images) Body/Kinesthetic (physical movement) Musical/Rhythmic Interpersonal (communication and cooperation) Intrapersonal (self reflection)

11 Elias Porter’s Strength Deployment Inventory Task Oriented (Assertive-Directing) Reds People Oriented (Altruistic-Nurturing) Blues Thinkers (Analytic-Autonomizing) Greens Balanced (Flexible-Cohering) Rainbows

NJIT 12 Models of Team Development

13 Team Formation Forming Storming Norming Performing

14 ICA Model (based on Will Schutz) Inclusion recognition belonging participation Affection closeness warmth sensitivity Control influence leading responsibility

15 Kenneth Blanchard’s Situational Leadership S3 Supporting Reluctant Contributor S4 Delegating Peak Performer S2 Coaching Disillusioned Learner S1 Directing Enthusiastic Beginner The Four Leadership Styles SupportingSupporting D i r e c t i v e Low High

NJIT 16 Thirty Five Classic Mistakes in Software Development From Chapter 3 of Rapid Development: Taming Wild Software Schedules, by Steven McConnell

17 The Book

18 People-Related Mistakes Undermined Motivation Weak Personnel Uncontrolled Problem Employees Heroics Adding People to a Late Project Noisy, Crowded Offices Friction between Developers and Customers Unrealistic Expectations Lack of Effective Project Sponsorship Lack of Stakeholder buy-in Lack of User Input Politics placed over Substance Wishful Thinking

19 Process-Related Mistakes Overly Optimistic Schedules Insufficient Risk Management Contractor Failure Insufficient Planning Abandonment of Planning under Pressure Wasted Time during the Fuzzy Front End Shortchanged Upstream Activities Inadequate Design Shortchanged Quality Assurance Insufficient Management Controls Premature or overly Frequent Convergence Omitting Necessary Tasks from Estimates Planning to Catch Up Later Code-like-Hell Programming

20 Product-Related Mistakes Requirements Gold Plating Feature Creep Developer Gold Plating Insufficient Planning Push-me, Pull-me Negotiation Research Oriented Development

21 Technology-Related Mistakes Silver Bullet Syndrome Overestimated Savings from New Tools or Methods Switching Tools in the Middle of a Project Lack of Automated Source Code Control