Skip to content

Instantly share code, notes, and snippets.

@Potherca
Last active March 17, 2021 10:28
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save Potherca/b4f68ed264de6eb5d7b55d3e84aee55f to your computer and use it in GitHub Desktop.
Save Potherca/b4f68ed264de6eb5d7b55d3e84aee55f to your computer and use it in GitHub Desktop.
Plan of Attack / Work Breakdown Checklist

Plan of Attack / Work Breakdown Checklist

Before starting work on a ticket, ask yourself the following questions:

  1. Who will benefit by the implementation of the ticket?
    The end user? Other developers? Other systems?

  2. What do you need to edit in the code to implement the ticket?
    Which classes or components need to be touched?

  3. How do you plan on implementing this ticket?
    Which steps do you need to take? Break it down into small chunks!

  4. How long will each step take?
    If you estimate a step will take more than 8 hours to complete, create a (sub) task or new ticket for it.

  5. The ticket estimate is the tally from all step estimates.
    Round up if it does not total a number in your planning-poker card set.

1. Main benefit

The main benefit of this ticket will be for …

Because …

Original User Story / Ticket

… ~ https://example.com/…

Deliverables

  • Users can …

Check / Validate:

Any questions or uncertainties that arise whilst reading the ticket should be written here.

  • Q. Can … be (re)used?
    Does a new … need to be added? -> Should …
    A. If different endpoint, create new lib.

2. Edits in the code

Expected

  • Add … in /path/to/file/…
  • Edit/Change … in /path/to/file/…

Unexpected

(Any unexpected edits that take place during implementation should be added here)

3. Plan of attack

(Steps to take, some common tasks have been provided)

  • Investigation (…h)
    • Read … (…h)
    • Create POC for … (…m)
  • Technical Design (None needed)
  • Implementation (…h…m)
    1. Completed task (…m)
    2. Uncompleted task (…h)
    3. Cancelled task
  • Verification (…h)
  • Final implementation round (…h)
    • Minor tweaks / bugfixes based on review (…h)

4. & 5. Estimated Timeframe

  • Investigation (…h…m)
  • Technical Design (…h)
  • Implementation (…h)
  • Verification (…m)
  • Final implementation round (…h)

Total: …h (…h…m + …h + …m)

Based on somewhere between 6 (best case) and 3 (worst case) productive hours per diem, work will be completed between … and … work days.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment