CSC 480 Software Engineering Team Issues. Essence of a Successful Team To be successful, teams must  Plan their projects  Track their progress  Coordinate.

Slides:



Advertisements
Similar presentations
Module N° 4 – ICAO SSP framework
Advertisements

Facilitated by Joanne Fraser RiverSystems
Program Management Office (PMO) Design
Leadership ®. T EAM STEPPS 05.2 Mod Page 2 Leadership ® 2 Objectives Describe different types of team leaders Describe roles and responsibilities.
Culture and Leadership
More CMM Part Two : Details.
Program Management Overview (An Introduction)
Lecture 2b: Software Project Management CSCI102 - Introduction to Information Technology B ITCS905 - Fundamentals of Information Technology.
Aplicaciones de Ingeniería de Software
Project Work and Administration
Chapter 3: The Project Management Process Groups
8/7/2007SE _8_07_Misc_PostMortem.ppt1 Additional Topics & Team Project Post-Mortem.
DEFINITIONS OF MANAGEMENT, ADMINISTRATION, LEADERSHIP, AND DISCUSSION SOWO 874 FALL 2012.
Project Management “Introduction to Project Management: Tools, Techniques, and Practices” BA 320 Operations Management.
Fundamental of Software Project Management Team Assignment 1 – K15T2 – Team 07.
Planning. SDLC Planning Analysis Design Implementation.
LOGO TEAM ASSIGNMENT 02 TEAM 7 – K15T02 The Big Goal.
1311A.1 Club Leadership Training Session Achieving Success As President.
Release & Deployment ITIL Version 3
Monica Hutchins LDR-601 Dr. M. Parsons “Teams are organizational groups composed of members who are interdependent, who share common goals, and who.
CMM Level 3 KPA’s CS4320 Fall Organizational Process Focus (Goals) Software process development and improvement activities are coordinated across.
INFO 637Lecture #31 Software Engineering Process II Launching & Strategy INFO 637 Glenn Booker.
Copyright Course Technology 1999
CS 350, slide set 6 M. Overstreet Old Dominion University Fall 2005.
Test Organization and Management
Competency Area A: Communicating with Paraprofessionals.
Teamwork and roles in student Scrums. Most software is designed by teams …but merely throwing people together does not result in a functioning team To.
Quality Management.  Quality management is becoming increasingly important to the leadership and management of all organisations. I  t is necessary.
Preparing for the Launch Mohammed El- Affendi. Launch Major Tasks  The Launch is performed according to script “LAU1”, table 3.1 in the book (page 39),
Service Transition & Planning Service Validation & Testing
INFO 637Lecture #21 Software Engineering Process II TSP Roles and Overview INFO 637 Glenn Booker.
1 Project Management Introduction. 2 Chap 1 What is the impact? 1994: 16% of IT projects completed “On-Time” 2004 : 29% of IT projects “On- Time” 53%
1 © The Delos Partnership 2004 Project Management Organisation and Structure.
Improving engineering productivity APEGGA. Improving Productivity Mega Projects  History  What is needed  How will it be done  Division of Labour.
TEAMWORK.
Team Work What is a team? Building Effective Teams Managing yourself Team obligations Common Team problems Risk Management Meeting techniques cs3141, Fall.
Project monitoring and Control
Communications Skills (ELE 205)
Managing Teams  Goal: Have all projects succeed  Why projects fail Teamwork problems, not technical problems Common problems  Ineffective leadership.
Personal leadership qualities
Georgia Institute of Technology CS 4320 Fall 2003.
INFO 637Lecture #101 Software Engineering Process II Review INFO 637 Glenn Booker.
Team Software Process (TSPi) CS4320 Fall TSP Strategy Provide a simple process framework based on the PSP. Use modest, well-defined problems. Develop.
 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 Product Line Material based on slides and chapter by Linda M. Northrop, SEI.
