-What a Computer Scientist Needs to Know-
Upon reading the webpage I believe that being a computer scientist is difficult. I agree with the information given, because not only does a computer scientist need to know basic mathematical knowledge, but they need to understand the grasp of using proofs and getting the grasp of using their minds to distinguish the problems that are given in front of them. Knowing several languages is also beneficial for a student as it increases their chances of being able to expand their work in other fields. Having good grades and graduating from a top university does not always make a student great. Resumes can be as flashy as they could be, but it's the work that student produces that is the real point. Having a strong portfolio with a lot of great projects will more impress people than not having anything at all. Although many classes can be extremely difficult, getting the grasp of most of them and passing can help you speak in the "engineering" language. This could help formulate a conversation on what plans you will need to take to tackle a project with a team.
-Project Management-
Project management is very important in any project. In order for businesses to prosper, they need to be able to disperse the time needed into their team to get the job done at a good time. Using the "scope triangle" is a good method to see exactly what trade-off you will need to get the job done. It distributes the time, cost and quality needed to complete a project. The time factor is the most important, as it with any project that has enough funding and a good team; if you do not have the time to finish, it won't end well for anyone. Making a guideline is also very important. Drawing out graphs that include each step will help a team disperse their time to complete each header as they continue on with the project. Following this can help a member not get sidetracked on what needs to be done as a project leader should be able to layout the steps efficiently to help them. Working on a team that is smaller is always beneficial. Large projects that involve a large number of people are harder and will not always get a project done in time. Communication plays a huge role in these projects. With more people, it makes it harder to establish a basis on where everyone should be and what needs to be done. With every project; milestones needed to be implemented to be able to move on the next phase. This enables the team to have a deadline to know what will be coming in the time span of the project.
