There are different structural organizations that can be made to a company in order to become a more productive and efficient company. One such structure is referred to as the functional structure where the groups are divided based on their function or activity. In this time of structure, companies or teams will be divided into their respective specializations. With this form, efficacy and production becomes easy only after the process has been systematized. However, with this structure, communication between the different sections may be a problem due to the high level of specialization between the different sections which may cause some misunderstandings and frustrations.

Another project management style is Waterfall: each phase of the project takes place in the sequence. It requires long term planning (extensive and detailed) at the start of the project.

Pros: making designs more straightforward because customers and developers can together agree upon the desired product early on.
Cons: requires lots of time for effective completion, not flexible.

Other PM styles are agile, lean, scrum.
I found this article helpful: https://www.business.com/articles/which-team-member-are-you-identifying-your-project-management-style/

As briefly mentioned above, another project management style is Agile. This unique project management style is centered around being a fast, flexible approach to a project that relies on collaboration and adaptability to get a project done. This style works in continuous project release iterations where each product is a little better than the last. This style has proven to work best in service oriented projects such as coding where each iteration can clean up the code form previous and add features while working out the bugs.

The pros to this service oriented project management style would be the involvement/ collaboration of all team members and the quick course corrections to be applied as needed. The cons to this management style would be its drawbacks when it comes to projects that have strictly defined requirements and scope. When this is not an issue, the lack of focus of scope could also concern stakeholders and executives alike until the first few iterations are complete.

Below is a link that further dives into this unique project management style. https://www.liquidplanner.com/blog/agile-v-waterfall-which-project-management-style-is-right-for-you/

Another style of project management is the Crystal method. With this method there is more importance put in to communication among team members, less emphasis on the actual tasks. The system allows for people to work on their skill-sets and learn how to use them with people of different skill-sets. This method does not seem to be reliable for when having a strict deadline on projects. People are given more flexibility in their work as they put more focus into interaction among the team. The method seems useful in exploring people’s creativity. The method is color-coded according to how much risk the project may have on human life. I personally feel that the method is not useful when doing actual projects, since people will not be as obligated to
finish the project at hand.

https://blog.azendoo.com/top-project-management-methodologies-and-styles/
https://project-management.com/xp-fdd-dsdm-and-crystal-methods-of-agile-development/

Another style of project management is the Crystal method. With this method there is more importance put in to communication among team members, less emphasis on the actual tasks. The system allows for people to work on their skillsets and learn how to use them with people of different skillsets. This method does not seem to be reliable for when having a strict deadline on projects. People are given more flexibility in their work as they put more focus into interaction among the team. The method seems useful in exploring people’s creativity. The method is color-coded accordingly to how much risk the project is to human life. I personally feel that the method is not useful when doing projects in industry, since people will not be as obligated to finish the project at hand. People will be more interested in broadening their talents and interactions with their teammates.

https://blog.azendoo.com/top-project-management-methodologies-and-styles/
https://project-management.com/xp-fdd-dsdm-and-crystal-methods-of-agile-development/

Another style of project management is the Crystal method. With this method there is more importance put in to communication among team members, less emphasis on the actual tasks. The system allows for people to work on their skill-sets and learn how to use them with people of different skill-sets. This method does not seem to be reliable for when having a strict deadline on projects. People are given more flexibility in their work as they put more focus into interaction among the team. The method seems useful in exploring people’s creativity. The method is color-coded accordingly to how much risk the project is to human life. I personally feel that the method is not useful when doing projects in industry, since people will not be as obligated to finish the project at hand. People will be more interested in broadening their talents and interactions with their teammates.

https://blog.azendoo.com/top-project-management-methodologies-and-styles/
https://project-management.com/xp-fdd-dsdm-and-crystal-methods-of-agile-development/

Another style of project management is the Crystal method. With this method there is more importance put in to communication among members, and less emphasis on the actual tasks. The system allows for people to work on their skill-sets and learn how to use them with people of different skill-sets. This method does not seem to be reliable for when having a strict deadline on projects. People are given more flexibility in their work as they put more focus into interaction among the team. The method seems useful in exploring people's creativity. The method is color-coded accordingly to how much risk the project is to human life. I personally feel that the method is not useful when doing projects in industry, since people will not be as obligated to finish the project at hand. People will be more interested in broadening their talents and interactions with their teammates.

References:
https://blog.azendoo.com/top-project-management-methodologies-and-styles/
https://project-management.com/xp-fdd-dsdm-and-crystal-methods-of-agile-development/

