It’s All About The People

Slides:



Advertisements
Similar presentations
NML/436/L1-1 Nazareth Northwestern Mutual Life Participants in IS Development l A team of people comprising: l Project Manager l Systems Analysts l Specialists.
Advertisements

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.
CS5714 Usability Engineering An Iterative, Evaluation- Centered Life Cycle For Interaction Development Copyright © 2003 H. Rex Hartson and Deborah Hix.
CSCU 411 Software Engineering Chapter 2 Introduction to Software Engineering Management.
Stepan Potiyenko ISS Sr.SW Developer.
About Us Founded in 2000 Partnered with the Specialist Schools and Academies Trust Microsoft Gold Partner Microsoft Education Specialist.
IS Careers, Jobs and Organizational Roles. Contemplative Questions  Would I enjoy a career in IS?  What type of positions are available in IT?  In.
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
1 IS112 – Chapter 1 Notes Computer Organization and Programming Professor Catherine Dwyer Fall 2005.
Roles of IT Personnel Unit Customer Service This is a facility that helps customers with wide-ranging questions relating to a specific company,
Planning. SDLC Planning Analysis Design Implementation.
SOFTWARE QUALITY ASSURANCE Asst. Prof. Dr. Selim BAYRAKLI Maltepe University Faculty of Engineering SE 410.
Dr. Nguyen Hai Quan.  Overview  Classic Mistakes  Project Manager Requirements  Project Management Phases.
Rapid Development (Part 1) Mihail V. Mihaylov RammSoft.
Before we start construction, let’s lay the groundwork.
BIS310: Structured Analysis and Design Introduction and Systems Planning Week 1.
What is the Information technology career cluster?
Four P’s People – software engineers People – software engineers Product – software to be produced Product – software to be produced Process – framework.
Careers Matthew Ganey, Indiana University General Mills Company of Champions.
Twelfth Lecture Hour 10:30 – 11:20 am, Saturday, September 15 Software Management Disciplines Project Organization and Responsibilities (from Part III,
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design.
Chapter 1: Introduction to Systems Analysis and Design
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
2 Systems Architecture, Fifth Edition Chapter Goals Describe the activities of information systems professionals Describe the technical knowledge of computer.
CEN th Lecture CEN 4021 Software Engineering II Instructor: Masoud Sadjadi Software Project.
SCSC 311 Information Systems: hardware and software.
TEAMWORK WORKSHOP ICOM5047 Design Project in Computer Engineering J. Fernando Vega-Riveros, Ph.D. Associate Professor – ECE Dpt.
Systems Design Approaches The Waterfall vs. Iterative Methodologies.
Chapter 3 Project Management Concepts
Strong9 Consulting Services, LLC 1 PMI - SVC I-80 Breakfast Roundtable Monthly Meeting Thursday, October 12, :00 am – 9:00 am.
CSE 403, Spring 2007, Alverson Software Projects – the challenges we face RD:McConnell.
Copyright 2002 Prentice-Hall, Inc. 1.1 Modern Systems Analysis and Design Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 1 The Systems Development.
Slide 1 Project Management Chapter 4. Slide 2 Objectives ■ Become familiar with estimation. ■ Be able to create a project workplan. ■ Become familiar.
The Software Development Life Cycle: An Overview Presented by Maxwell Drew and Dan Kaiser Southwest State University Computer Science Program.
Large Software Projects Deborah Black Vice President, Windows Division Microsoft.
The Enterprise Project Management (EPM) Professional March 28th, 2007 Brendan Giles, BSc., PMP, MOS, MCP (EPM) The Key to Successful Adoption of Enterprise.
 Management ◦ The activities and tasks undertaken by one or more persons for the purpose of planning and controlling the activities of other in order.
Software Project Management Lecture # 2. Outline The 4 Ps in Project Management Detailed Insight of each P.
Training and Developing a Competitive Workforce 17/04/2013.
Lecture 1 Introduction, Fundamentals, Classic Mistakes 1.
Building Operational Effectiveness Presented by Sharon McCollick.
Definitions of GIS Works with geographic information Performs data input, management, manipulation/analysis, and output functions Composed of hardware,
Unit 2 ICT Job Role. ICT manager An ICT Manager has to plan, organise, control and coordinate with everyone, and they would help to design ICT- related.
IT3101: Rapid Application Development Lec-1. What is Rapid Application Development? Software development process that allows usable systems to be built.
Chapter 9 The People in Information Systems. Learning Objectives Upon successful completion of this chapter, you will be able to: Describe each of the.
Project Management Why do projects fail? Technical Reasons
Software Project Management
1 CP586 © Peter Lo 2003 Multimedia Communication Multimedia Development Team.
Introduction to Project management and Principles.
Organizational Communications and Its Importance to Company Growth. Presented by: Kenneth Martinez Organizational Communications Manager.
Computer Technology: Your Need to Know Chapter 1 Slide 1.
The Project Team. Major Ideas Software Projects are Cultural Events Management ≠ Leadership Team’s ability is based more on its personality than its skill.
1 Project Management Skills Leadership Communications Problem Solving Negotiating Influencing the Organization Mentoring Process and technical expertise.
Software Engineering “Practical Approach”
Chapter 1 Computer Technology: Your Need to Know
ORGANIZATIONAL CULTURE
Information Systems Development
Chapter 1: Introduction to Systems Analysis and Design
Chapter 1 The Systems Development Environment
MBI 630: Systems Analysis and Design
Rest of Project Management
why information systems?
Chapter 1: Introduction to Systems Analysis and Design
Software Project Management
Empyrean Consulting, Inc.
Chapter 1: Introduction to Systems Analysis and Design
Presented By:- Abhinav Shashtri Mastering Dot Net Training And Certification Course.
Presentation transcript:

It’s All About The People Software Development It’s All About The People

Introduction Project Management Project Team Life Cycle Personalities Classic Mistakes

Four P’s of Project Management People Recruitment, training, organization, team development Product Define project scope and design of product Process Establish framework for software development Project Understand complexities of project development

Project Team Life Cycle Team Formation Team Development Team Maintenance

Team Composition Technology Specialists Application Subject Area Experts Customer Support Experts Project Management Specialists

Team Formation Technical Skills Soft Skills Database design Detail design & debugging Network design Application architecture Requirements specification Test script writing Configuration setup Tools setup/support Customer problem analysis Soft Skills Personal ambition Level of commitment Interpersonal communication skills Strong biases Experience Attention to detail Sense of urgency Flexibility/Maturity

Team Development Ample communication Treat each other with respect Clear understanding of each person’s assignment and role Not hiding a chronic laggard Understand and support team goals Follow agreed-upon process

Team Maintenance Reward Punishment Attrition Growth

Personalities Intuitive vs. Sensing Feeling vs. Thinking Extrovert vs. Introvert

The Best Fit For The Job Team Leader Systems Analyst Programmer Intuitive and Feeling Systems Analyst Thinking Programmer Extrovert

Personalities (cont) Delivers vs. Prototypers vs. Perfectors Converges vs. Divergers Producers vs. Fixers Finishers vs. Non-finishers

Classic “People” Mistakes Undermined Motivation Weak Personnel Uncontrolled Problem Employees Heroics Adding People Late to a Project Noisy, Crowed Work Spaces Unrealistic Expectations Lack of User Input Wishful Thinking

Future “People” Issues Different Languages Different Cultures Different Time Zones Different Continents

References 1. Gorla, Narasimhaiah and Yan Wah Lam, “Who Should Work With Whom?”, Communications of the ACM, vol.47 no. 6, June 2004, pp79-82. 2. Howard, Alan, “Software Engineering Project Management”, Communications of the ACM, vol. 44 no. 5, May 2001, pp 23-24. 3. McConnell, Steve, Software Project Survival Guide, MicroSoft Press, 1996. 4. Pressman, Roger, Software Engineering: A Practitioners Approach, McGraw Hill Companies, 2005. 5. Tsui, Frank, Managing Software Projects, Southern Polytechnic State University, Jones and Bartlett Publishers, 2004.