Recent experience in a small and medium Internet company, iterative process summarized.
1. First iteration of the flowchart as follows :( hope you can give some optimization suggestions, learn from each other)
2. Problems encountered and summary
(1) expressly real project background and expectations. PM identify pseudo needs, the demand side of the real clear objectives and expected background. Documentation update and known. UI change notice.
(2) the demand for change and so do the implementation of PRD known.
The demand for change, in fact, not only changed the requirements phase, the project involves the entire process, are likely to change.
Documentation updates and known to measure the cost of development time. Of course, the two can be considered less urgent.
PRD and ensure consistency of UI graphics and text functions btn of. Often, C-side development is inconsistent and, finally, to confirm once again, increase communication and modification costs.
(3) document interaction details must be clear. To tell the truth, the company is not interaction designers, some interactive QA problem is to mention, so often, PM will write clearly some interactive logic to achieve, as far as possible to ensure the consistency of the C-terminus.
R & D phase
(1) to ensure that the daily progress of a task.
Dismantling daily research progress to ensure the end of the day the task successfully. Not the end of timely communication feedback, but this is a project manager to PUSH.
(2) ensure that the FBI time and self-test
to ensure that the front and rear ends of the FBI time to send a clear test before developing self-test.
(3) document interaction details must be clear. To tell the truth, the company is not interaction designers, some interactive QA problem is to mention, so often, PM will write clearly some interactive logic to achieve, as far as possible to ensure the consistency of the C-terminus.
(1) BUG To submit a management tool, the testing process visualization:
a tool for recording the execution of each person, but also through management tools to discover and test the lack of risk. But also as an asset test sediment and output. Typical BUG also serve as a reference for other project basis.
(2) Report BUG be professional, learn to locate BUG, the development of evidence-based investigation BUG:
As for QA, QA report some direct say BUG performance, UI aspects of the problem.
charles, Fidddler capture auxiliary test can locate some of the problems, while enhancing our ability to locate problems in RD there can be very convincing and harvest praise.
Therefore, the newspaper BUG hair CURL or LOG, will improve the efficiency of positioning BUG.
Share a very nice article, how to locate BUG:
http://www.360doc.com/content/17/0627/11/40343770_666897925.shtml
(3) clogging test
Sometimes you do not know who to turn to, or that so and so pay any attention to you, after all you do not have any power to make anyone with you, only you can make to the leadership of the problem of the leadership to come forward to coordinate the work.
There are reasons for blocking test: the process of bug cause, function point is not to develop, test resources are not in place