New Clients

Overview

There is a need to create a standardized approach when bring new clients into the EGIS to ensure that the clients needs are satisfied, and that the EGIS standards are met.

A brief search was done to see if a standard project initial approach existed at TC and none was found. The EGIS team will start with this framework and adjust it as we gain understanding.

Approach

An initial meeting with the clients should define a number of high level details about the client. With these details a proof-of-concept can be created to facilitate further discussion, and initiate our sprint based development approach.

First meeting

The first meeting should give a high-level picture of the business that the new client performs. Stay generic and high level. Try to answer as many of the following questions that are appropriate.

Describe the client

Including the name, all contacts, membership (analysts, DBAs, etc). Include the goals or mission of the groups.

What services does the client provide?

What users do the client serve?

These users are also stakeholder in the project and may be engaged as well.

Is there an existing system being replaced?

Get connection and access details so it may be reviewed. Note what is liked about the current system.

What features must be provided by a collaboration with the EGIS?

List them all. The highest priority will be included in the proof of concept.

What similar products has the client seen that they like?

What features or styles did they like?

Who provides the content / data for this group?

As we mostly deal with sharing data, determine the source. Obtain connection and access details. Consider a sample dataset while connection and access details are obtained.

Does the client have branding that should be used?

Does the client need hosting?

Note: where data is hosted is currently being discussed with the Data Analytics group.

There may be cases where the EGIS acts as just a discovery portal for existing applications.

What deadlines exist for this project?

What budget is at play for this project?

Roles

Define the roles and responsibilities of the Client as the Product Owner, including managing the backlog. Schedule regular meetings.

There is a possibility that training exists for our clients called "Agile for Product Owners".

A standard for data governance is in development, but recommend the client use an open-by-default approach.

Ongoing

After the initial meeting, an initial backlog will be created and a proof-of-concept will be developed. Regular meetings will be used to discuss the product as it improves iteratively.

Expectations

The EGIS project is still ramping up, and the team is initially aiming to deliver generic functionality that can serve the majority of TC users.