Haziq said:
In others words project should be self-explanatory.
This is never the case. Explain it with words, show pictures and diagrams, make animations, show math formulas, talk about it, have meetings discussing it, and there will STILL be differences in understanding.
Even people who are amazing at communicating ideas clearly can still struggle to communicate their vision exactly.
Each person needs to be careful about their explanations and do their best to communicate as effectively as they can, then be generous in allowing for implementation differences.
Haziq said:
The only issue which I have faced often by other team member that the project is not well organized based on the professional environment and the professional workflow is not used by me. I only want to know how would I know what is standard professional when transferring the work
Every project does things differently and there are few standards. They range from zipped up directory trees of files uploaded to file transfer sites, to allowing access to wikis and version control, to shipping disks or thumb drives, to shared documents on Google Drive, and everything in between.
Talk with them, discover what they need and want, figure out what you need and want, and find something that works.
If people are using a specific tool, sometimes that tool will have an organization standard that works well for it. Based on your game you may find there are logical ways to organize data, such as terrain and world, game mechanics, characters, weapons, abilities, or whatever, but that organization will be unique to your game and your explanation style.