Support/Goals/Review Wait Time: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
 
(5 intermediate revisions by the same user not shown)
Line 1: Line 1:
==Reduce articles waiting for review to one week or less==
==Goal==
Why we need to do this:
*Reduce articles waiting for review to one week or less
==Purpose==
*Keep the KB up-to-date so that users can find the answers they need (part of retaining users)
*Keep the KB up-to-date so that users can find the answers they need (part of retaining users)
*Provide motivation to KB editors. It's nice to know that if you spend time working on something it will get reviewed in a timely manner. (part of growing our community)
*Provide motivation to KB editors. It's nice to know that if you spend time working on something it will get reviewed in a timely manner. (part of growing our community)
==Project Plan==
*Work thought the [https://support.mozilla.org/en-US/localization/unreviewed backlog of reviews]
*Engage the reviewer group in one or more "review sprints"
**Define a day to review articles
**Be available on IRC, PM, email to answer review questions
==How do we know it's done?==
*There won't be any [https://support.mozilla.org/en-US/localization/unreviewed articles waiting over a week for a review].
==Schedule==
*Schedule and promote a review sprint for January 26.
*If needed, hold another sprint the week of Feb 20
==Notes==

Latest revision as of 19:00, 17 January 2012

Goal

  • Reduce articles waiting for review to one week or less

Purpose

  • Keep the KB up-to-date so that users can find the answers they need (part of retaining users)
  • Provide motivation to KB editors. It's nice to know that if you spend time working on something it will get reviewed in a timely manner. (part of growing our community)

Project Plan

  • Work thought the backlog of reviews
  • Engage the reviewer group in one or more "review sprints"
    • Define a day to review articles
    • Be available on IRC, PM, email to answer review questions

How do we know it's done?

Schedule

  • Schedule and promote a review sprint for January 26.
  • If needed, hold another sprint the week of Feb 20

Notes