Would you please comments on this discussion and add your thoughts?

In chapter 10, I agreed with most of the suggestions for improving project communications to help the project management process flow as smoothly as possible. A communications management plan is certainly useful for managing the different interactions with stakeholders, and mainly the people working on the project. I completely agreed with one of my classmates when they described the way that the chapter explained how meetings should be. As we know from learning about project management, things change along the way that are sometimes out of our control. For example, the book describes that meetings should not be very long, which I understand, but to a certain extent. Of course, you don't want to waste anyone's time with a long meeting and it is important and most efficient to be upfront and discuss the subject at hand in an open way. On the other hand, meetings can run over schedule just as a project can. If a meeting is a bit longer, sometimes that can help build the employee's knowledge and give time for any questions to be asked so that everyone has a good idea of what they should be doing. Overall, I think that the book does a great job at explaining project management but for some reason, this point stuck out to me, mainly because I had never really heard that "meetings should be short" before.

References:

Schwalbe, K., Information Technology Project Management. Smartsheet. 8th ed (2017). Cengage Learning, Boston, MA.

Project Management Institute, A Guide to the Project Management Body of Knowledge: PMBOK GUIDE. 6th Edition. Project Management Instituted Inc., 2017. Pennsylvania, USA.