Why is the option to Break out project effort by Skills Allocation turned off by default in new workbooks and templates?


Though we provide "starter" skills allocation for both new workbooks and QSM templates, the skills breakout is turned off by default because the skill categories, labor rates, and skills allocation data are most meaningful when they are configured to match the roles and practices actually in use on your projects. We recommend you create a template or two that represents a typical project resource requirement schema for your organization, then tailor it for individual projects as necessary.  


Taxonomy upgrade extras 

Setting Phase Start Dates


How do I set Phase Start dates?

To set Phase Start dates, simply click Estimate | Solution Assumptions, then select the Phase Tuning tab.  Please note that you cannot select the start date for the first phase included in the project - it will always begin on the project start date specified in the Solution Assumptions or Wizards.

Subsequent phases can be set to begin at:


Taxonomy upgrade extras 
SLIM-Estimate How To

Base Size Unit vs. Function Unit


What is the difference between the Base Size Unit and the Function Unit?

The Function Unit is the overall size measure for the project.  It makes sense to describe a book as a collection of chapters or a building by the number of floors or rooms it contains. The Function Unit allows estimators to describe a system as a group of functional or logical components (function points, modules, objects, or screens).

The Function unit is defined by three components:

Taxonomy upgrade extras 
SLIM-Estimate SLIM-DataManager

MTTD Value Increases When Runtime Environment Duration is Increased


I changed my runtime environment from 5 days to 7 days. I would have expected my MTTD value to get smaller because I am running the system longer. Why did my MTTD value get larger?

The MTTD value is simply the reciprocal of the monthly defect rate. Suppose the expected defect rate is 100 defects found during the last month of phase 3. This is a theoretical monthly rate number based on an average runtime environment. The MTTD for this month is therefore 1 month/100 errors or .01 months between defects

Taxonomy upgrade extras 
SLIM-Estimate SLIM-Control Defects (MTTD)

Peak Staff in Solution Panel Doesn't Match Staffing Chart


The Solution Panel says my peak staff value is 10.3, but the Average Staffing Rate charts and reports show a peak staff of 10.1. What is causing this inconsistency?

The theoretical Rayleigh curve used to derive the values on the Solution Panel is a smooth curve resulting in different staffing numbers at each point along the x-axis. In drawing the Average Staffing chart, this smooth theoretical curve is approximated by a series of discrete staffing rates (with one bar, or average staffing rate value, per month).