You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

Initial Contact:

During the initial contact step of the flowchart, a very freeform discussion takes place with one consultant and the customer(s). The initial engagement will be logged in MI6, allowing the customer to log feedback through JIRA. The customer is given documentation about the process at the initial meeting to help them generate their user stories. Either a link to a basic outline if they're already familiar with the process, or a more in depth set of documentation if they are not.
A checklist is needed for the initial meeting, to make sure the consultant obtains the key pieces of information needed from that step. Some structure in the initial meeting helps determine whether or not the customer has a good understanding of the full scope of the project. Initial proposed questions for the checklist were:

  1. What data is involved?
  2. What people are involved (as in need access, need a process, or need to provide permission of some sort)?
Between Initial Contact and Customer Meeting

Between the two steps, anyone in the organization has the opportunity to add further questions or raise concerns. Anyone who feels they have a stake in the project are invited to speak up.

Customer Meeting:

Compared to the initial contact, a much more guided and directed step. It was decided that we table discussion of this step until we can review best practices on guided customer meetings. John agreed to look into this.

Translating User Stories Into Use Cases:

There's always at least a goal, at least one active player, passive players, tasks, and one to two paragraphs describing getting from the start to the goal. Sample stories and sample use cases will be sent to the customer. John already has documentation on this, and will research it further.

Customer Verify Use Cases:

Fairly self explanatory, they look at it.

Tasks for Backlogs:

Developers generate tracker incidents for each programming task. The big challenge of this step is estimation. Shannon will look into this further.


Russell will make a flowchart of the process from the picture he took.
Larsson will write a prose framework for the process, outlining the scaffolding for the whole process.

  • No labels