Skip to content

Instantly share code, notes, and snippets.

@vmbrasseur

vmbrasseur/db.md

Last active May 3, 2017 05:29
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 vmbrasseur/f5587442355849ed2bcd467e9c7df13e to your computer and use it in GitHub Desktop.
Save vmbrasseur/f5587442355849ed2bcd467e9c7df13e to your computer and use it in GitHub Desktop.
Download ZIP
Outlining thoughts for Donna project
Raw
db.md

Goal

  • decomission a legacy bespoke PHP application
    • replace it with an open source ETL where it makes sense to do that
    • transition it's functions into other things where it doesn't

Moving parts

So the bits which jump out immediately:

  1. Replace with open source ETL
    • List items to replace with OS ETL
    • Evaluate for commonalities
      • Refactor into separate item
    • Foreach item
      • Detail how they will be replaced
  2. Transition to other things
    • List "other things," each and every one of them
    • Evaluate for commonalities
      • Refactor those into separate item, if applicable
    • Foreach item
      • Decide to what will it be transitioned
        • Deciding can be a project in itself, alas.
      • How will that transition occur

Project planning

Once you have those items identified…

  1. Split into phases
    • Common bits for ETL & non-ETL (if applicable)
    • Break down each phase
    • Run past team member(s) for reality check/best & worst case scenarios
  2. Work with teams for estimates
  3. Correlate against customer needs
  4. Add appropriate padding
  5. Set delivery dates for each phase
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment