Transcript TEAM MORALE

SOFTWARE MEASUREMENT & ANALYSIS
DASHBOARD
Team Assignment 14
K15T2-Team 21
Content
1.
2.
Introduction
• Purpose of reporting
To keep team members and professors aware of
the progress and status of projects within an
organization/class
To show individual’s competence in pursuing and
completing a task your Project
To help you assess your work and plan future work
Introduction
• Requirements
Collecting and showing data automatically
Project manager saved projects’ data into a
database that will be used to show the information
that necessary for Dashboard user
Allowing users to choose whatever they want to
see (General / Detail)
Allowing users to drill down to the components that
make up what area requires corrective action
Dashboard Structure
• Measure Project Completion
This part is to measure how many features the
project team has completed, how good those
features are, and how many features are left to
implement.
• Measure the Schedule
This part will show the comparison of schedule
estimates and reality looks like.
• Determine the Rate of Change on your project
Using requirements change chart to know the rate of
change on project.
Dashboard Structure
• Measure Project Cost
Using original budget and actual cost for implementing
the project to compared and give conclusion
• Measure Defect Trends Overtime
Counting the number of remaining open defects so you
can see when the close rate passes the find rate,
enough so that the number of remaining open defects
starts to decrease. Looking for the knee of that
remaining open defects curve, knowing that as the
slope of the remaining number of open defects goes
negative, the risk of release lessens.
SOFTWARE MEASUREMENT & ANALYSIS
THANK YOU
Team Assignment 14
K15T2-Team 21