I think it's pretty rare for companies to use every point of an IEEE standard for test documentation, and for good reason. Anything more than what you need for your organization is time spent doing something other than testing software. It might be good to review the purpose of the standard, and ask how it is serving your role and your organization.
How many companies actually create test plans using EVERY point of the IEEE 829 standard template?
I am on a team of two working on standardizing testing for the company. The culture here is very resistant to change, as I am sure many colleagues on here have experienced themselves. I want to continue pushing this elephant up the stairs, but I am afraid some of these templates (IEEE 829 standard templates) are too dense for most of them. My mentality right now is to take this in strides. I want to avoid creating a 12 part test plan that people need to follow if they are just going to get defensive and say they do not have the time to even test, or test this way. Of course we have plans to educate as much as we can, but this is going to take years. What are your suggestions, then, with creating templates? Right now I have identified three that need to be used across all teams (Test Strategy, Test Plan, and Test Summary). We have plans on creating a best practice document/resource for teams to educate them on the industry standards.