Versions Compared

Key

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

...

  1. find the domain and stakeholders << VCE definition?
  2. find the purpose << mission, value for the domain?
  3. find the challenges << what are the current issues and problem statements?
  4. find the history <<. what were the expectations, investments, consequences of past efforts?
  5. find the goals and priorities now << what are the current goals, priorities and related KPI, OKR metrics 
  6. find the best solution strategy << given the goals, resources, needs, what is a candidate best solution strategy?  << VCRS
  7. find the potential value << research the potential value, impacts for a "best" solution strategy with those responsible for delivery and operation << FACTUR3DT.io << POVs
  8. find stakeholder consensus << net value for change? ownership? VCRS keys communication, consensus, collaboration methods
  9. find the commitment for the solution << CBTP << new expectations << new solution commitments << resource and solution planning strategies, tactics
  10. kick off the solution process


How to manage a missed milestone on a data solutions project


how to handle missed milestone in data architecture project

https://www.linkedin.com/advice/0/heres-how-you-can-navigate-aftermath-missing-eiv5f

a financial services example ---

need defined for a new, common source of truth with central data warehouse and multiple feeds and services to solutions

  1. <<< prior segregated data marts with ETLs to synch data as needed
  2. <<< DQM issues, impacts
  3. <<< IT management had poor value, credibility score with business
  4. <<< goal was a single source of truth data warehouse with many feeds, services, secure


data services and operations teams were segregated from the data warehouse design team
the new data warehouse had never been done by the company

  1. <<< data warehouse design team reorganized 3 times with new personnel
  2. <<< data warehouse team had good business but not strong data architecture skills
  3. <<< after 3 reorgs, the data model came out 6 weeks late
  4. <<< the data warehouse team shared little until done
  5. <<< my data services team was fully dependent on the data model
  6. <<< the warehouse data model delivered was unusable
  7. <<< the data services team had to engineer a working, useful data model for services
  8. <<< we communicated weekly to the CIO our dependencies, the expected impacts of delays
  9. <<< CIO made faces and said we needed to make the original deadline
  10. <<< we delivered the data services to go to production 6 weeks late as well
  11. <<< we failed to make up the lost time from the warehouse team
  12. <<< key - we failed expectations and there were consequences


own the problems first then your team's responsibilities and support clearly
communicate clearly, directly, immediately with all stakeholder groups
agree on the core team to lead analysis and solution definition going forward
identify missed expectations, consequences
research together root causes for failures, missed opportunities
collaborate with stakeholders on options, best strategy forward




Candidate Solutions



Step-by-step guide for Example

...