Task Checklist

A checklist to help estimate the time we might take to finish a task. I didn't set a limit on the totals but generally each task shouldn't exceed 16 hours or 21 story points.

TaskHoursStory Points
DATA
Where does it come from?
  • Is it easy to access?
  • Do we need authentication?
Does it contain all the properties we need?
Have we actually seen it or are we just assuming that we probably have this data because it's so obvious? (Don't assume. lol. 😭)
Does it need to be transformed?
  • Is it complex to transform?
  • Does the data's reliability depend on many third parties?E.g., country calling codes 📞 could start with +, 0, 00, or a whole slew of other patterns depending on country. It might take a lot of investigation just to figure out what the data is really about, and how to break it up into component parts suitable for our use case.
  • Does the new form need to be stored somewhere?
  • Should we work it into a regular ETL and CD process?E.g., daily cron job to ETL public transport traffic data, transform it, test it, then deploy to a server that uses Docker in Kubernetes in Azure 😅.
Do we need to communicate with several parties over a period of time to get this data, and in a form we can use?
UI/UX (IF FRONT END)
Does any part of the design look different from native browser elements?E.g.: The little up and down arrows on a select dropdown, or the colour of the centre dot in a radio input. These cannot be changed so we have to fake them with entirely new components. But, because of accessibility, we have to somehow connect the fake component with the real one. Like, maybe put a real radio input inside the fake one but with opacity set to 0 so nobody sees it. It can be a bit of a tall order.
What does it look like on mobile and desktop?
How should the UX behave?
Are the updated designs readily available?
How much time to add accessibility?E.g., invisible elements that screen readers should read out, can tab through all elements, UX for focused elements.
Does it work on all browsers we support?
Do other teams' CSS override ours in production?Could happen when multiple teams develop separately but their work is merged in prod.
Tests!
REUSED CODE/COMPONENTS
Do we have to reuse code?How easy is it to edit and/or inherit for the new use case?
Do we need to refactor existing code? If yes, do we need regression testing?E.g., legacy code, update libraries.
Is it complex?E.g., deeply nested modules or 1000+ lines in the module.
Will regression testing be complex?E.g., if edited code touches 10 services, manual testing might be required in spite of extensive test coverage, especially when it's UI/UX.
TESTS
Difficult?
Totals