📊 stats, stats, and more stats

[jadudm]

At a glance

In order to do the data analytics
as a data scientist
I want data

Acceptance Criteria

We use DRY behavior-driven development wherever possible.

Scenario:

Given
when
...

then...

Beta Give feedback

1. [a thing happens]

Shepherd

• UX shepherd:
• Design shepherd:
• Engineering shepherd:

Background

• Click-through rate
• Impressions (per search result) (this is basically host/path counters)
  • computed value: times clicked/impressions
• Time to resolve queries
• Pages fetched/day (or per site/day)

Product success metrics (monthly)

CTR
CSAT score (customer satisfaction score)
Service uptime (resiliency)

Affiliate (host, possible aggregation/disaggregation), Search Query, Clicks, Impressions, CTR, Average Position

Security Considerations

Required per CM-4.

---

Process checklist

• Has a clear story statement
• Can reasonably be done in a few days (otherwise, split this up!)
• Shepherds have been identified
• UX youexes all the things
• Design designs all the things
• Engineering engineers all the things
• Meets acceptance criteria
• Meets QASP conditions
• Presented in a review
• Includes screenshots or references to artifacts
• Tagged with the sprint where it was finished
• Archived

If there's UI...

• Screen reader - Listen to the experience with a screen reader extension, ensure the information presented in order
• Keyboard navigation - Run through acceptance criteria with keyboard tabs, ensure it works.
• Text scaling - Adjust viewport to 1280 pixels wide and zoom to 200%, ensure everything renders as expected. Document 400% zoom issues with USWDS if appropriate.