Wiki Pages > Metrics Derived From Requirements

Metrics Requirements

Requirements arise from three sources: users, clients, and our own internal, professional standards.

User Requirements

Metrics important to users tend to be product metrics. Metrics typically important to users include accuracy, appearance, and usability.

Usability tests and satisfaction surveys are practical and effective ways to gather user metrics.

Client Requirements

Metrics important to clients tend to be process metrics. Metrics typically important to clients include accuracy, cost, and time to produce.

Tracking completion milestones are a practical and effective way to gather client metrics.

Internal Requirements

Metrics important to documentors tend to be workgroup standards. Metrics typically important internally include adherence to style guides, templates, logo specifications, and boilerplate text.

Checklists are a practical and effective way to ensure adherence to workgroup standards. For example, reducing spelling errors increases document quality; using spellchecking software reduces spelling errors; therefore, requiring that spellchecking software be used before each draft is released increases quality.