K15T2-Team 5- PoD Team Software Project Management.

Slides:



Advertisements
Similar presentations
Facilitated by Joanne Fraser RiverSystems
Advertisements

Project Management Process. Managing the Information Systems Project Focus of project management To ensure that information system projects meet customer.
Automated Software Testing: Test Execution and Review Amritha Muralidharan (axm16u)
USC Football Recruiting Database System. Team 6 Client: Jared Blank with USC Football. Revati Kadu Natasha Karnik Akshay ArasMike Nicosia (IV & V) Abhishek.
GAI Proprietary Information
Using UML, Patterns, and Java Object-Oriented Software Engineering Royce’s Methodology Chapter 16, Royce’ Methodology.
Stepan Potiyenko ISS Sr.SW Developer.
Introduction To System Analysis and Design
Software project management Module 1 -Introduction to process management Teaching unit 1 – Introduction Ernesto Damiani Free University of Bozen-Bolzano.
The Soft Topics in Software Engineering Mark Ardis Stephen Chenoweth Frank Young.
5/29/2007SE TSP Launch1 Team Software Project (TSP) May 29, 2007 Launch/Strategy Team Formation.
SwE 313 Introduction to Rational Unified Process (RUP)
Copyright  Larry Dribin, Ph.D. SE470_EngFlows_v1.ppt SE470 EngFlows - 1 Excellence in Software Engineering Repeatable Level Defined Level Manage.
I n t e g r i t y - S e r v i c e - E x c e l l e n c e Business & Enterprise Systems Introduction to Hewlett Packard (HP) Application Lifecycle Management.
By Saurabh Sardesai October 2014.
project management office(PMO)
LOGO TEAM ASSIGNMENT 02 TEAM 7 – K15T02 The Big Goal.
An Overview of Agile L e a d i n g C h a n g e T h r o u g h C o l l a b o r a t i o n.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 17 Slide 1 Extreme Programming.
INFO 637Lecture #31 Software Engineering Process II Launching & Strategy INFO 637 Glenn Booker.
Chapter 3 – Agile Software Development 1Chapter 3 Agile software development.
Test Organization and Management
CSE G674/2009 Project Project Management Section Presented by: Amir Aref Adib.
Page 1 ICT in Time Management Grade 11 ICT Mrs. Ghazaal.
MEASUREMENT PLAN SOFTWARE MEASUREMENT & ANALYSIS Team Assignment 15
Software testing basic. Main contents  Why is testing necessary?  What is testing?  Test Design techniques  Test level  Test type  How to write.
Basic of Project and Project Management Presentation.
Introduction To System Analysis and Design
LOGO “ Add your company slogan ” Software Measurement & Analysis Team Assignment 2.
Common Activities Activities and Tasks in the WBS.
Extreme/Agile Programming Prabhaker Mateti. ACK These slides are collected from many authors along with a few of mine. Many thanks to all these authors.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
INFO 637Lecture #21 Software Engineering Process II TSP Roles and Overview INFO 637 Glenn Booker.
1 Software Process Models-ii Presented By; Mehwish Shafiq.
Software Project Management
Roles in a Project Team By Sebastian Wagner And Michal Pieniazek.
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
LOGO Team Assignment 1 Software Architectures. LOGO K15T2- Group21 Contents Introduce to Sale system 1 Architecture Drivers 2 Minimal Acceptable Delivery.
XP Explained Chapters 7-9. Primary Practices  Sit together Ideal Resistance Multi-site  Whole Team All the necessary skills in a single management structure.
1 김 수 동 Dept. of Computer Science Soongsil University Tel Fax
COMP3615,5615 Capstone Projects Week Overview of the semester Website tour – XP and roles – Assessment – note especially the individual mark operating.
Pair Development Framework Monvorath (Molly) Phongpaibul.
The Role of Teams in Engineering By: Ethan O’Brien(presenting), Chloe Ward, Robert English, John McDermott and Graham Britchfield.
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
The Ferl Practitioners’ Programme Transforming Teaching and Learning with ILT O4.3 ILT Implementation.
Planning Extreme programming
Team-Based Development ISYS321 Managing the Information Systems Project.
1 Project Management Software management is distinct and often more difficult from other engineering managements mainly because: – Software product is.
TMP3413 Software Engineering Lab Lab 01: TSPi Tool Support.
P3 Business Analysis. 2 Section F: Project Management F1.The nature of projects F2. Building the Business Case F4. Planning,monitoring and controlling.
CSC 480 Software Engineering Team Issues. Essence of a Successful Team To be successful, teams must  Plan their projects  Track their progress  Coordinate.
1 Advanced Computer Programming Project Management: Basics Copyright © Texas Education Agency, 2013.
P ERSONAL & TEAM PROCESS MODELS Lecture 05 Part -2.
Applied Software Project Management SOFTWARE TESTING Applied Software Project Management 1.
AGILE METHODS Curtis Cook CS 569 Spring 2003.
Process 4 Hours.
Online Event Organizing Company Managemant System
Applied Software Testing
Project Management PTM721S
Fundamentals of Information Systems, Sixth Edition
BA Continuum India Pvt Ltd
CSC 480 Software Engineering
Where Agile Business Meets Agile Development
1.Introduction to Rational Unified Process (RUP)
Project Management.
Lecture # 3 Software Development Project Management
Roles and Responsibilities of a Project Manager
Extreme Programming.
Asset Manager Job summary: Essential functions of the job:
Presentation transcript:

