Readers/Web/Team/Story estimation

This page provides guidelines and examples to provide some background on how the reading web team estimates.

Examples of pointed tasks
For reference, here's a table with examples of previously pointed cards to be used as a reference in future estimations.

XLarge (8)

 * Event logging: Update event logging used for Hovercards

Large (5)

 * Feature: Create Special:Citations fallback for non-JavaScript/Resourceloader unsupported users

Medium (3)

 * Tech debt + Upstream: MobileFrontend should use upstreamed mediawiki.router
 * UI bug: Search overlay drops 1px when you type into input (note: this was an unusually involved fix and not a good example; please replace)
 * Feature change: References sections should always be collapsed
 * Deployment preparation: Prepare HoverCards for A/B test on smaller wikipedia project

Small (2)

 * Regression: Call to undefined method DOMDocument::setAttribute( in MobileFormatter.php on line 239)
 * Security review: Security review of Hovercards before beta->default conversion

Very small (1)

 * Config variable change (deployment) with SWAT: Increase ON percentage for Hovercards A/B test 1
 * CSS bug: Rename watchlist icon in main menu to not collide with OOJS

Spikes (0)
Spikes will have the tag #spike and in the title will express a finite window of time during which the task will be worked on. We point these as 0 to note that these have been discussed and agreed upon by the team during an estimation meeting.