50 questions-about Microsoft Project Management

Question 51: What is day-daybuild and how to execute
A:
Maybe you are referring to daily-build. Daily-build is built on a daily basis. Code Build and build a runable version to ensure check-in
The code is correct. We usually perform both the daily-build and the smoke test at the same time, that is, build the check-in code before the end of daily work, and then build
The system performs a simple test on the basic functions to ensure that the generated code has no negative impact on the system functions. Make timely adjustments when problems are detected to ensure daily-build and Smoke Testing
This can be done normally, which is of great benefit for improving the overall code quality.

Question 50: Should developers complete unit test development? Or should they be done by testers?
I personally think it should be done by testers, but there are manyArticleAll said that unit testing should be completed by developers. Which role should MSF be used to complete unit testing development?
A:
Unit tests are carried out by developers themselves, because unit tests usually focus on Some Problems in the implementation process of functions and methods in classes or modules, the specific implementation logic is only developed by the developer
It has been known that testers only focus on whether the system meets user requirements in terms of functions. They do not know how it works. Therefore, testers cannot perform unit tests on the developed classes or modules unless they can
To understand the meaning of each line of code. Therefore, in MSF, unit testing is performed by developers themselves.

Question 49: In the project planning phase, the project master plan and schedule should be completed on the basis of technical verification and functional specification. However, when we face customers, we often see the project master plan and schedule before in-depth communication (before the contract is signed), and even the price based on these, in many cases, the price determines whether a deal can be made. How can this problem be solved? A:
This situation is already common in China, but there will be a big problem in practice. Before in-depth communication, you can only make some estimates based on the project and industry experience, but the estimation results will
There is a large deviation from the actual workload, usually around 25%-400%, or even higher. At this time, the price determined is also very inaccurate. Generally, after the company's senior management determines the price, they sign the contract,
So many estimates will take into account the customer relationship maintenance, future project opportunities, and other impacts. MSF and a2k can help us with project management implementation and architecture design.
Help, but there is nothing to do with the operating principles of such companies.

Question 48: Which role of MSF is responsible for the final signing and approval process of the customer? The final work in chapter 19 mentioned that the product manager is responsible for the final signing and approval of the customer. I think it may be a product management role orProgramManagement roles, because these two roles involve the product manager. A: The release management department is responsible for the deployment and implementation of the project in the later stage and selecting the appropriate release version. The final task of the release management is to smoothly and stably deploy the project results to the production environment, the final signature is recognized by the release management to confirm that the work has been successfully completed. In many cases, roles of program management and release management are merged. Question 47: why are there no P, U, or N letters in the fourth set of charts that contract the team?
A: No matter how the project team is organized, as long as the roles to be merged have no conflicts of interest in the project, they can basically be merged. That is to say, roles with a common interest orientation in the project can be merged.

Question 46: Is program management not only responsible for requirements?
A: Yes. Question 45: What is the most important thing for a project manager? In short, what is the more important skill and experience for the project manager? A: For project managers, skills and experience are equally important. However, skills here are not only technical skills, but also project management skills. Question 44: How does Microsoft perform task estimation? A: experience is very important, but it also integrates a lot of estimation work. Question 43: how to effectively manage bugs? A: You must have an effective Bug management system that provides features such as discovery, reporting, resolution, and logs. At the same time, you must have a dedicated person responsible for Bug Management. Question 42: What role does the Development Management in China belong to in MSF? Program Management? Question 41: Who should update the development documents? A: developers and testers.

Question 40: What are the benefits of setting milestones in a project?
A: You can effectively control the project progress and control the project.

Question 39: Is the function of the system described in the function specification from the user's perspective? A: You must consider both the user and the development process.

Question 38: When can we release a product during product development? What are the criteria for determining the release?
A: In principle, the product release standard is zero bug, but we should not consider the market issue. If the market is "cold", the product release will be meaningless.

Question 37: which method is better for user requirement description? Usecase?
A: Yes.

Question 36: to what extent does the prototype need to be implemented? Is there any instructions? Does Microsoft have the original recommendations?
A: We recommend that you find this on the Microsoft website.

Question 35: How can risks be reflected in the project? Buffertime?
A: risks are everywhere. Only by fully understanding all aspects of the project can we accurately estimate risks.

Question 34: Is there any practical development experience from Kong Wenda? Can I share it with others?
A: Yes, but it can be said without words.

Question 33: under what circumstances do I need to establish a program management team and a development management team?
A: We recommend that you have a program management team under any circumstances.

Question 32: should the test personnel test the project no matter how small the project is?

Question 31: I think both development management and program management belong to the program management role. Is this correct?
A: In fact, many software developers in China share the same situation as you, and their roles are incomplete. However, it is fine to merge them properly.

Question 30: who is responsible for the design of the overall system framework? Program Management role?
A: Yes, but it should be done together with other roles.

Question 29: at present, only one program management role and one development management role are involved. This is the combination of roles, but it is too bad to merge only two roles!
A: You only need one role for program management, but not necessarily one person.

Question 28: How many projects require more teams with program management roles to manage?
A: No matter how big the project is, all roles in MSF are required.

