| Term |
 |
Definition |
| Architecture Review |
|
Internal IS meeting to determine if project proposal meets architectural standards. |
| Artifact |
|
One of the documents described by the technology life cycle methodology. It may be paper or virtual. |
| Build |
|
The phase associated with construction of deliverables. |
| Checkpoint |
|
A point in time when the project is evaluated against the requirements received to date. At this time, adjustments to the project may be required or the project may be cancelled. This is the final step of an iteration. |
| Cycle |
|
The entire life of a project, from initiation to support. |
| Deliverable |
|
All items that are results of the project. This includes interim products (e.g. project plan, test plan) as well as final products (e.g. new module, new hardware). All deliverables are objects. |
| Delivery date |
|
The date a deliverable is provided. |
| Deploy |
|
The phase associated with delivery of a new product/service to the production environment. |
| Design |
|
The phase associated with detailed requirements gathering; including any prototyping activities. |
| Iteration |
|
The process of following the steps within a phase. |
| Object |
|
The product of one or more tasks. This is used for project and time tracking. It includes items such as meetings, as well as all deliverables. |
| Phase |
|
One of the 5 major breakdowns of the cycle (plan, design, build, deploy, support). |
| Phased implementation |
|
The practice of breaking down a large project into functional pieces that will be delivered over a period of time instead of all at once. |
| Pilot |
|
A tactic in implementation whereby the new product/service is delivered to a select group instead of the entire planned user base. |
| Plan |
|
The phase associated with project startup and initial planning. |
| Project initiation |
|
The set of tasks required to start a project. This includes creating a business case and ROI, which are input to the architecture review. If needed, this also includes even swaps analyses. Project initiation is complete when the directors approve the project and a project manager is assigned. |
| Project management |
|
The work required to track project activity against plan and review all products for adherence to project management standards. |
| Proof of concept |
|
Creating a product limited in functionality to be sure that the technology will perform as required. When new technology is involved, or a novel interaction is proposed, this may be used as a risk mitigation tactic. |
| Prototype |
|
Creating a product limited in functionality as a demonstration, to be sure that the technical team is on the right track. Generally used to give the functional team a view of what the final look and feel will be, to ensure that requirements have been captured correctly. Sometimes used as a synonym for a proof of concept. |
| Support |
|
The phase associated with post-production activities, including maintenance and help desk functions. |
| Target date |
|
The date a deliverable is planned to be ready. |
| Task |
|
The smallest definition of a discrete piece of work, required for the production of an object and used for tracking purposes. Since time tracking requires tasks to take approximately 2 days of effort, some logical pieces of work may be split into multiple tasks. |
| War room |
|
A room set aside for a project team or a subset to work together on the project, separate from the normal work place to minimize distractions and enable focused, collaborative effort on the project. |
