Project Tracking. Questions... Why should we track a project that is underway? What aspects of a project need tracking?

Slides:



Advertisements
Similar presentations
Process and Product Quality Assurance (PPQA)
Advertisements

Configuration Management
1 Dr. Ashraf El-Farghly SECC. 2 Level 3 focus on the organization - Best practices are gathered across the organization. - Processes are tailored depending.
Software Quality Assurance Plan
OPSM 639, C. Akkan Monitoring Progress How does a project get one year late? … One day at a time –Frederick P. Brooks MBWA: Management by Walking Around.
Software Engineering CSE470: Process 15 Software Engineering Phases Definition: What? Development: How? Maintenance: Managing change Umbrella Activities:
1 SW Project Management (Planning & Tracking) Dr. Atef Z Ghalwash Faculty of Computers & Information Helwan University.
Chapter 7: Key Process Areas for Level 2: Repeatable - Arvind Kabir Yateesh.
More CMM Part Two : Details.
Overview Lesson 10,11 - Software Quality Assurance
Software Configuration Management
CS 501: Software Engineering Fall 2000 Lecture 4 Management I: Project Management.
Lecture 2b: Software Project Management CSCI102 - Introduction to Information Technology B ITCS905 - Fundamentals of Information Technology.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Fundamentals of Information Systems, Second Edition
1 Chapter 6 Risk Management. 2 Project Risks What can go wrong? What is the likelihood? What will the damage be? What can we do about it?
SE is not like other projects. l The project is intangible. l There is no standardized solution process. l New projects may have little or no relationship.
Software Process CS 414 – Software Engineering I Donald J. Bagert Rose-Hulman Institute of Technology December 17, 2002.
ANSI/EIA -748 EVMS 32 Guidelines National Aeronautics and Space Administration.
Software Verification and Validation (V&V) By Roger U. Fujii Presented by Donovan Faustino.
Configuration Management Avoiding Costly Confusion mostly stolen from Chapter 27 of Pressman.
Capability Maturity Model
© 1999 Prentice-Hall, Inc. Chap Level 3: Key Processes Defined Group 9: LaTanya Moore Ali Imajat Asim Eldaroty.
S/W Project Management
The Key Process Areas for Level 2: Repeatable Ralph Covington David Wang.
Team Launch Introduction. Real projects are large and complex, and most software is created by teams Merely throwing people together does not result in.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Managing Software Quality
Capability Maturity Model Part One - Overview. History Effort started by SEI and MITRE Corporation  assess capability of DoD contractors First.
Chapter 2 The process Process, Methods, and Tools
Dillon: CSE470: SE, Process1 Software Engineering Phases l Definition: What? l Development: How? l Maintenance: Managing change l Umbrella Activities:
N By: Md Rezaul Huda Reza n
S oftware Q uality A ssurance Part One Reviews and Inspections.
Software Quality Assurance Activities
Michael Dermody September 2010  Capability Maturity Model Integration ◦ Is a Trademark owned by the Software Engineering Institute (SEI) of Carnegie.
CMM Level 2 KPA’s CS 4320 Fall Requirements Management 1 Goals: – System requirements allocated to software are controlled using a baseline for.
Soft Tech Development Inc. 1 Software Project Tracking A CMM Level 2 Key Process Area Soft Tech Development Inc.
S Q A.
Prof. Roy Levow Session 8.  Steps in Closing a Project  Getting Client Acceptance  Installing Project Deliverables  Documenting the Project  Post-Implementation.
Software Development Process and Management (or how to be officious and unpopular)
Certification and Accreditation CS Phase-1: Definition Atif Sultanuddin Raja Chawat Raja Chawat.
CMM Level 2: Repeatable Copyright, 2000 © Jerzy R. Nawrocki Quality Management.
Project monitoring and Control
Project Tracking and Monitoring QMS Training. 2 Objective To track and monitor the progress of the project and take appropriate corrective actions to.
Georgia Institute of Technology CS 4320 Fall 2003.
©Ian Sommerville 2000 Slide 1 Project management l Organising, planning and scheduling software projects l Objectives To introduce software project management.
AP-1 5. Project Management. AP-2 Software Failure Software fails at a significant rate What is failure? Not delivering it on time is an estimation failure.
CS 501: Software Engineering Fall 1999 Lecture 6 Management I: Project Management.
Software Engineering - I
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Project Management All projects need to be “managed” –Cost (people-effort, tools, education, etc.) –schedule –deliverables and “associated” characteristics.
Fundamentals of Information Systems, Second Edition 1 Systems Development.
CSCI 521 Final Exam Review. Why Establish a Standard Process? It is nearly impossible to have a high quality product without a high quality process. Standard.
Project management Topic 7 Controls. What is a control? Decision making activities – Planning – Monitor progress – Compare achievement with plan – Detect.
Chap 4. Project Management - Organising, planning and scheduling
MGT 461 Lecture #27 Project Execution and Control Ghazala Amin.
SE513 Software Quality Assurance Lecture10: Documentation and Quality Records Control Galin, SQA from Theory to Education Limited.
SEN 460 Software Quality Assurance. Bahria University Karachi Campus Waseem Akhtar Mufti B.E(C.S.E) UIT, M.S(S.E) AAU Denmark Assistant Professor Department.
Project Planning Goal 1 - Estimates are documented for use in tracking and planning project. Goal 2 - Project Activities and commitments planned and documented.
Pertemuan 14 Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
Capability Maturity Model. CS460 - Senior Design Project I (AY2004)2 Immature Organisations Software processes are often rigorously followed. Organisation.
6/6/ SOFTWARE LIFE CYCLE OVERVIEW Professor Ron Kenett Tel Aviv University School of Engineering.
Cmpe 589 Spring Fundamental Process and Process Management Concepts Process –the people, methods, and tools used to produce software products. –Improving.
MGT 437 OUTLET Become Exceptional/mgt437outlet.com FOR MORE CLASSES VISIT
ANSI/EIA-748-B Earned Value Management Systems (EVMS)
Software Project Configuration Management
CS4311 Spring 2011 Process Improvement Dr
CMMI – Staged Representation
Maintenance.
QA Reviews Lecture # 6.
Presentation transcript:

