SlideServe
Télécharger Obtenir Pro
Menu
Accueil Pro
Préférences
ApparenceLight Aide et commentaires
© SlideServe · v2026

Effective Team Management in OO Software Development

francesbrown avatar
francesbrown
5 diapositives · 81 Views · Jan 05, 2020

This project involves a team-based approach to develop an OO software application. It emphasizes non-trivial, interesting, and useful requirements within reasonable scope. The project structure follows a formally defined OO development process, with team-oriented responsibilities and weekly status reports. Key artifacts include a Project Development Plan, Software Design Specification in UML, Source Code (C++), Test Plans, and a User Guide. The roles of Team Lead and Software Engineer are outlined, with a focus on communication, work assignments, monitoring progress, and adherence to standards. Weekly status reports and activity data spreadsheets are essential for project management.

#effective team management in oo software development #effective team management in oo software development ppt #powerpoint #presentation
Effective Team Management in OO Software Development - slide 1
01 / 5Effective Team Management in OO Software Development
1 / 17

Télécharger la présentation

Effective Team Management in OO Software Development
Une image / un lien ci-dessous est fourni (tel quel) pour télécharger la présentation

Politique de téléchargement : le contenu du site vous est fourni TEL QUEL pour votre information et votre usage personnel ; il ne peut être vendu, concédé sous licence ni partagé sur d’autres sites sans l’accord de son auteur.Le contenu vous est fourni TEL QUEL, pour votre information et votre usage personnel uniquement. Téléchargez la présentation en cliquant sur ce lien. Lors du téléchargement, si vous ne parvenez pas à télécharger une présentation, l’éditeur a peut-être supprimé le fichier de son serveur.Pendant le téléchargement, si vous ne parvenez pas à obtenir une présentation, le fichier a peut-être été supprimé par l’éditeur.

F I N

Plus de contenu associé

Transcription de la présentation

  1. Team ProjectResponsibilities COP4331 and EEL4884 Processes for OO Software Development Dr. David A. Workman School of EE and Computer Science January 11, 2005 Revised: October 22, 2008

  2. Project Overview • Requirements • Non-trivial (more than what one person could accomplish) • Interesting ( stimulates creativity and learning ) • Useful (has application outside academic context ) • Manageable (suitable for team development) • Reasonable scope (can be completed within the time frame of one semester) • Structure • Follow a formally defined OO development process • Team-oriented (1 team lead, 3 software engineers )(2 software engineers) • Weekly status reports (capture process data, report progress ) • Informal design reviews (Team and Customer) • Artifacts • Project Development Plan • Software Design Specification (in UML) • Source Code (C++) • Test Plans and Procedures, Data, and Results • User Guide • Working System (c) Dr. David A. Workman

  3. Project Manager = Customer Team Lead Team Lead Team Lead Team Lead Team Lead Team Members Team Members Team Members Team Members Team Members Team Members Team Members Team Members Team Members Team Members Team Members Team Members Team Members Team Members Team Members Team Members Team Members Team Members Team Members Team Members Project Organization InstructorPlays roles of: Project Manager and Customer • Team Lead: • represents team to project manager and customer • schedules, sets agenda, and manages team mtngs • makes work assignments • coordinates work activities among team members • compiles status reports • reports team status to project manager • oversees assembly and delivery of work products • Team Members: • prepares and submits weekly status reports to team lead • performs assigned work activities • keeps team lead well-informed of progress and technical issues (c) Dr. David A. Workman

  4. Team Roles & Responsibilities • Team Lead • Point of Contact for project management • Schedules and coordinates team meetings (at least one per week) • Facilitates team communication • Assigns work packages and responsibilities • Acts as team configuration manager, or delegates that responsibility • Collects and summarizes weekly status reports (emails status to PM) • Responsible for monitoring team activities to ensure project schedule is met. • Reviews work products and enforces standards and conventions for those products. • Represents team in formal reviews with project management and/or customer. • Software Engineer • Performs assigned work packages maintaining schedule and quality standards • Prepares weekly status report and submits to Team Lead • Keeps Lead informed of progress, problems, and accessibility (c) Dr. David A. Workman

  5. Administration & Reporting • Weekly Status Report • Activity Data Spreadsheet (c) Dr. David A. Workman