PROJECT CHECKLIST

Project requirements
Has use cases written for the requirements
Will the customer agree to spend time in formal requirements gathering meetings
Has the requirements been prioritized in terms of business value
Is peer review of requirements understanding done
Estimation and scheduling
Project objective understood and reviewed with management and customer
Have the project resources been a part of the process of estimation
Have the estimates reviewed by peer

Project planning
How much is the reused portion of the project
Are all the risks taken into account
Level of experience of the resources for the project
Has the peer review done for the estimation
Project communication channels other than mails?

Staffing
Are the best people available?
Do the people have the right combination of skills?
Are enough people available?
Are staff committed for entire duration of the project?
Will some project staff be working only part time on this project?
Do staff have the right expectations about the job at hand?
Have staff received necessary training?
Will turnover among staff be low enough to allow continuity?

Code Design
Have the project resources participated in the design review
Have the design been reviewed

Is the review consistent with the standard

Coding
Is there already a sample for the work with the customer which can be used as the
framework.
Is there a framework for the work available that can be reused.
Is there a peer review of the code written
Is there iterations of the code functionality at periodic intervals with the customers
Is there technical competence with the customer to understand and approve the work
done.
Is a coding standard available and all project resources made to understand them.
Have the unit test cases written before the coding starts
Have the requirements been traced to the code
Is the code commented
Are the code review comments actioned on and reviewed again by PM
Are the metrics for the coding below the tolerance limits
Have the performance checked
How is the defect measures collected

Configuration management
Is configuration management tool used for checking in and checking out the code
Are constant backups made for the system
Change control
Is the scope of the project defined and frozen by the customer
Has the requirement change go through change control

Testing
Is unit testing done by the developers before checking in the code
Are testing tools available and appropriate for the product to be built?
Have members of the project team received training in each of the tools?
Are local experts available to answer questions about the tools?
Are compilers or code generators available and appropriate for the product to be built?

Documentation
What is the requirement for documentation
What is the priority and extent of documentation needed by the customer