project management

Project Management Evolutionary Delivery Checklist

- Have you planned for several releases of the software before the full, final capabilities are present?

- Does the first release contain the germ of the program, the seed from which the rest of the program will be developed?

- Will the first release be made as early as possible to get the ball rolling?

- Is the first release usable, at least at some minimal level?

- Have you defined what each evolutionary stage will deliver as best as you can in the hazy dawn of the project?

- Does each release add significant capabilities?

The following guidelines provide a basic checklist for reviewing data models and entity descriptions.
Basic review of model
- Ensure each entity has a singular noun as a name.
- Ensure the diagram is well laid out. Topology guidelines include:
- relationship lines as direct as possible, but retaining clarity;
- master entities higher in the diagram than their details (so avoiding upward pointing relationship arrows);
- minimum crossing lines.
- The diagram should have no visible storage connotations, e.g.:
- indexes and arrays should not be shown unless logically significant;
- business relationships as opposed to physical access paths should be defined.

Review of business implications
Relationship review

Download Free Project Management Process Flow. This simple project management process flow explain how the reporting process between each counterparty in project could running well.