WALKTHROUGHS

Walkthrough steps

Chairperson calls the meeting to order and reminds participants that: -Producer briefly introduces the product -Reviewers comment on the product Create action item list - be as specific as possible Vote Sign walkthrough report

Walkthrough Guidelines

Keep it short No more than two consecutive walkthroughs Don't review segments Use standards to avoid disagreements on style Let coordinator maintain decorum

Maintenance oracle:

Maintenance oracle: This person reviews the work product in terms of future maintenance activities. The goal is to make the system and its documentation easy to maintain.

Presenter:

Presenter: This person describes the work product to the group. The presenter is usually an analyst who has done all or some of the work being presented.

What is a walkthrough?

Walkthroughs, also called structured walkthroughs, are peer group reviews of any product created during the systems development process. The users, management, and development group must review and approve the baseline project plan.

Roles of participants

Chairperson/Coordinator: Presenter: User: Secretary/Scribe: Standards bearer: Maintenance oracle: Data diva Reviewers

Chairperson/Coordinator:

Coordinator: This person plans the meeting and facilitates discussions. This person may be the project leader or a lead analyst responsible for the current life-cycle step.

Walkthrough Don'ts

Correct errors Discuss more than one point at a time 'Nit' pick Evaluate the producer Get off track Go over the time limit

Secretary/Scribe:

Secretary: This person takes notes and records decisions or recommendations made by the group. This may be a clerk assigned to the project team or one of the analysts on the team.

Standards bearer:

Standards bearer: This person ensures that the work product adheres to organizational technical standards. Many larger organizations have staff groups within the unit responsible for establishing standard procedures, methods, and documentation formats. These standards bearer validate the work so that it can be used by others in the development organization.

User:

User: This person (or group) makes sure that the work product meets the needs of the project's customers. This user would usually be someone not on the project team.