The Project Review Checklist contains a series of 80 questions aimed at finding out if the project delivery has been completed as planned and agreed with the customer or stakeholders.
The Project Review Checklist is grouped into the following categories
You finally delivered the project and had the go live drinks. The team is now breaking up but there are a few things the project manager needs to do to make sure the project is closed and wrapped up. These are grouped into:
Here is a simple to use project close checklist.
Venture Capital investor checklist. This is a useful checklist of what VCs look for when talking to a start up. Useful for the startup wanting to be be ready for their next pitch.
In store now, for only the price of coffee. $4 (Sydney coffee prices OK)
This short post gives some context for what is an MOU or SLA and a basic structure or template for what could go into a MOU. This is focused more on an internal MOU between two departments within a corporation rather than a contractual MOU between a customer and supplier.
You can get the template here.
This post explores the structure of a good template for a business functional specification or template for a detailed functional specification. It looks at the contents and template of a good functional specification, how to work with users and the process of creation of a good functional specification.
I have provided a template of a business functional specification in a simple to follow 10-step way that can be used by a business analyst to walk through with users and collect the business functional specifications for the development of a new or modified application.
In addition there are helpful hints and tips on developing the business functional specification that you can use as you develop the document.
This was a specific request via feedback from one of my blog followers. A big thank you to Heather in Colorado, USA, really appreciate the feedback and I hope that you find this useful.
This post is part of a number of articles on projects, you can read more here.
The Statement of Work (SOW) is a document, which describes the scope of work required to complete a specific project. It is a formal document and must be agreed upon by all parties involved.
In order to be effective, the SOW must contain an appropriate level of detail so all parties clearly understand what work is required, the duration of the work involved, what the deliverables are, and what is acceptable.
Writing a good Statement of Work. What goes into a good SOW (Statement of Work)?
In this post there is a basic outline of the structure of a good SOW. In addition there are some real world examples and templates that you can use right away of SOWs that you can use for either a project or consulting engagement