Project Tracking

Questions... Why should we track a project that is underway? What aspects of a project need tracking?

Reasons for Late Projects 1. overly optimistic scheduling bad estimations during proposal or planning 2. tardy identification of schedule and budget problems noticing too late that we are late 3. tardy reactions to important events bad risk management Software Quality Assurance by Galin page 401

Solution to previously listed problems 1. better estimation 2. better project tracking 3. better project tracking

Objectives of Project Tracking Short Term:  early detection of irregular events Long Term:  creation of preventive actions  improvement of estimation accuracy modified from Galin page 402

What do we need to track? Project Schedule are we hitting the milestones on time what about the "critical path" milestones Risks what might happen how likely is the problem what can/should we do Resources  Humans  Budget Galin section 20.1

How do we track projects? Use tools!!! a tool can track the critical path a tool can track the budget a tool can alert you to potential resource conflicts Status Reports both formal and informal

Key Aspects of Continuous Risk Management Identify – Continually asking, “what could go wrong?” Analyze – Continually asking, “which risks are most critical to mitigate?” Plan – Developing mitigation approaches for the most critical risks Track – Tracking the mitigation plan and the risk Control – Making decisions based on data Communicate – Ensuring a free-flow of information throughout the project Carnegie Mellon SEI

Example 1 You notice that design, implementation, and testing of the database component is running about a week behind. Instead of one week for each of the three tasks, the database tasks will take a total of four weeks. However, the database can be a week late because it is not on critical path. Any potential problems?

Example 2 Task: Testing the Database Estimated Duration: 3 days Required Resources: the database requirements specs the implementation (source code) real data from customer test person that has a DB Test certificate Any Special Scheduling / Tracking Issues?

Example 3 Initial Unit Testing reports indicate a bug rate of 4.5 / KSLOC. Should you be concerned? Further checking finds  Average initial bug rate is 3.1 per KSLOC  StdDev of 0.5  weighted rate is also higher than average What actions should be taken?

Example 4 Well into development, you get an indicating changes in the interface requirements are necessary based on a demo of the prototype done for the customer. The changes will require a good amount of recoding. Any SQA tasks necessary?

And of course, Follow Up Audit the Tracking Procedures are we really seeing what is going on? are the progress reports reporting the important info? are we tracking what needs to be tracked? are we talking to the right people?

CMM on Project Tracking "The purpose of Software Project Tracking and Oversight is to provide adequate visibility into actual progress so that management can take effective actions when the software project's performance deviates significantly from the software plans." Goals 1.Actual results and performances are tracked against the software plans. 2.Corrective actions are taken and managed to closure when actual results and performance deviate significantly from the software plans. 3.Changes to software commitments are agreed to by the affected groups and individuals. adapted from

CMM on Project Tracking Ability to Perform 1.A software development plan for the software project is documented and approved. 2.The project software manager explicitly assigns responsibility for software work products and activities. 3.Adequate funding and resources are provided for tracking the software project. 4.The software managers are trained in managing the technical and personnel aspects of the software project. 5.First-line software managers receive orientation in the technical aspects of the software project.

CMM on Project Tracking Activities performed 1. A documented software development plan is used for tracking the software activities and communicating status. 2. The project's software development plan is revised according to a documented procedure. 3. Software project commitments and changes to commitments made to individuals and groups external to the organization are reviewed with senior management according to a documented procedure. 4. Approved changes to commitments that affect the software project are communicated to the members of the software engineering group and other software-related groups. 5. The size of the software work products (or size of the changes to the software work products) are tracked, and corrective actions are taken as necessary. 6. The project's software effort and costs are tracked, and corrective actions are taken as necessary. 7. The project's critical computer resources are tracked, and corrective actions are taken as necessary. 8. The project's software schedule is tracked, and corrective actions are taken as necessary. 9. Software engineering technical activities are tracked, and corrective actions are taken as necessary. 10. The software risks associated with cost, resource, schedule, and technical aspects of the project are tracked. 11. Actual measurement data and replanning data for the software project are recorded. 12. The software engineering group conducts periodic internal reviews to track technical progress, plans, performance, and issues against the software development plan. 13. Formal reviews to address the accomplishments and results of the software project are conducted at selected project milestones according to a documented procedure.

Maintenance

Types of Maintenance Corrective bug fixes, security fixes, etc Adaptive new hardware, new OS, … Perfective adding new functions Preventative Y2K

Where the money goes Software Quality Assurance by Galin, page % 12% 15% 33% Rest of Project Corrective Adaptive Functional

The big questions… Why does so much money go into maintenance? How do we reduce the maintenance costs?

Does software wear out? errors per KSLOC Time Expected Actual - due to Maintenance Effective

Essential SQA Maintenance Tasks Maintain Accurate Design Document Quality Source Code is Cheaper to Maintain set and maintain coding standards  conduct peer code reviews set testing guidelines via a Maintenance Test Plan Track Maintenance Metrics mean time to correct errors mean time to add new function … Determine Root Cause of Errors Determine Root Cause of Errors

Up Next in the Course You You