6 questions to be clarified in project development and management

1. Are the project requirements [including demand changes] and requirements module quotations clear?

2. Is the system framework, source code management, and document management clear?

3. Are the quality requirements, bugs, and exceptions of the project clearly handled?

4. Is the project progress clearly tracked?

5. Are the tasks of each member clear?

6. Is the communication between superiors and subordinates, customers, and peers clear?

Summary

Common project processes include: Marketing-receiving customized projects-requirement analysis and determination modules-document preparation andCodeWriting-ProgramTest and adjustment-acceptance delivery training use acceptance feedback for post-maintenance-the project has come to an end.

1. [demand stage] are the project requirements clear?

2. Deployment environment: This is very important. Only by clarifying the customer's deployment environment can we develop it well.
4. Requirements milestones: they are generally divided into several milestones, such as a phase, phase II, or a specific process of several key processes.
6. Classify requirements: Important, General, and secondary requirements. This may occur during different cycles of the project.
8. Whether the image has been drawnFlowchart,Use case diagram, object relationship diagram, prototype demoAnd so on.
10. Whether or not to refine the requirements, that is, to break down the requirements.
12. Whether or not to deal with demand changes, how to interact with the Task Plan and arrangement, and always implement perfect control over the plan, fully reflected in the report, rather than verbal, this requires a system, record requirement change history.
14. This process is very important because demand accounts for 40% of projects.
16. Outbound?Prototype DesignAre there any requirements?
18. Requirements should be combined with plans and arrangements.
20. Requirement management and requirement change management system?This is linked to the task schedule, and the system is built on a daily basis.
22. Requirement management should be divided into modules and functional points, which cannot be further refined.
24. First-Do functions, followed by optimization, but the most basic functions should also have the most basic user experience, rather than error unavailability or poor experience.
26. The technical architecture, including hardware and software, is sufficient to clarify the requirements.
28. Only when the requirements are clear can we find the right person to do the right thing.
30. Are you clear about the requirements that have been fulfilled, those that have not been determined, those that have changed, and those that have not been done?

2.[Demand phase]Source codeIs the management clear?

1. Use source code system for management?
2. Whether to perform daily build
3. Whether it is a complete source code management, everyone sees it all, not part of it. Some companies do not correctly apply source code management and do everything.
4. Is the download from source code management the most complete and correct system that can run smoothly?
5. The source code has a permission control code.
6. Is there a branch backup for source code management?
7. Can it be completed step by step from our source code to online release?
8. Standardized and unified development, testing, and testing standards
9. Is the database maintained by one person?
10. Is the core code a single person working on a uniform part of the code?

3.[Test phase]Is the project bug clear?

1. How to deal with bugs: find one and never drag it to the next day.
2. Requirement management and Bug management should be connected, corresponding to the requirement Management Module.
3. Check whether the old bugs have been cleared before starting a new program. Try to avoid rework.
4. Is there a clear bug list for tracking, monitoring, and checking?
5. For bugs that cannot be modified for the time being, are there any research and update improvements in the future.
6. There is no online Bug Management System. Not only testers, developers, demanders, and customers can add it, but the permissions displayed may be different.

4.[Development stage]Is the project clearly tracked?

1. Can project requirement content, development schedule, development progress, and tracking and supervision be reflected in a specific place, so that administrators, programmers, and customers can see it at a glance, instead of making the project management plan and progress virtually the same?
2. Project requirements, modules, functions, specific functions, change records, planned time, completion time, owner, and the overall project situation should be clear at a glance.
3. Is the project process clearly formulated and implemented?
4. Is code and functions being traced and monitored?
5. The performance of the project personnel is derived from the task completion, work attitude, and tracking reports.
6. Are there clear project quality, style specifications, code and Development specifications, test requirements and specifications? There is no standard reference. How can we track quality?Design a person in the database, design a person in the style, share a part, preferably one person, the core class library one person

5.[Development stage]Are the tasks of each member clear?

1. Module, the responsibility of Function Points is specific to the person, who is responsible and who is responsible
2. Cross-member development to prevent member changes
3. Prioritize Member issues
4. Do you have technical explanations and knowledge training for members?
5. Is there a record of daily work logs for project members?This work log record should be similar to the Work Plan arrangement, but even so, the project team members should enter at least two or more entries each day.
6. Weekly and monthly work reports are sometimes quite necessary.
7. Indicator Management may not be suitable for us. The efficiency of development per unit time can be obtained by who, when, what functions are completed, the number and time of records. At the same time, we can also calculate the bug rate, which is an indicator to measure the work.
8. Is communication between project members convenient?
9. Is there any member involved in the arrangement and change of the work plan?
10. What is someone doing now, what is previously done, what is to be done later, and how is it done? Are you clear?

6.[Demand development and testing stage]Is the communication clear?

1. The team should communicate with each other on a daily or weekly basis and communicate with each other at any time to reassure the team members.
2. In customer user communication, the customer contact must be unique. The customer pays attention to the feedback but does not fully accept the feedback, guides the user and reports the progress, so that the customer can feel at ease.
3. The superior actively reports the communication, looks at the progress, and raises the problem, it is best to propose its own solution, and strive for resources, so that the boss can feel at ease and at ease.
4. Unified Communication outside the project team, set up a unified contact with other groups, communicate in advance, also need to follow up and check, ensure that there is no error, so that the partner can rest assured, peace of mind.
5. List all problems to be communicated, contacts, communication times, and communication results

Summary

Generally, Ms projects are used. I personally feel that they are not very easy to use. In many cases, they are useless.

My idea is:

The most important thing is to create a chart with confidence. The content of this icon is:

Requirement [module, Function Point, Change Record] --> responsible person [Change Record] --> execution time [plan, complete, change Record] --> completion progress --> whether to review --> bug list --> whether to solve the problem. To achieve this, the entire project management page is clear, which makes it easier.

Of course, you can also generate the corresponding chart based on the person:

View the work status and time progress of the person.

You can also generate reports of people and events based on time.

This wayPeople, events, and timeThere should be six types of icons in a combination. This is my personal idea. If there is a similar project management software, it would be nice.