You will find here our background posts on project documentation and the associated writing methods based on our expertise, our feedback, and industrial engineering practices.
So the first revision of your document is now all written. Before sending it to your customer or your supplier, it can use a peer review to check its content. Let’s see how we can manage such a review.
It is very important to track the changes in every document of a project, in order for all the contributors to be in sync. In this article we will see how a few coding tools, like SVN, can be used to this end. We’ll start with a description of the principles of version and configuration...
Here is a method to write a request for proposal: which elements to put in, how to sequence and structure its content… Those best practices come from our own experience of engineering project management and from companies we worked with.
“Yeah, just have a look on the specifications… They’re on the shared drive, or in your mails. And the title of the document is… Specifications_v1.1_draft(3).doc”.Wow wow that doesn’t sound good. Unreliable revision located somewhere in several copies… to fix that you only need a couple of management rules and pretty simple methods. Together, let’s see...
For over a year now, we have been interrogating more than 200 companies about their documentation activities. Help us to better understand how to document a project by taking part in our study. Let’s dive into this number: 40%.
A collaboration between a corporate and a startup can take different shapes according to their needs. But their very different cultures can make it difficult. Corship designed a free tool to help those companies to settle the foundations of such a project for a greater success.
