Information system project manager thesis preparation 2

The first few articles shared how to prepare for the multiple-choice and case study questions of the project manager (ISPMP), and today I share the last article in the exam preparation guide - how to prepare for the essay part. Many people think that the thesis on item management is difficult. I think the main reason why it is difficult is that in addition to requiring candidates to have solid theoretical knowledge, it is also necessary to combine theory and practice for the test points of the thesis, and based on the theoretical knowledge of the book. Summarize and analyze based on your own project experience, solve practical problems, and put forward suggestions for improvement. Therefore, on the one hand, it can check whether the candidates can memorize the relevant knowledge points of the test points, on the other hand, whether the candidates have rich project practice experience, thesis writing experience (such as whether they can apply what they have learned) Project management experience is used in the thesis), at the same time due to the time factor and word count requirements of the thesis topic (nearly 3000 words in just 2 hours, I think it is a challenge for everyone), and also the writing style of the candidates. , handwriting neatness and other requirements.

Therefore, it is very difficult to write high-quality papers under such conditions. To be honest, it is difficult for people without special training to achieve a score of more than 50 points. Most of the people's scores are around 45 points. (It is estimated that those teachers who can score 45 points see that we have worked hard and feel that it is not easy). Therefore, in order to achieve this "passed" indicator, based on my own experience and the conclusions of other friends, if you want to not participate in the training, (even after participating in the training) you should pay attention to some basic methods and Skills, of course, to emphasize one more point, a premise of my articles is that some friends who read this article have certain experience in project development or management. Of course, students in school can also learn from them. At the same time, some of the content draws on some summaries and key points of many friends. Since there is no way to know who wrote it, I can only use doctrine here.

1. Familiarize yourself with the requirements, writing format and matters needing attention of the thesis test questions

1. Analysis of the test question types Let's

look at the next practical topic:

(Below 2005) The management of project risks has become an important aspect of project management. Every project has risks. It is impossible to completely avoid or eliminate risks, or to enjoy benefits without taking risks. On the other hand, careful analysis and scientific management of project risks can avoid adverse conditions, reduce losses, achieve expected results and achieve project goals.

Please focus on the topic of "project risk management" and discuss from the following three aspects:

1. Briefly describe the information system projects you have participated in the management of (the background of the project, the sponsor, the purpose, the products delivered in the project cycle, etc.), and the The status of the project in terms of risk management.

2 Please briefly describe your understanding of project risk and the basic process of project risk management.

3 Based on your project experience, outline the main risks often faced by information systems projects, their causes and possible countermeasures.

After reading this topic, after analysis, this question is actually divided into the following parts:

introduce the topic project risk management, and briefly introduce some basic properties and meanings of project risk management. ——Corresponding to the main part
of the question, ask questions and analyze problems (combined with your actual project, introduce project risk management and some theoretical applications) -Corresponding to the first and second points of the test questions to
solve problems (through the use of theoretical knowledge, combined with practical case, carry out an introduction, and put forward your own experience and experience) - corresponding to the third point of the test question,
then , when we write the paper, we should also generally follow the logic of this question, and write the paper in a structured way. The correspondence of one point depends on the requirements of the test questions. The test questions for project managers generally have at least two questions for you to choose from. First, we have to choose the test questions that we are best at; then we will outline the structure of the test questions. The paper consists of an abstract and a main body. and Essence, which play a role of summarizing and navigating, the body part generally consists of three main parts (proposing questions, analyzing problems and solving problems), and determine the number of words and time spent in each part (this part is in writing skills will be further introduced in the conference)

2. The paper grading standard

1. The full score of the thesis is 75 points, and the score of the paper can be divided into three grades: excellent, pass and fail. The scores for scoring can be divided into:

· 60 to 75 excellent (equivalent to 80 to 100 on a percentile scale).

· 45 to 59 points pass (equivalent to 60 to 79 points on the 100-point scale).

· 0 to 44 points fail (equivalent to 0 to 59 points on the 100-point scale).

When grading, you can first use the percentage system to score, and then convert it into a full score of 75 points (multiplied by 0.75).

2. It is suggested that when grading, refer to the requirements put forward in the corresponding "answer points" of each test question, and score against the following 5 aspects:

(1) It is suitable for the purpose of the question (30%)

Whether it is a technical paper, theoretical paper or practical paper, all Need to address one or more of the main aspects of the answer points. It can be divided into 3 grades: very suitable, relatively suitable and basically suitable.

(2) The application depth and level (20%)

can be divided into 4 grades: strong, strong, general, and poor independent work ability.

(3) Practical (20%)