Another style of project management is the Crystal method. With this method there is more importance put in to communication among team members, less emphasis on the actual tasks. The system allows for people to work on their skillsets and learn how to use them with people of different skillsets. This method does not seem to be reliable for when having a strict deadline on projects. People are given more flexibility in their work as they put more focus into interaction among the team. The method seems useful in exploring people’s creativity. The method is color-coded accordingly to how much risk the project is to human life. I personally feel that the method is not useful when doing projects in industry, since people will not be as obligated to finish the project at hand. People will be more interested in broadening their talents and interactions with their teammates.

References:
https://blog.azendoo.com/top-project-management-methodologies-and-styles/
https://project-management.com/xp-fdd-dsdm-and-crystal-methods-of-agile-development/

Six Sigma is another management style, and study shows that firms who successfully implement this style is typically deliver better return on investment, return on sales, employment growth, stock growth and value growth.
Pros:
1)Six Sigma strategy places a clear focus on achieving measurable and quantifiable financial returns to the bottom-line of an organization. No Six Sigma project is approved unless the bottom-line impact has been clearly identified and defined.
2)Six Sigma methodology of problem solving integrates the human elements (culture change, customer focus, belt system infrastructure, etc.) and process elements (process management, statistical analysis of process data, measurement system analysis, etc.) of improvement.
3)Six Sigma emphasizes the importance of data and decision making based on facts and data rather than assumptions and hunches! Six Sigma forces people to put measurements in place. Measurement must be considered as a part of the culture change.
4)Six Sigma utilizes the concept of statistical thinking and encourages the application of well-proven statistical tools and techniques for defect reduction through process variability reduction methods.
Cons:
1)The challenge of having quality data available, especially in processes where no data is available to begin with (sometimes this task could take the largest proportion of the project time)
2)The right selection and prioritization of projects is one of the critical success factors of a Six Sigma program. The prioritization of projects in many organizations is still based on pure subjective judgement. Very few powerful tools are available for prioritizing projects and this should be the major thrust for research in the future.
3)Assumption of 1.5 sigma shift for all business processes does not make much sense. This particular issue should be dealt with extra caution as a small shift in sigma could lead to erroneous defect calculations.
4)The relationship between Cost of Poor Quality (COPQ) and Process Sigma Quality Level requires more justification.

I looked at managing styles for my Engineering Ethics class last year and we looked at the "This is Water Commencement Speech by David Foster Wallace"

https://www.youtube.com/watch?v=MZjpihl2pfg

The overly simplified point of the fish story is that the most obvious things in life are often overlooked. However, by adjusting our perspective/mindset and understanding ourselves we can heighten our awareness and empathy in more than one dimension; therefore, facilitating personal and business efficiency and growth. David Wallace’s “This is Water” speech is easy to understand but the philosophy behind the words is a bit difficult to follow. In terms of the engineering industry, people of the administrative level can benefit more from this mindset; therefore make the workplace more efficient. For example, when looking at the manufacturing side of a company, the employer most likely to be in charge would be a Project Manager or someone with a similar title. Now if this person was a stereotypical TV sitcom boss (apathetic, non-compliant etc.), then most likely the people under her/him will not be as efficient as they can be. These types of leaders are like salmon who are trying to swim upstream, who only care about is self-growth and reward. They fail to understand the concept that if the entire team grows together it is a more effective, yet slower, process. Whereas if this same manager was more empathetic as shown in “This is Water”, and understood that the team is built up with other workers (engineers, designers, researchers, laborers), then the efficiency would be far greater than the latter example of a leader in the workplace. I believe that a strong manager is not an employer who just oversees and manages but rather, someone who works alongside his team members. The ability to be humble and listen can be harder when the person in charge has far more experience than those who are less experienced and trying to voice their opinions, but giving these novices the time can go a long way. However, a good manager is one that also is acumen business perspective, where they can bridge the gap between the business and the user’s needs, but also know when one is more important than the other. This philosophy can also be applied to lower-runged workers. Having just enough personal empathy for each other and the right amount of selfishness/drive can benefit the operation a lot more. Perspective is key in the workplace, and they both go hand in hand when it comes to the personal, professional, and intellectual development.

Lean process management is now being used extensively in the healthcare industry to improve efficiency and reduce costs. According to PMI, Lean Management introduced five core concepts:

1) Specify value in the eyes of the customer

2) Identify the value stream and eliminate waste

3) Make value flow at the pull of the customer

4) Involve and empower employees

5) Continuously improve in the pursuit of perfection

These concepts can be applied to any project in the sense of increasing efficiency by reducing waste. We are moving towards a world of automation and every engineer should be familiar with the lean principles.