And cio q & A software project implementation management

Q: first, the origin of a project should be the project application form. When you are working on a project, you propose the project requirement book based on the requirements. And how did you prepare this project requirement book? And let your project be recognized by the general manager and give you strong support in the future. My first question is that at the very beginning of the project, your project application (submitted to the company's management) contains such content. So that the Project Plan can be recognized by the boss and given you strong support in the future?

A: I suggest you solve your most difficult problems first, so that they will be effective. Otherwise, they will become rigid. In reality, it is rare to follow the formal process. We have discussed the formal process, and it is generally difficult for Party A or Party B to ensure mutual cooperation according to the formal process. Therefore, you can only split all the steps in the process and break them apart. You can see the steps in the future.

1. Which business department should this project solve? Lists 1, 2, 3, and 4. If a project is to solve multiple problems in multiple business departments, it is divided by department and then listed by question 1, 2, 3, and 4.

2. What duties, processes, assessment methods, or business processing methods should be changed by the business department.

3. What kind of IT software and hardware product guarantee is required?

4. What are the available it software and hardware on the market? What are the advantages and disadvantages and the price?

5. What are the steps in the launch phase? How long does each step last? What are the responsibilities of the business department and persons involved in each step? What is the total length of time?

Q: How do you consider the members of the project team and their specific division of labor when project 1 is confirmed? If the daily work of this project team is reported?

Answer: 1. The project team should participate in our IT department, the business department involved in solving business problems, and the IT company. Therefore, the following persons are required to know the progress and exceptions and changes of the project.

A. Our boss

B department managers of various business departments

C. Main Business Department staff who participate in daily requirement discussion and launch of the project

Dit owner

EIT project manager

F The IT department of our IT project is responsible for the project manager. If you want to launch multiple subsystems at the same time, you need to set up multiple project managers. However, each subsystem counts as a sub-project and does not hold a conference between each other, unless the business connection problem between several systems is required and a meeting of relevant personnel is held. Do not allow a project manager to launch multiple modules. If there are not so many people in the IT department, it is recommended to launch the subsystem based on the current number of people. Do not have to stick to the system as few people as possible, so it will be very busy and things will not be done well.

2. All of these people should enter the project team. Then, the contacts in each project team should first set up the address book and then send it to you by email ., In the future, if the project team has personnel changes during the project process, update the address book in time and send it to you via email. Each sub-system project team has a separate project team with their own address book. A dedicated folder and email subdirectory are also listed for this project, so that all files and changes in the project process can be quickly sorted out.

3. The IT project manager of the project of the IT department follows the project stage steps mentioned in the first question just answered. List the tasks that should be done this month, and there are implementers. The implementer is a member of the Project address book.

4. Call the persons involved in this month's task to notify the Meeting, including the location, time, content, and final result. Because everyone may have a bunch of things, so in this meeting notification email, let everyone have a read receipt

5. In a real meeting, we will put the real things into practice. There will also be time for each implementer to submit a report. Some people record the meeting minutes and send them to all the members of the project team after the meeting. In addition, each implementer who needs everything should be marked with a red background in the minutes of the meeting. List the pending issues 1, 2, 3, and 4. Add the tasks 1, 2, 3, and 4 to the task list for this month, and then continue to round-robin to solve the task in a single line.

Q: How many stages will a project be divided into? What results and documents do you think must be submitted at each stage? As the IT department director, how do you control the overall progress of the project and revise the progress of the plan?

A: 1. Remember, a project is a sub-system launched. Multiple subsystems require multiple projects. The whole project is a large project, which is macro-oriented and difficult to implement and implement. Therefore, decomposition is strongly required and cannot be confused. Although each subsystem must be closely related, it is likely to be an IT supplier, and IT suppliers may only assign one project manager to cover the entire process (in order to save costs, the launch effect is poor, the project managers of both parties of a project have a lot of work), but do not mix in a large project. Otherwise, it is difficult to have such powerful management, coordination, distribution, supervision, and inspection capabilities.

2. There is a project demand survey link in the implementation phase of each project. It is divided into process sorting, requirement collection, requirement material collection, requirement discussion, and requirement determination.

After the demand research stage is complete, you need to reply to the demand. Should you modify the requirements? Do you still not meet the requirements? Do you still need to make a detour or meet the requirements in the next stage? provide a detailed response to each requirement.

Solve the problem. Which needs to be modified by the IT company. Make the modification list ready for them, set the scheduled time for them, and send these documents to the project team members you are responsible. Let everyone know, not follow. They don't think it's their own business. In each phase, the main participants are different. Only one requirement research step involves IT project managers, business department managers, and business department backbone.

We have encountered one thing in our past experiences in the implementation process. If the system has not been used, we have raised a lot of demands, from very small to very vague, many of them will be used in actual use in the future. The white Development White meeting is true. Therefore, the requirements must focus on the issues listed by each business department during project initiation. If it has nothing to do with those issues, do not join this issue. Many people think that this small demand is easy to implement. At last, we found that the project was very tiring and the project process was nowhere near. Because many things occupy a piece of time, and the last time is gone.

Think about it. A morning is over. Write a plan, write a meeting minutes, and notify the individual to confirm that one afternoon has passed. In a month, there are only 22 working days, and the national public holidays have to be protected. In fact, there are also 20 working days in a month, because there are many national holidays, on average, one year, it only works 20 days a month. To make a plan, you must do it in 20-22 days instead of 30 or 31 days. You cannot make a plan like this.

A project is most afraid of having no project goals, unclear project goals, or too many things a project wants. I often hear a project goal: putting our management to a higher level and improving our work efficiency. Let us know what everyone is doing. This is the most bullshit project goal and there is no way to break down the executable plan.

Therefore, the project goal must be to solve the problems of which department. The problem should be implemented by the Department. Limited people, limited money, and limited time must be able to do limited things.

Q: The Demand Survey is a progress of the project. In this progress, what key documents do you think both parties need to organize or determine?

A: This is a phase of demand research. I have just broken down this stage into several smaller stages: Process sorting, requirement collection, requirement material collection, requirement discussion, and requirement determination. After each small link is completed, there are documents to be left.

Sort the process. Why is this step required? Because it companies may or may not even understand the industry. However, we certainly do not understand our business processes. So you need to know about the entire disk first. For example, to solve the problem of the business department, we must first process the daily business of each person in the business department, the special business at the beginning and end of the day, special business processing at the beginning of one week and one weekend, special business processing at the beginning of January and the end of January, and special business processing at the beginning of the first quarter and the end of the first quarter, special business processing at the beginning of the year and the end of the year all outlines the process. In addition, documents, tables, and reports processed by each person in each business process must be collected. Whether it is paper, electronic excel, or other existing software systems, it must be collected.

The success or failure of a project lies in:

1. problems to be solved by the project objectives

2. Requirements in the project process

3. Project Plan

4. Confirmation, check, and report on the actual implementation of the Project Plan

5. Coordination between project managers and parties

Q: How many stages will the simulation run in? What business behavior does each stage simulate? How do you add documents to the document process? Print format? What is external data? And internal financial account statement? How do you test the association between a menu and a function? How do you sort out the association logic between reports and menus?

A: You cannot solve this problem if there is no process arrangement. Because you are aware of it all by yourself and want to simulate input and verification. Therefore, after you finish the process sorting, everyone in the business department will get the business, input, and report information after the process sorting. You just need to follow this process and input and output for verification. Process sorting refers to taking a picture of your existing business processes, that is, organizing the status quo. After the process is sorted out, it is the real part of demand research. At that time, new demands will be raised. In addition, all these new requirements should be centered around the project establishment goals. If they do not meet the objectives, they cannot be raised, and they will not be promised to do or rectify the problems. After the demand research is completed, adjust the photo of the previous business process as required.

The requirement must be confirmed. Because the meeting was attended by all people, they thought about some ideas. if you asked him again the next day or a week later, he had changed his mind, so he had to confirm his needs. After confirming that these modifications can solve the problem, they are as complicated, easier, or more complex as they are now. Ask the person in the business department to ask the question to confirm. If he does not dare to confirm, he has to hold a meeting and ask his department leaders to join him for confirmation. If the meeting cannot be confirmed, the next confirmation time will be proposed. If the next confirmation time is not available, give up. The next confirmation time is limited to five days. Do not exceed 5 working days. Otherwise, one month is only 20 working days.

The business departments themselves, the IT team, and our team cannot determine how to solve the problem after so many intelligent discussions. What should they do after a week, it means that this problem is unlikely to be solved. Enterprises have many questions, not all of which have answers. Maybe the problem is the biggest boss.

Therefore, closely grasp the project objectives and meet the needs of the problems in the objectives. We often go too fast, and forget to think about why we want to go like this? When there are too many times, we always follow our feelings, ignoring why? Can you change the path? What benefits can this process bring to enterprises? Why not? Can you leave?

What if this document type or report is not available in the original system? Use manual calculation. Indeed, this report is not available in the original Excel table, paper report, or original system. But nothing suddenly exists in isolation. Therefore, it is always associated with the past data, but only from different angles or layers of statistical data. Do not worry about manual computation. In fact, it is not that troublesome, but it is because I feel that I am in trouble, I have not even opened my head, and I have not tried to execute it, so I can't do it. There are a lot of things, even the IT department staff are the same, it is too troublesome, let it companies do it. As a result, the IT company certainly does not want to forget it, just report a sloppy one. When something went wrong, we all regretted being lazy.

The key is to clarify the problems to be solved by the project. 1234. The project plan, responsible person for implementing planned tasks, weekly inspection of project progress, process sorting, requirement discussion and confirmation closely related to the project objectives, and training management.

Q: How to manage training?

Answer: 1. Training Management should be conducted by operators in the business department, operators in the business department, business department managers, and IT department system administrators. This is the main training target.

2. Where are the training courses, textbooks, and teaching plans?

3. Where is the training simulated database?

4. Where is the training environment? Server? Printer? Scanner? Simulation Exercise PC?

5. Who trained the training several times? What training content? When will the training be conducted? Who participated, who did not?

6. What are the test scores of each business operator after the training? Where is the exam questionnaire?

In this way, the management of training can determine whether the business department is able to use new IT systems for their daily business.

Project Initiation, existing process sorting, requirement confirmation, system rectification, system training, simulated operation, and system switching can be viewed as a project in each phase. To manage the entire project, we need to manage these links.

After each step is managed, the entire subsystem is successfully launched. After each sub-system is launched successfully, the entire project is successfully launched. I am afraid that some companies say, Let's start implementing ERP now. If this ERP system has 20 subsystems and 10 core systems, will it be launched at the same time? Is it necessary to enable each function? Which business department should we solve? Some problems have not been solved much. Some problems are acute but cannot be solved by anyone. Therefore, it is good at solving problems that need urgent solutions. There are a lot of problems, it software is not good at solving, it has to solve, certainly no effect or worse effect

Q: How do you complete and effectively switch data during the important process of switching online? In this work, what do you think you must pay attention to as the IT owner? And how long is the switchover cycle most beneficial to the system?

A: 1. I do not agree to import old data to the new system. The data format does not match the data validation. If it is reversed, it disrupts the data input from the new system. I did this, and after a month, I finally abandoned it.

2. I do not agree to launch the product in March and march. At this time, I was very busy. I was busy checking out bills, reporting accounts, transferring accounts, receivables and payables, and reporting at the end of the year. I also thought about preparing for the Spring Festival.

3. I do not agree to launch the product in the middle of the month. Otherwise, I will print the report at the beginning of next month and find the number in the two systems. We recommend that you switch between instances after the 3rd of each month. In this way, the two-day data can be rerecorded in time. The business departments do not want to go online when things on the first and second sides are busy.

4. Do not go online on Friday, Saturday, or Saturday. Because it looks okay, there are many things on Monday, and everything is a problem, and things are even more messy. It is recommended to go online on Wednesday. In this way, things are almost finished on Monday. If there is a problem, it will only take one to two days, and it will take another Saturday to fix it.

It is reasonable to say: 1. the dictionary is ready for verification. 2. The existing business process has been verified. 3. The training is complete. System switching and use of new systems are relatively less risky.

There are also a few notes:

1. Never let it implementers stay with us from process sorting to project launch. We should not do this even if we promise to provide accommodation. One link, one link, and one link, let them do it in their own company or residence. Otherwise, people may get tired, get angry with others, and get down to work. Many things are easy to do and don't want to do. If there is no conflict, then people may get angry or get angry.

2. When discussing a task plan or requirement, you have not reached an agreement with the key contacts or responsible implementers. Do not convene a meeting. Otherwise, you may not be clear about the problem. In the end, it is easier for you to clarify the problem with your mouth. In addition, if a leader decides what to do at the meeting, it would be even worse. Do it or not, knowing that there is something wrong with what the leader says, can't help but do it. Therefore, when you do not know each other or reach an agreement with key contacts or responsible implementers, do not convene a meeting.

 

Star candle net (http://www.xingzhu.net.cn) focus on small and medium-sized enterprise information, provide enterprises with crm oa erp SaaS Supply Chain Management Inventory and other web edition software.