P3 skip evaluation

From DPWiki
Jump to: navigation, search

Project Managers (PMs) and Post-Processors (PPs) can request that a project skip P3 and go directly from P2 to F1. This page discusses the requirements and suggestions for determining if a P3 skip is a good idea for a project.

Determining if P3 skip is right for a project

There is no single criterion that can be used to determine if a project should skip P3. There are several different factors that a PM/PP should consider when deciding if a P3 skip is the right decision.

See also the Current policy for PM-requested P3 skips.

Tool recommendations

Probably the first place to start is the Site-wide retread/skip recommendations tool. This tool uses the results of the Confidence in Page analysis work to suggest projects that are good P3 skip candidates. Even if the project isn't listed here, consider using the Show all project retread/skip recommendation tool to view all of your projects in P2.waiting. The project may still be a good P3 skip candidate based on the other criteria listed below. To see information about a specific project, use the Project retread/skip recommendation tool.

Note that just because the tool suggests a project for skipping P3 does not mean that it should. This is simply one metric to consider when determining if a project should skip P3.

Non-standard round history

The standard round history for a project being considered for a P3 skip is P1->P2. Some non-standard round histories may improve the quality of a project and improve the odds of a P3 skip while others may decrease the odds of a P3 skip.

P1->P1

Anecdotal evidence shows that P1->P1 projects can be good P3 skip candidates.

No P2

Projects that did not go through P2 are probably poor P3 skip candidates.

WordCheck usage

High WordCheck usage on a project can make for good P3 skip candidates. Projects where most of the pages have been WordChecked in P2 may be good P3 skip candidates. Projects where few, or none, of the pages have been WordChecked are often poor P3 skip candidates.

Types of diffs

Spot-checking the diffs between P1 and P2 can show you what kind of things were caught in P2. If most of the things that P2 found were items that can be easily caught and corrected in PP the project may be a good P3 skip candidate. If most of the changes in P2 were stealth scannos P3 skip may not be ideal.

Quality of scans

Clean scans can improve the quality of the P1 and P2 rounds and can make for good P3 skip candidates. Poor scans can make for poor P3 skip candidates.

Number of different proofers

Having more eyes on a project in a given round is a good idea. What one proofer may miss another one can catch and can help with some of the other criteria, such as the Type of diffs. If most pages in a round were proofed by the same proofer, the project may be a poor P3 skip candidate.

Committed PPer

Having a PPer who has committed to post-process the project is a big bonus for a P3 skip candidate. See also WANTED: PPer for round skip

Requesting a P3 skip

Getting PP approval

If a PP has signed up for the project, you must obtain his/her permission before requesting a P3 skip.

Sending the request

To request a P3 skip see the instructions on the db-req wiki page.