Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Start doing

Stop doing

Keep doing

  1. Add comments in the code base to provide a brief explanation of the implementation.

  2. Connect with the developer who created the PR. its easier to explain things on call rather than posting a long comment in the PR. (comment from Kevin: Sure - but then document that call on the PR for future generations)

  3. Add a lane on JIRA, before verification where the UI/UX designer can review UI issues associated with a ticket

  4. Prioritizing review of tickets in validation (same day review)

  • Approving PRs without actually reviewing them

  • Great team work. shout out to Duncan Brain for doing a though review of field work PR.

  • Shout out to Richard Wasswa (Unlicensed) in helping me out in the irrigation task module and resolving the PR comments.

  • Booya! Carlos Moreira (Unlicensed) had his first ticket merged in - you’ll now have a tiny impact on thousands of people around the globe!

Action items:

  •  Add “Community manager” role for each sprint planning to support new contributors Lite Farm
  •  Create some documentation around common libraries we use (add to “Getting started”?) - ticket for next sprint?
  •  To discuss during next planning session, implementation of “Start doing” #2, such that there is a reduction of lengthy comments on PR, possibly adding this as a portion of definition of done.
  •  Carolina di Lello (Unlicensed) and Mwayanjana Bolokonya (Unlicensed) to define how best to verify UI/UX tickets
  •  Lite Farm During planning on 12/12 to review the comment from “Stop doing” Approving PRs without actually reviewing them