Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »


Once the MVP product has been delivered, more focus can be given to product refinement - encouraging a more consistent and robust approach. This approach is by no means exhaustive, but should act as a guide to what "full" refinement of the TIS product and features looks like.


The suggested approach is as follows:

New requirements & Feature development

  • Develop and adhere to an overall screen flow - based on desired site mapping
  • Adhere to components based on UX, which would be linked to the screen flows: Programmes, Posts, People, Placements etc
    • Create and link Epics
    • Create and link Stories to Epics
    • Create and link stand alone Tasks to Stories
    • Design TBD
    • Field validation should be created and linked to Stories/Tasks where relevant
    • Data analysis should be conducted to ensure that we have the data and it supports the design via Metabase and/or in conjunction with Data leads - outputs can be added to the ticket(s)
  • Ensure that all stories contain the relevant items from step 2 (and justification if not)



Artefact TypeDescription
1Component / Theme
  • large area of work that impacts multiple teams / roles
  • will span multiple sprints
  • impacts FE & BE
  • should describe the area of functionality in scope
2Epic
  • focused area of functionality thatĀ  impacts multiple teams / roles
  • may require several iterations
  • impacts FE & BE
  • should describe the focused area of functionality in scope
3Story
  • specific functionality that impacts a single team or role
  • may still require one or more sprints to resolve
  • impacts FE & BE
  • should describe the agile story
  • should include statement of business benefit
  • should include acceptance criteria overall
  • should include links to the field validation & data analysis
  • should describe work around (if applicable), relevant red line dates & H / M / L rating
4Task
  • very specific task related to functionality that impacts a single team / role
  • should be manageable in 1 sprint
  • impacts FE or BE
  • should describe what functionality is
  • should include acceptance criteria specific to task
5UX/UI designTBD
6Field validationĀ 
  • listing of relevant fields, validation, sections, error messages per component / theme
  • rules should be validated with Data leads
7Data analysis
  • extract of relevant data from Intrepid DR (via metabase)
  • flag fields that should be in TIS and/or NDW
  • validate with data leads


Once this checklist has been met, they can be discussed with the Development team for a smooth transition across to implementation. Any further additions can be made on an ad-hoc basis.


Bugs

Where this might differ is where Bugs are raised concerning existing development, in this scenarios TBD

  • No labels

0 Comments

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.