From: Microsoft Cai Wei
One. Team organization
1. common problem
No one is willing to do test, I can't afford it, so many test staff don't follow the norms, and the project will be able to take the leader, divide it.
2. Microsoft Team Model
Each role
Role Responsibilities Project Manager Writing Functional Specification, Coordinating Bridges Contact User Relations Product Manager Customers, conducting demand analysis User education makes products easy to use the release manager to ensure the product is successfully released
two. Project management
1. common problem
Unable to determine the resources required by the project (Human and Budget) cannot determine the progress of the project cannot control the progress and quality of outsourcing projects.
2. Microsoft Project Management - Multi-Milestonic Process
Each milestone completes some features facilitates team concentration to complete a function of providing multiple opportunities to adapt to demand.
How to complete a milestone
Step 1: Rendeze a consensus
Basic completion of demand research and analysis (product manager is responsible) Determine all roles of large direction and long short-term goals to participate in discussions and truly agree with documents generated by the conclusion:
Common user scenarios: More than 80% of the function Vision: Sword denote the direction of the big direction, and has the role of the incentive team
Step 2: Complete the project plan
Writing a detailed functional specification (responsible for project manager) I want to know all functional processes before programming, and guide users to clearly need all roles to participate in reviewing functional specifications and development planning and schedules (development teams) formulate test plans and schedules (test team) ) Distribution resource (humanity and budget) forms a document generated by project integrated planning and comprehensive schedules: functional standard, development plan, test plan (use case), project comprehensive plan development schedule, test schedule, comprehensive progress table
Step 3: Complete the function
Developers complete their own feature, using version control tools, make programmers Check Out and Check IN, avoid accumulating a large number of code timely integration, timely find problems, testing each testable function, No need to wait for the test case tool, check the functionality and repeated checks to use BMS to use BMS to defect track Record all program problems to resolve the bug's automatic process, follow the integrated schedule, constantly check the schedule:
Version Control Tool VSS Defect Tracking Tool RAID / BMS Test Sample Management Tool
Step 4: Stable and release
Test group comprehensive test function, including the performance and stability development group full fit to solve BUG use BMS
Monitoring quality prediction issuance date expert consultation mechanism:
Deciding which bugs can wait until the next milestone or version to solve the tools that solve a bug use:
Version Control Tool VSS Defect Tracking Tool BMS Test Sample Management Tool
three. Microsoft's development management experience: 100% BUG is the core
1. BUG and common type
The function is not implemented, and the specification is inconsistent. It cannot work: crash, no reaction is not compatible with boundary condition interface, message, prompt is not accurate enough, unfriendly has not completed work as a bug document and help information in the help information is also bug
2. Basic function of RAID / BMS
The complete BUG database The central record and control powerful query function of the BUG database, which effectively tracks the status of the project. All records cannot be deleted. For each record, you can only add a rich report function, provide judgment standard for product issuance
3. Effective information in bug record
Status Leader Problem Type Severe Level Priority Modification Time Registration Time Defect Source Solution Operation Environment Defect Association Annescape Data Defective Details
4. Severity of bug
Dead, data loss, main function group is completely lost, the main function of system suspension, leading to serious problems, or fatal error declarations, less serious, less serious, if the prompt information is less accurate, it is almost no problem. Impact, product and attributes can still be used. If there is a name
5. Trend of activated bugs
Before the code is completed: very few code is completed: grow quickly close to Beta: Dropping close to RC: Running to zero product quality and milestone Signal Signals New bugs and corrected BUG Compare Active Status BUG total
four. Microsoft's day
1. Let's take a look at how every day in the project is spent.
Development test project manager
Note: There is a focus on each stage of the milestone, and we take the "completion function" stage as an example.
What is the day of Microsoft?
Answer: Midnight
why?
Because Daily Build is the core of all work and is automatically started in the middle of the night. Daily Construction Daily Build
Do you know that you use the version number of Windows? DAILY Build's Significance:
The module can be integrated in time to request the programmer to put the latest code into the code library with the script language and compile / link tool to implement the BVT Build Verification Test.
Verify BUILD Blocking bug
Problems discovered in the problem of Build unfinished issues BVT
2. What is the most worried about programmers?
Answer: Because of his code CHECK-IN, it causes Blocking bug.
why?
Because the daily build is the foundation of all the work of everyone: programmers need Build to verify interface testing of other modules requires Build discovery new bug, and verify that the bug has been resolved in the new bund, how to do?
Solve the problem and play patch on today's Build. Developer's business
After experiencing the BUILD, the first thing is to do after the second, what answers do: Open the defect tracking tool, view the BUG specified to you, solve the high-priority bug. Because of the quality of new features.
Next, the developer will ...
From the version control tool, the CHECK OUT code modifies the code (solving the BUG or the new function) to obtain the latest changes in the version tool, in this machine build and unit test, please develop group colleagues as the Code ReviewCheck IN code 3. What is the first thing to test?
Answer: Open RAID / BMS to view the bug that specifies to you, verify the resolved bug.
Next, the tester will ...
Test today in the test case test record new discovered bugs in RAID / BMS
4. Expert consultation
Participants: project manager and development team leader, test team leader evaluated each unresolved bug through RAID / BMS
Decide whether the BUG priority waits until the next milestone or version is solved? Who will solve the actual progress and release time of forecasting items
Defect chart
5. Review the day of Microsoft
Construction: Daily Build Development: Solve Blocking Bugs, Implementation, Check-Out, Code Review, Check-In Test: BVT, use test cases to test project managers / group length: expert consultation
6. Microsoft's practice solves those common problems?
Quality issues
The previously resolved issues occurred again, requiring rework that can not be estimated to publish premature release, bringing quality and maintenance issues to test the problem of testing, or not to measure testers and developers' work procedures The problem is often discovered after the release of document management issues.
Documentation and program is out of breath, documentation has become a description of the program results to see the write document as a burden.
Team coordination problem
The developers have their own war. When they are integrated, they need to be aware of the serious problems in the connection of the module. There is no guarantee that the company's previous version and code are not allowed to meet the user's changes to the old version. The developers have left a big impact on the project. No one knows where the code is, or cannot read
Fives. Steps to improve software management
1. Use RAID / BMS to automate process management 2. Use Test Sample Management Tool 3. Use Document Management Tool 4. Use the version control tool to perform DAILY Build5. Create code standard 6. Create a Code Review mechanism 7. Establish an expert consultation mechanism 8. Establish a team communication mechanism 9. Adjust the team structure as needed
