Data readiness

You will generate value if you manage to reuse data.  We can help you reveal the necessary dependencies between data. Analysis of dependencies gives us an optimal technical sequence for development. If you follow this sequence you will build your applications with minimum effort, maximum quality and in shortest time.

Development sequence

Very often you must follow business priorities when you initiate change initiatives.  But neglecting data readiness and the optimal technical sequence you miss opportunities and you close your eyes for emerging project risks.

How we can help

  • Assist you in developing your optimal technical sequence that leads to data readiness
  • Show you how to prepare for and utilise the optimal sequence
  • Show you how to use the dependencies in risk assessment
  • Show you how a combination of business priorities and data readiness gives added value

DELIVERY ALTERNATIVES

  • On-site
  • Remote
  • Video conferencing

FEATURES

Dependency Matrix

A dependency matrix will show all dependencies between your business data. These dependencies come from business rules, not current or future system design. This compact matrix will be a valuable insight for architects and developers. Once you have it, you will wonder how you could ever do without it.

Information Architecture

The secret lies in the information architecture. If you already have one we start there. If you don’t have one we help you develop the overall business information model. That is where you start in a subsequent detailing of your business information models.

Data-ready sequence

Analysis of the dependency matrix gives us a data-ready sequence for development. Combined with the status of data sources you can give valuable input for your actual application portfolio roadmap. This is engineering tasks that are highly valuable for all organisations, small or big.

Cleanup

Large organisations with data and application redundancy need to clean up their portfolio. Planning this is a puzzle. Knowing all business dependencies is an advantage both for removing, changing and replacing applications and databases.

WHAT’S IN IT FOR ME?

  • You will see and understand why IT will prepare modules for future use, before you request it
  • This is an important tool to speed up business change, reduce risk and save money
  • Existing hurdles for business change will be visible
  • The organisation addresses business changes systematically, and has a plan to improve
  • This is real value delivery from architecture
  • You will produce important results leading to informed business decisions
  • You will learn how to produce this and how and when to use it
  • You will get a necessary tool to plan and coordinate your application and project portfolio
  • It will be a lot easier for you to explain pros and cons of alternative plans
  • Less politics and more fact based decisions
  • More project dependencies, but less risk, which means more value creation
  • Add known dependencies to “Big room meeting” (popular method in SAFe) and get a head start
  • You can hardly find an easier way to improve performance and quality in development
  • Reduce risk and uncertainty, more informed decisions
  • Be part of coordinated teams that make local results that adds up to great business value
  • Informed decisions make better decisions which in turn make stable work conditions
  • Free time and energy to be used in core developer activities

METHOD DETAILS

The methods used have been performed and tested many times. A quality high level information architecture is required. From there we follow well-documented steps for development, analysis and further use. You will not need any of the sophisticated EA tools available. As far as we know – you will not find support for these methods there.
The number of important dependencies between business data is in the range of 70 – 120. This is more than any expert can overview and communicate without documentation. Once documented, you can dive into details without loosing control of the big picture.

CONCEPTS

Changes come frequently. A stream of change initiatives will transform the enterprise. This process must be managed using a value-driven business architecture. Leaders and managers will benefit.

We regard it as the most important tool for coordinating changes and systems development. The sequence can be derived from the information architecture. It is a must if your ambition is to
  • become an agile business
  • reduce cost, risk and time to market

Information is used to managed all of your business resources, like money, personnel, technology etc. It should be managed as a resource itself in the same manner as we manage other resources (how we plan, acquire, use etc). Information is abstract, and we need models to represent it. An information architecture holds these models and lets us manage information as a resource in a structured and controlled manner.

Change initiatives can span from small process improvements to large business development efforts. It can be a project, but not necessarily. So when we use the term “change initiative”, it is neutral for how work is organised.

CONTACT

Back to Services