Words| chapter 11

14 Oct

Don’t write specs documentation because it is not realistic. The app can only be considered real if the team already started doing the actual app (design & code). Specs documentation can also lead to some future problems like the difference in expectation. So, it is better if the people involve in the project has the same vision of the final output (everyone has a different way of analyzing and comprehending things.)

Unless the the documents that your team are doing will turn into a real thing, pursue it! But if it is just a useless and pointless documentation, forget about it! Unnecessary documents (if piled-up) can lead to future referencing problems. Instead if doing documentations, it is better if the you will make a prototype instead of just writing your ideas. “Stick to the experience instead of getting hung up on the details. Think strategy, not tactics.”


Leave a Reply

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

WordPress.com Logo

You are commenting using your WordPress.com 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

%d bloggers like this: