Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

...

  • Initial customer contact - Typically informal, the initial customer contact may be an email, phone call, or walk-in visit where the customer expresses the business problem they are trying to solve. The individual responsible for the initial contact must triage the request and determine if it requires more extensive investigation or can be solved immediately as a minor task. The result of the initial customer contact should be an issue tracker incident that describes the engagement and allows for comment from the customer and the rest of the development team. The customer will be furnished with a link to documentation on our consulting methodology and a new wiki page where they can begin to draft user stories for our next customer meeting.
  • Customer meeting - This is a guided interview process in which user stories are elicited from the customer. The customer has had time to think about the user stories and the interview team has had the opportunity to generate specific questions for the customer prior to this meeting.
  • Translation of the customer user stories into use cases - The development team translates the customers stories into use cases and documents them in the wiki.
  • Customer verification of use cases - The customer provides feedback on the accuracy and priority of the use cases that have been generated by the development team. If necessary, the process loops back to user story and use case generation based upon customer feedback.
  • Generate prioritized backlog tasks - The development team translates the use cases into bite-sized development tasks for the prioritized project backlog. Backlog items should be scoped so that they can be accomplished completely within an iteration. The backlog items are created as tickets in the issue tracker to be worked by the development team.

...