## Revised Planning Review Sheet (practice, fictional data)

### 1. Recalculation (person-days)
| Plan | Dev | Design | QA | Total | Cost (KRW) | Pass? |
|---|---|---|---|---|---|---|
| A+B+M | 4+7=11 | 1+2=3 | 1+2=3 | 17 | 3,400,000 | Fail: QA 3 > 2 (money is left over, but the QA cap is exceeded) |
| A+C2 | 4+4=8 | 1+2=3 | 1+1=2 | 13 | 2,600,000 | Pass |

- B+M is dev 7, design 2, QA 2 (B's old 5/1/1 plus T2's 2/1/1). QA cannot be skipped and no unfixed release is allowed (T2), and no extra QA staff is approved (T4), so B does not fit this window.
- A+B+C2 would need QA 4 and A+D QA 3, so both still fail.

### 2. Revised plan: A + C2
**In scope**
- A: fast search (required, unchanged)
- C2: the first-use guide narrowed to explanatory wording and step order. It uses T3's estimate, not the full C.

**On hold**
- B (+M): in T1, 2 of 3 keyboard-only participants could not reach the save button. B is not released with that defect, and fixing and re-verifying it needs extra QA, so it is out of this cap. Resume conditions: QA capacity secured and re-validation after the fix.
- D (SSO): vendor schedule unknown and QA 3 exceeds the cap. Unchanged.
- Any work in the original C beyond C2.

### 3. Workload and cost by role
| | Dev | Design | QA | Total |
|---|---|---|---|---|
| Used | 8 | 3 | 2 | 13 |
| Cap | 12 | 4 | 2 | 18 |
| Left | 4 | 1 | 0 | 5 |

Cost: 13 x 200,000 = 2,600,000 KRW, leaving 1,000,000 of budget. Leftover dev and design days are not used for B or any new scope, because nothing ships without QA and roles cannot substitute for each other.

### 4. Work order (not fixed dates)
1. A dev/design -> A QA (1 day)
2. C2 dev/design -> C2 QA (1 day). C2 is independent of A and can run in parallel, but actual staffing is unconfirmed.
3. Release decision after both QA passes. The target date is a requirement, not a commitment.

### 5. Pre-release checks
- QA complete for both A and C2 (no skipping or cross-role substitution)
- Re-check with the revised mockup that the Next button is no longer mistaken for a payment button
- Confirm B is off the release list until its defect is fixed
- No effect figures: S1's 32 still include repeats; S2's 20 of 50 are sessions, not people, with the cause unknown. T1's 2 of 3 and T3's misreading are small fictional checks, not user-wide rates. Do not claim C2 reduces drop-off.

### 6. Decision change table
| Item | Before | Now | Reason |
|---|---|---|---|
| Recommendation | A+B | A+C2 | T1/T2 push B over the QA cap |
| B | Included | On hold | Keyboard defect; fix brings QA to 3 |
| C | Excluded | Included as C2 | T3 validation, new 4/2/1 estimate |
| Total / cost | 13 / 2,600,000 | 13 / 2,600,000 | Same numbers, different scope |
| Leftover | Dev 3, design 2 | Dev 4, design 1, QA 0 | Scope swapped |
| A, D, caps, budget | | Unchanged | T4 |

### 7. Questions to confirm
1. Is there staffing to run A and C2 in parallel?
2. Can the 2 QA days be used when A and C2 each finish?
3. When will QA capacity for resuming B be available?