“Unfortunately, most will just view the team projects, class presentations, software life cycles, and ambiguous problem statements as ‘hoops they have to jump through’ to graduate. I recall a meeting with a student who was having trouble working with her project team in a recent class. She actually asserted with some confidence that the problem she was having with her team members…wouldn’t happen in industry. She was stunned when I explained…” William Harrison —The Software Developer as Movie IconIEEE)

What Prof. Harrison says about computer programming projects can also be said about techncial writing, or about almost any project. In the real world, rarely do workers have complete project specs handed to them; rarely do they have enough time and/or resources; rarely do all the team members have all the required skills; rarely are key personnel available to consult at convenient times; etc, etc.