can be divided into the following 4 grades;

·There is a lot of practice and in-depth professional level and experience.

·Have good practice and personal experience and experience.

·Have general practice and basic appropriate experience.

·Have preliminary practice and relatively superficial experience.

(4) Expression ability (15%)

can be divided into 3 grades according to whether it is logically clear, rigorous in expression, fluent in writing and well-organized.

(5) Comprehensive ability and analytical ability (15%)

can be divided into three grades: very strong, relatively strong and general.

3. Papers under the following circumstances need to be deducted appropriately:

·The abstract should be controlled within the range of 200-400 words, for those papers that do not write an abstract, the abstract is too brief, or the abstract has no substantive content.

·The handwriting is relatively scribbled, and there are many papers with illegible characters.

·The main text is basically just a dissertation that lists the narration one by one according to the article.

·It is indeed a dissertation that is excessively self-proclaimed or self-proclaimed and exaggerated.

·If there are obvious errors and loopholes in the content, one point will be deducted for each category of errors of the same type.

·Dissertations whose content is only a student or graduate internship project and whose practical application background level is relatively low.

A deduction of 5 to 10 points may be considered.

4. Passing marks cannot be given for papers in one of the following situations:

· Fictional plots, papers with serious untrue or unreliable content.

· Failure to discuss in detail the practical experience of project development, mainly from book knowledge and dissertations based on material excerpts.

· The content and methods discussed are too old, or the standard of the project is relatively low. For example, database design only discusses Foxpro. And there are no distinctive applications; the development is only a stand-alone version (isolated), small scale, and no special application projects.

·The content is irrelevant, or the content is relatively empty, which is basically a dissertation that talks in general terms and has no in-depth experience.

·The main body and abstract are too short in length (for example, the main body is less than 1200 words).

·Articles are not smooth, there are many typos, the organization and thinking are not clear, and the handwriting is too scribbled.

5. Appropriate extra points may be considered in the following situations:

·A relatively outstanding paper with unique insights or in-depth experience.

·A paper with a high opinion, which is indeed in line with the new trends and trends in the development of today's computer application systems, and can be initially realized.

·An excellent paper with informative content, pertinent experience, clear thinking, and very practical.

·The project is very difficult, or the quality of the project is excellent, or the project involves major topics and can be correctly discussed in accordance with the requirements of the test questions.

Consider adding 5 to 10 points.

It can be seen from the specific grading standards that a high proportion (70%) are in line with the meaning of the topic, the depth of application, and the level of practice. Therefore, when we write a paper, we should pay special attention to these areas. Guarantee enough words, and at the same time need to write neatly, it all depends on personal awareness and the level of climbing the grid.

Second, master the skills of essay writing

1. Time arrangement and word count arrangement

5 minutes for selecting test questions
, 10 minutes for listing the outline, 300-400 words
, 15 minutes for writing the abstract, before or after the main text, 500-800 words for
writing the main body for 80 minutes ,1000-1500 words
Check and revise the paper for 10 minutes, 800-1000 words
2. Write abstract

Abstract is the summary and concentration of the paper, which plays the role of outline and guide, and is a concentrated expression of the argument. It is easy for the main body of the paper to be inconsistent with the content of the abstract, and even if you find out later, it is difficult to revise (because the grid is already occupied, don’t keep thinking about using correction fluid, time is precious. of). Therefore, one of my suggestions is to go back and write the abstract after the main body is written, so that the content of the abstract can more conform to the overall structure of the paper. In fact, there are rules to follow when writing abstracts. Let me give you an example (this was written when I was preparing for the exam, of course, it is very general...):

Abstract: I participated in our company's large-scale tap water in March 2011. The company's urban water supply pipe network detection and software development integration project. As the project leader of the project, I am responsible for managing the implementation of this project. The main goal of the project is to complete the detection of the water supply pipe network within the urban area within 8 months. Software development and integration tasks with water supply network geographic information system. Due to the long construction period, many project contents and complex project structure, the project implementation is difficult and risky.

In order to ensure the smooth progress of the project, I have taken targeted measures as a whole, including formulating a complete project management process, strengthening communication, focusing on user needs, controlling the scope of the project, rationally collocating project resources, and assessing risks in a timely manner. Risks were successfully controlled. Through these methods, the interests of all parties were effectively balanced, the scope of the project was controlled, the quality and progress of the project were ensured, and the project was successfully completed.

After the completion of the project acceptance, I found that there is still room for improvement in the project testing, requirements management, and training of internal team members, so I hope to strengthen these aspects in the future to further improve my project management capabilities.

