explanation please

There are real life projects that fare just fine without a formal project management plan, most likely because one or more of the following apply:

1. The project does not have a high degree of uniqueness and is very similar to prior projects (in the organization)
2. The expertise level and degree of coordination/teamwork is very high
3. The project is"small" and/or inherently simple
4. There is a very high degree of colocation of team members (example: all five team members are in the same room)

On the other hand, a high percentage of projects encounter major challenges, slip cost/and or schedule, or even wind up getting cancelled after major investments have been made in them because the project team failed to put together a sound project management plan. As a project manager, your responsibility is not to blindly follow a recipe for putting together a project management plan, but to use your knowledge, skills, experience, and judgment (and common sense!) to determine when such a plan is needed, which sections of the plan are absolutely essential, and what degree of formality and rigor those sections need. Moreover, you should always strive to use visualization (charts, meters, heat maps, dashboards, etc.) to the greatest extent possible as opposed to vast amounts of text that run the risk of not being read. This requires that you understand your project well and that you also understand your team, stakeholders, organizational culture, environment, and perhaps even your industry in general.

This team assignment requires you to exercise this knowledge, skill, and judgment for the project that you worked on this term. You will only focus on the communications, stakeholder, quality, and procurement management sections of the project management plan for this assignment. Your assignment should be about five to six pages (double spaced) altogether. Any charts, pictures, visuals, etc. do not count towards this page limit. Divide your assignment into four parts, one each for communications, stakeholder, quality, and procurement, and in each part clearly, succinctly, and convincingly address and argue the following:

1. Does your project management plan need a section that addresses that knowledge area (communications, stakeholder, quality, procurement). Why or why not? If the answer to #1 above is "no" (for one or more of those four knowledge areas) then you can skip #2 and #3 for that knowledge area. However, you should then offer a very compelling argument to justify your "no" answer. If the answer to #1 above is "yes", then address the following for that knowledge area:
2. What type of information would you include in the project management plan (for that knowledge area), and why; and to what level of detail and formality? You don't have to include the actual information. Only justify and explain the type and level of detail/formality of the information.
3. How much of the information (in #2 above) could be presented using visualization as opposed to text? Provide visualization examples if possible. You don't have to develop these visualizations specifically for your project. You may use generic examples to make your point.