ULEADD: Define

DEFINE

Clearly Define all of the criteria for design and implementation, based on the actual needs for satisfying our objectives.
We’ll need to include the definition for solving and not solving the unknown and part of our overall path to success.

For an in-depth explanation and details around how to perform a Needs Assessment review the information at Investopedia at this link.

How we will Define the scope of delivered value

Problem scope can be defined by answering the following question:

  • What is the actual problem?
  • Do we need to solve this problem? Is this the right problem to solve?
  • Will our solution deliver the expected outcome?
  • What’s needed to solve the problem?
  • Are we positioned to solve this problem?

Problem Definition

The problem statement will serve as our baseline as to why this initiative is worth our effort. Once that is complete and we move into other phases such as business expectation statement or business justification we will begin identifying what the business expects to get from doing this initiative. We’ll add more context and details around this initiative when we identify the Objective’s and key results (OKR’s) target dates, triple constraint, and Key Performance Indicators (KPI’s). the final artifacts needed to complete the definition phase are:

  • Problem statement
  • Business expectation statement
  • Targets (OKR’s, KPI’s, dates, etc)
  • Risks, gaps & constraints
  • Impact Expectations
  • Identified data challenges