Documenting our Understanding

If it’s not written down, it didn’t (or may not) happen.

In addition to defining what needs to be accomplished with our expected outcomes, some consideration needs to be given on any sort of environment or settings that need to be in place to complete development. Documenting information in a task is vital for success!

Although expected outcomes can be somewhat related to what is needed to be done to test/QA the feature, this is potentially different in that there may be external data sources or dependencies. Documenting our understanding is important in order to have a history of steps taken to resolve issues and complete the task.