Clarification of "time required" values

[AaronUXD]

Overview

Update 18F Methods time required to be specific

Tasks

• [x] create a spreadsheet with how "time required" is described on each site
• [x] make a recommendation for a standard way to describing time required across the methods
• [x] review by a member of the TLC team
• [x] update the spreadsheet with text that meets the standards

Acceptance Criteria

• [x] spreadsheet with consistent way of describing the time required to complete each 18F method. Implementation ticket to follow

Background

Great site! Could you clarify what the "Time Required" represents, or where it came from? (e.g. is this what 18f uses for sprint planning estimates?)

Saying time required "it depends" isn't necessarily helpful either, but noticed some variation in how it's used -

Some examples:

Represents time from end-users, but not preparation or analysis from team:

Seems oddly low (e.g. design pattern library: 1-2 hours per pattern, does this suggest that the US design standards were created and posted by one person in 1-2 weeks?)

This one seems to make more sense in how its phrased - broader range of hours for creation activity, and also time per person to give feedback, could add a few hours to gather and publish results to team. (The total time still seems low for someone to estimate sprint task time though.)

[MelissaBraxton]

Hi @AaronUXD,

Thanks so much for your feedback!

These estimates were not intended to be used in sprint planning but are more general guidelines of how long, in our experience, these methods can take.

Your point on the inconsistency in how these estimates are represented is well taken. We do intend to evaluate these estimates, and revise them as needed, in the coming months.

Thanks again,

Melissa

[line47]

@MelissaBraxton - any progress on this since the last comment?

[juliaklindpaintner]

This still seems worth addressing. Time required is not consistently estimated across methods.

[mgwalker]

Closing as stale, on the assumption that the need will resurface if it still exists.

[qmanderson1]

Recommendation could be informed by other team members in slack.

[qmanderson1]

Time Required Spreadsheet/Recommendations here

[boonerang]

This looks great, nice to see these all in one place.

It’s almost impossible to get specific on many of these activities so the “Average X-Y” allow for flexibility of the skill level of the individual or team doing the work.

I’ve adjusted most of the suggested to include average ranges and allowances for varying levels of skill in the spreadsheet.

[bpdesigns]

@qmanderson1 please review @boonerang's updates. Let me know once you've done. I'll give it a final review. Thanks

[qmanderson1]

@bpdesigns I've reviewed Boon's updates. This ready for your review. Thank you.

[bpdesigns]

Thanks @qmanderson1 ! This is ready to close.