How to write software project documentation to give to software engineers

Here is my Amazon author page with the 6 books I wrote: http://www.amazon.com/Alex-Genadinik/e/B00I114WEU

For more marketing and business help, check out my apps, books and online courses for entrepreneurs: http://www.problemio.com

In this video tutorial I explain how to write software project documentation. There are two approaches that I recommend. The first approach is to have very loosely written documentation if you are working with more of an extreme programming approach to writing software. The other approach to writing software documentation is to have more well defined documentation that details what should happen when each button is pressed on each screen. That is quite painstaking, and isn’t typically used in the software industry despite a few exceptions. There are some instances when you should use the very detailed documentations, but they are rare. Some examples are when you give project requirements to an agency or a software developer. While you can always change the requirements, it would be cheapest for you to never change the requirements until they complete the project. That isn’t often possible, and usually you want to have more flexibility with your engineers. But the more clearly you can explain to them exactly what you need them to build, the more likely they will build it for you in the way that you need to have it created.