Generic Project Pages

Overview
These pages on the Wiki are intended to help someone starting a project (presumably tied in some way to VistA) and provide forms to make the project consistent and understandable to its participants.

Generic Project Pages Organizing Principles
Since the MediaWiki software allows sub-pages, each of the generic pages that will be available to copy for a project will be organized as a sub-page of this page. That means the URL for these pages will be formed like this:

http://vistapedia.net/index.php?title=Generic_Project_Pages/ SomePageName

Note that the text in Red will change based on the various kinds of pages that may be created.

Generic Agenda for the First Meeting of the Project
The first meeting of the project is usually between the people who want the project to occur and the people who are going to organize the project. This rarely includes the people who are going to make the project happen. In many cases, the people who know the technical details of implementing the project will not be interested in the first meeting, because it involves finding answers to questions that they expect to already be answered by the first meeting they attend.

[| Generic Agenda for the Kickoff Meeting of the Project]
By the time the Kickoff meeting, the basic decisions have been made that the project will occur. The general scope, schedule, and resources have been decided. The Kickoff meeting brings the people who are going to work on implementing the project together, informs them of the broad outlines for the project, and establishes the roles they are going to play in the project. The Kickoff meeting is not the time to go into the details for any given person, but to create a common understanding of what the project is, how long it will take, who is involved, what processes will be followed, and when key events will occur.

[| Generic Agenda for the Wrapup Meeting of the Project]
By the time of the Wrapup meeting, the activities that make up the project have have been completed. All efforts to implement the scope have either succeeded or failed, all of the scheduled events of the project and their deadlines have passed, and resources have been used as far as the purpose of the project is concerned. The Wrapup meeting brings together the people who worked on implementing the project, or at least those relevant to the evaluation of the project. The broad outlines for the project are reviewed, lessons that can be learned from the project activities are expressed, and disposition of any extant project resources is established. The Wrapup meeting is not the time to go into the details about the success and failure of the project, as that should alerady be clear before the meeting. The Wrapup meeting is intended to create a common understanding of what occurred in the project, what kind of organizational follow-through will occur, and what impact the project had.