The abstract is basically divided into three paragraphs (proposition, analysis, and problem solving), corresponding to the three main parts of the main text, so it is relatively easy to start after mastering the rules. Of course, it is basically impossible to get a high score for such a strict and structured discussion of the paper. This is like writing an argumentative essay for the Chinese test in high school. Each test is basically around 48 points. It's hard to get high, and it's hard to get low, so let's make do with it, huh, huh.

3. Writing the main

text is the main event. The introduction of the project, theoretical discussion, practical problems and solutions should be carried out one by one here. Corresponding to the main points of the abstract, here I have the following basic ideas based on the summary of some friends and my own experience:

1) (fixed part) Write a project introduction. This part mainly introduces the main content, main characteristics, main role and main work of the project, such as the need to describe the requirements, construction period, investment amount, structure, performance, reliability, etc. in detail. This part of the content has about 800 words to write, and it is a good place to get points, because this part of the content can basically be transplanted into any topic, so it is recommended that this part of the content should be prepared before preparing for the test. It's time to practice writing.

2) Discussion part. This part of the content is the core content, involving the development and discussion of the argument, about 1200 words. Generally, it is discussed in several points in a structured way. You can first briefly introduce the basic theory, commonly used tools and technologies corresponding to a certain management content, and then discuss how to deal with them in combination with the characteristics and difficulties of the project.

4. Summary part

The summary part mainly summarizes and analyzes the application in the process of dealing with the difficulties of the project according to the above body part, including the aspects of success, aspects that can be improved, aspects of failure in the process of project implementation. Generally speaking, when summarizing the project, it is best to show that the project is successful, that is, to talk about feelings, experience and deficiencies while it is successful. This part is about 800 words.

Third, carry out a certain amount of practice

. Even if a person has project experience, and also has a relatively comprehensive theoretical knowledge of software engineering and project management, it is difficult to play in such a time-critical environment if you never write by yourself. Therefore, no matter how much project experience you have before, it is recommended that you write a few articles in half a month before the exam, continuously summarize and refine project materials, further master and apply project management theory, and finally achieve When you take the test on the spot, you can take it easy and feel free to do it. If you are well prepared, basically this test is just practicing writing. If you do not have project experience, or are not rich enough, you can go to the Internet to collect some information (such as the Greek soft test, project manager alliance and other websites to collect information), and at the same time accumulate more.

In addition, there are a few additional suggestions, because it is not allowed to bring a mobile phone during the exam, or the mobile phone cannot be turned on. It is recommended that you bring a watch and drink less water at the same time, and it will be a tragedy if you always go to the toilet. .

Fourth, the past year's test paper title (part) Year
Test question in

the second half of 2011
Quality management, human management in

the first half of 2011
Communication management, cost management

2010 On
the progress management of large-scale projects

On multi-project resource management

2009 On
software project quality management and its application On

large-scale information system project risk management in the

second half
of 2008 On project procurement management On

project communication management in the

first half of 2008 On
the establishment of enterprise-level information system project systems On

project team building and performance appraisal On

project quality management

2007 On
planning and monitoring of large-scale projects On

organizational-level project management performance appraisal

On the importance of review in the process of project quality management



From the table above, we can basically see The test questions are concentrated in the nine major management knowledge areas of project management. Other major project management, information security, performance, etc. have fewer questions, and some test sites have not been covered all the year round. For details, see the test syllabus section below. Therefore, when preparing for the exam, we can prepare for thesis writing in a targeted manner based on the situation of thesis questions in recent years.

Fifth, appendix (syllabus part):

1. Information system project management

· project selection

· feasibility analysis

· project life cycle process management

· project overall, scope, schedule, cost, quality, human resources, communication, risk and procurement Management

·Project Evaluation

·Establishment of Enterprise-level Information System Project Management System

·Analysis of Similarities and Differences between Quality Management in Projects and Enterprise Quality Management2

. Information Security

, Information Security

System, Security Risk Assessment of Information Security System

· Enterprise information security strategy

3. Information System Engineering Supervision

· Supervision method and work flow

· Supervision organization and supervision engineer

· Quality, investment, progress and change control

in supervision · Contract management, information management and safety management

in supervision · Organization and coordination in supervision

4．Informatization strategy and implementation

· The process

of

building

an

informatization

system Differences in the construction process

· E-government construction

· Influence of enterprise's own management maturity on enterprise informatization construction5

. Management of large, complex information system projects and multi-projects ·

Planning process ·

Tracking and control ·

Scope management ·

Resource management

· Collaboration management Indicator Design Performance Improvement