Where We Are Now 14–2. Where We Are Now 14–2 Major Tasks of Project Closure Evaluate if the project delivered the expected benefits to all stakeholders.
Communications Skills (ELE 205) Dr. Ahmad Dagamseh Dr. Ahmad Dagamseh.
2.4 Key Management Roles KEY CONCEPT
Sponsored by the U.S. Department of Defense © 2002 by Carnegie Mellon University July 2002 PSP-TSPi Faculty Workshop Pittsburgh, PA Lecture.
Team Assessment In software development, teams are how we accomplish more and better than what can be accomplished by an individual.
THE POSTMORTEM Chapter 10 Introduction to Team Software Process.
PRJ566 Project Planning and Management Teamwork 1.
INFO 637Lecture #11 Software Engineering Process II PSP Overview & TSP Introduction INFO 637 Glenn Booker.
Team X Review. The members of Team X propose to develop a therapeutic activity system using a Microsoft Surface unit and a Windows 7 desktop. By working.
Using the TSPi Chapter Using the TSPi Chapter 16 Managing yourself Chapter 17 Being on A Team Chapter 18 Teamwork Postmortem.
MGT 461 Lecture #27 Project Execution and Control Ghazala Amin.
Project Management Why do projects fail? Technical Reasons
Lecture 8 TQM 311 lecturer: Noura Al-Afeef Medical Record Department 1.
R. I. T Multidisciplinary Senior Design #1 rule of classroom science: Don’t eat the experiment!
Capability Maturity Model. CS460 - Senior Design Project I (AY2004)2 Immature Organisations Software processes are often rigorously followed. Organisation.
The Project Management Process Groups
MIS Project Management Instructor: Sihem Smida Project Man agent 3Future Managers1.
CSC 480 Software Engineering
Software Subcontractor
Critical Element: PBIS Team
CSC 492 – Senior Design – Spring 2019
Teaming Class 2 Notes – Section 1
Teaming Class 2 Notes – Sections 2 & 3
Team Software Process (TSP)
Presentation transcript:

CSC 480 Software Engineering Team Issues

Essence of a Successful Team To be successful, teams must  Plan their projects  Track their progress  Coordinate their work  Agree on goals  Have a common process  Communicate freely and often

Why Projects Fail Projects usually fail because of team problems, not technical ones. Some team members have difficulty with the pressure that is caused by a tight schedule. Without a plan and a schedule team members do not know the status of their projects and can not see problems with project progress.

Team Problems  poor communications  inability to compromise or cooperate  weak participation  procrastination  lack of discipline  lack of confidence  ineffective leadership  poor planning  function (or requirement) creep  lack of emphasis on product quality  unclear team roles and responsibilities

A Jelled Team Development teams need to “jell.” A jelled team  works smoothly and efficiently  is tightly knit into a single unit  is greater than the sum of its parts  is fun to work with formstormnormperform

Team Building Principles A team consists of  at least two people,  who are working towards a common goal/ objective/mission,  where each person has been assigned specific roles or functions to perform,  and where completion of the mission requires some form of dependency among the group members.

Conditions for Effective Teams The tasks to be done are clear and distinct. The team is clearly identified. Each member has a clearly defined role. The team has control over their tasks. The team has challenging, specific, and measurable goals. The team is aware of its performance and progress toward their goals. The team has a common framework for their work.

Team Roles Team member responsibility is defined by five team roles  Team Leader  Development Manager  Planning Manager  Quality/Process Manager  Support Manager

Maintaining Communication Internal communication  Teams meet weekly.  Roles, processes, plans, and measurements allow discussion to be focused upon the issues.  A meeting script ensures that all necessary topics are discussed every week.

Maintaining Communication External communication  The team leader makes weekly reports to the instructor.  The instructor can provide guidance when it appears to be needed.

Team Leader Leads the team and ensures that engineers report their process data and complete their work as planned.  Motivate the team to perform their tasks and resolve issues.  Facilitate Team Meetings.  Report to the instructor on project status.  Lead the team in allocating tasks among the team members.  Maintain the project notebook.  Lead the team in developing the Cycle Report.  Also, act as a development engineer.

Development Manager Leads and guides the team in designing and developing the product.  Lead the team in producing the development strategy and the product conceptual design.  Lead the development of the requirements specification (SRS).  Lead the team in producing the design specification (SDS).  Lead the team in implementing the product.  Lead development of the build, integration and system test plans.  Also, act as a development engineer.

Planning Manager Supports and guides the team in planning and tracking their work.  Lead the team in producing the task plan and schedule for each development cycle.  Lead the team in producing the balanced team development plan.  Track the team's progress against their plan.  Also, act as a development engineer.

Quality / Process Manager Supports the team in defining their process needs, in making the quality plan, and in tracking process and product quality.  Lead the team in producing and tracking their quality plan.  Identify where quality performance falls short of objectives.  Lead the team in defining, documenting, and maintaining their processes and development standards.  Act as moderator and lead all team reviews and inspections.  Also, act as a development engineer.

Support Manager Supports the team in determining, obtaining, and managing the tools needed to meet its technology and administrative support needs.  Lead the team in determining their support needs and obtaining the needed tools and facilities.  Lead the development and management of Change/Configuration Management System.  Handle the team's issue and risk tracking system.  Act as the team's reuse advocate.  Also, act as a development engineer.