Question 27: some specific implementations have developers directly annotate the code, and finally extract all the annotations through the program ..., Is this reasonable?
A: Of course, it is impossible to describe all the details in the document, but it is best to write all the technical details related to end users in the document rather than in the program, I think this is more troublesome?

Question 26: How can I solve this problem when the Code Implementation changes, but the document is not updated? developers are not good at writing documents, and the time is not enough?
A: Yes. Normally, in principle, the development documentation should be updated by the development team. It is useful to train such a person.

Question 25: how to effectively ensure the synchronization of design documents and code?
A: day-daybuild is a good method.

Question 24: is it important for the product prototype to confirm the requirement with the user?
A: Yes. Yes.

Question 23: How do I view the infrastructure in a project?
A: The infrastructure is very important. It includes many aspects, such as software and hardware configuration and deployment scripts and their processes, automatic deployment tools, and deployment check lists, provides troubleshooting and troubleshooting guidelines, including backup, recovery, and rollback.

Question 22: For a development role, the functional points of the system are not the same as those of the Development Block. How can this conversion be realized?

Question 21: how to effectively encourage team members?
A: A passionate vision statement, commendation, phone number, email, and bonus are all acceptable. This is just a suggestion.

Question 20: How do I know the customer's requirements accurately during the project preparation?
A: It is best to go deep into the user's application environment, understand users' complaints, and collect information about what functions the user most wants to implement so that the user's needs can be clearly defined?

Question 19: What is the most important significance of dailybuild during product development?
A: The biggest benefit of day-daybuild is that the project team can grasp the project status in time and locate and correct errors in the first time, in this way, there will be no problems throughout the solution.

Question 18: concerning how to identify and control risks, MSF says that risk assessment can be handed over to relevant owners. For example, technical risks can be assessed by developers, however, many technical personnel hope to use new technologies in the project, but they do not have a good grasp of the technology and cannot reasonably give risks. How can this problem be solved?
A: It is recommended that all roles of MSF have project-related risks because they exist in all stages of the project.

Question 17: Is the design document of the development module designed by developers reasonable?
A: The requirement document should be the responsibility of the program management role, while the technical development document can be the responsibility of the development role.

Question 16: Do developers try to understand the requirements as much as possible, or do they try to block the requirements in design?
A: It is recommended that all roles of MSF define customer requirements, but the main task of the development role is to develop components according to the functional specification.

Question 15: what are the specific methods to avoid risks? How to control it?
A:
The key to a successful development solution is to control the inherent risks of the project. In MSF risk management guidelines, risk management refers to the determination, analysis, and control of project risks through proactive and predictable methods. Risk Management
The goal is to minimize the negative effects (losses) of project risks and increase the positive effects (Benefits) of the project ). Therefore, in terms of understanding and managing risks, an effective set of guidelines can be used to ensure
Balance. I can say for sure, no. Any method can successfully avoid risks if it is used. In order to effectively manage risks, we must fully understand the software, hardware, environment, personnel, and funds designed by the project,

Question 14: What is the basis for building a development role solution?
A: Function Specification.

Question 13: how can we ensure good communication in MSF? Some people do not like to talk to others.
A: You don't have to talk too much. You can use other forms, such as asking him to participate in meetings and sending emails.
Question 12: What should I pay attention to in project management if the organization is a matrix organizational structure? What besides communication?

Question 11: does one account for two projects violate the MSF principle?
A: do not violate the MSF principle.

Question 10: Can a developer develop two projects simultaneously? Does it violate MSF? What are the main problems? Because his work is not full in a project.
A: although this is not recommended, it is barely possible for developers to do so. If so, I think it can be considered, but we need to consider the efficiency of one person.

Question 9: What are the most important qualities required by the project manager?
A: I think the project manager's skills account for 80% of experience and theory, and the technology accounts for 20%.

Question 8: I am responsible for the maintenance project. I often need to communicate with the product manager in Japan about the working hours and schedule. How can I accurately estimate the working hours? Is there any template for reference?
A: It is really a headache to estimate the working hours. This requires us to clarify the project objectives, develop detailed functional specifications, and use the officeproject.

Question 7: What should we do if customers always think they can't do anything but don't want to do it?
A: Then we need to know that it is not impossible for them to do it. It is just a matter of time, so the project will be delayed indefinitely, so we need to develop a release version.

Question 6: When I submit the software to the customer, I always need to modify it repeatedly. What should I do?
A: This is a problem that has been encountered in many projects. Therefore, the basic principles of MSF include "Active Response.

Question 5: how to make the project complete delivery on time?
Answer: 21 is too representative. To ensure that projects are delivered on time, you must pay attention to many issues. Simply put, you must strictly follow the various suggestions of MSF and ensure communication.

Question 4: Can I save one of the user requirement specification and Software specification?
A: The user requirement specification can be combined with the software specification, but cannot be omitted.

Question 3: Why should the design results be included in the software specification? A: Because your function specification will also be used as a standard to confirm with the customer whether the target is completed after the project is completed, the design results should be included.

Question 2: Can I check whether the test role can be combined with the development role?

Question 1: In the project manager's work description (SOW), what key components should be included in the work description of each stage?

A: It should include at least two models and three standards in MSF, namely, the team model, process model, project management standards, risk management standards, and readiness management standards, but it will also be adjusted according to different projects.