Data Service Requirements

Process Component Service Requirements


Description

Outline of what the client is trying to achieve and crucially what the Account Manager has proposed. It is also absolutely essential that service requests states which version of the software is being used so that the consultant can if necessary prepare a Virtual Machine.

Processes (that produce or use this component)

Deliver Consulting Services

  • Category: Input
  • VSM Role: System 1 - Operations
  • Feedback Notes:

    Any feedback reports should always be sent to the sales person. In addition:
    - Any client issues
    - Product weaknesses
    - Misleading information given to client (e.g. promises that the software can do things it cannot)
    - Misleading information in the service request

  • Potential Issues:

    Service Request is vague, incomplete, inaccurate, or misrepresents the software capabilities, e.g.
    - Does not specify what version of the software they are on
    - Says client wants X (say, set up a process diagram template), when in fact X is only a minor component of the real requirement (say, set up a Process template, produce a set of diagrams, and simulate them)
    - Uses jargon without any sense of work to be done (e.g. client wants a Process architecture in two days)
    - Is misleading to client, e.g. set-up automated comparisons, complete with audit trail, between as-is and to-be models.
    As suggested above, this can often lead to the client Requirements being completely unrealistic, suggesting failure, upstream, to manage expectations.

  • Evaluation: 2

Identify Client Requirements

  • Category: Output
  • VSM Role:
  • Feedback Notes:
  • Potential Issues:
  • Evaluation:
Appears On

IGOE Scope Diagram Deliver Consulting Services

VSM View Deliver Consulting Services