Documentation problem

It is cool autumn weather.


Yesterday, we asked for a chance of demonstration to the customer, which had been my concern all these days.  We have already finished system design phase, but there is risk that the result of system implementation could be something Customer hadn’t imagined, as is always the case with system development projects.


In the afternoon, one of our colleagues found there was system behavior that didn’t match with the design documentation we had already submitted.   It seems we have to fix the corresponding description because it is apparently the spec.



-Aggressive communication without hesitating friction



-Documentation fix successively turns up



-At the next meeting, explain it to the customer and tell them we are going to fix the documentation.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s