K15T2-Team 5- PoD Team Software Project Management

1 2 3 Project goals Roles & Responsibilities Work Breakdown Structure Content

 Produce a quality product  Run a productive and well managed project with XP methodology  Finish on time

 Opportunities to learn more information about SMS system  Product made to serve our study and can become the commercial product in the future.  This is essential thing to complete this course  To collect preliminary knowledge of programming about sending SMS automatically via AT command sets.

Vision Goals of Team

 How to manage project activities that following XP methodology  How to make a plan or iteration plan following XP methodology  Understanding clearly XP methodology  Learn and grow together as a team, thriving on each other’s strengths, helping overcome each other’ shortcomings, and come out as better individuals, team players and software engineers.

 Learn how to work smart and not hard – exhibiting self control under pressure, and managing time better to deal with multiple tasks efficiently  Team’s artifacts should be used as a precedent for excellence next semesters

 Be a cooperative and effective team member  Plan and track all your personal work  The team members know each other better  The team members can support each other, share work during the project implementation  Create relationships with the outside teams to support own team solve the problems.

1 2 3 Project goals Roles & Responsibilities Work Breakdown Structure Content

Manager/ Tracker An Ha Coach &Tester Tho Nguyen Programmer in pair Tuan Lai Phu Nguyen Programmer in pair Hoang Tran Quyen Thoi

 Monitor progress of the team and notify the team of problems with the progress and of delayed tasks.  Make sure plan is being followed.  Improve planning process.  Maintain the plan.  Make sure that time data is being recorded in the plan.

 Tracks the risks  Makes sure that mitigation strategies are planned in the cycle.  Ensure that the process is being followed and record deviations from it.  Maintain the process documents.  Tracks the risks  Makes sure that mitigation strategies are planned in the cycle.  Ensure that the process is being followed and record deviations from it.

 Collect, maintain, and analyze planning metrics

 Lead all development work.  Track defects.  Alert the team to quality problems in the product.  Keep the architecture and detailed design up to date.  Ensure architectural drivers are met.  Maintain the Test Specification.  Make decisions about changes in the architecture.

 Coordinate test planning, documentation of the test plan, and test execution

 Estimate tasks.  Write code and tests.  Gradually improve the design.  Be an advocate for reuse.  Follow disciplined personal practices

1 2 3 Project goals Roles & Responsibilities Work Breakdown Structure Content

THANKS FOR YOUR LISTENING!