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.
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.
In the first part we discovered the concept of traceability matrix. Today we’ll see the different kinds of matrix used to ensure the consistency of the project.
In a customer request for proposal, the need is usually given through a list of requirements. The supplier sends back a proposal showing his solution through a list of specifications. The coverage between requirements and specifications can take different shapes: 1 to 1: one specification covers one requirement1 to many: several specifications are used to...
Finally ! You did it ! The document is finished. But before definitely freeze it, it has to be validated. So you send it to several people who will read it and comment it. But one week later, you have dozens of e-mail from them and 4 different corrected copies of your document. Those exchanges...
When we write a needs assessment or a specification document for a supplier, we try to be as complete as possible. The document turns into a list of expected features. Here are some good practices to build the most efficient request.
“We’ll have to do documentation again ? Really !” We hear this a lot when we tell a teammate he will have to write some documentation for the project. We are engineers and we have had to deliver many many documents. So let’s be honest, documentation is boring. But when it is well done, it...
