Template download: http://download.csdn.net/detail/kaka1121/9562176
Summary of this week (project owner must fill in, member selected) |
fill out this week's summary, including but not limited to the following:
- A brief summary of the bugs in the team this week;
- In addition to project work, other issues of reporting, such as testing environment, new training, automation and other activities;
- Oneself or the team encounters the question, the perplexity and so on;
- Comments and suggestions;
|
Points |
Work highlights of the week: |
Here is a good place to fill in this week |
Not doing a good job this week: |
Here to fill out the work not done this week, such as project extension, online problems and their summary, etc.; |
Risk Tip: |
Here to fill in the current expected risk; |
Overview |
This week's project overview |
Project Overview next week |
Fill out this week's project overview to pick the 2 to 3 things that matter most or most, in one sentence |
Here to fill out the next week's project overview, pick the most important or most attention to 2 to 3 things, in a sentence to explain |
Work progress |
Matters (Project) |
This week's results (progress) |
Plan for next week |
Problems and thinking |
|
this week to fill in the details of the project progress 1. As far as possible in the written language, Non-verbal, chat (dialogue)-type statements; 2. The description of the progress of each piece of work; (Chinese semicolon) end; 3. Each description is as complete a sentence as possible, describing project progress/objectives, encountering problems (and solutions), and it is easy to see "progress" or "work objectives" rather than a long sentence; 4. To classify the progress of the work as far as possible and to describe the progress of the stages rather than the very specific work; 5. Describe the style as uniform as possible, do not two weeks the description of the same work as if not written by a person; be consistent weekly every week and plan to get a little bit of progress last week; |
Here's a more detailed plan for next week's project, asking for "This week's results" to try to avoid the meaningless description of "iterative x test" |
Here to fill in the issues encountered in this matter and thinking, optional fill |
|
|
|
|
Continuous follow-up matters |
This column is for the selection, there are long-term follow-up responsible matters to write, such as marketing platform agile, new Learning Plan, automated long-term detailed plan, etc., or other have a clear plan of their own or team follow-up matters. |
More Wonderful content: http://www.bianceng.cnhttp://www.bianceng.cn/Programming/project/
First, "Overview" and "Essentials" columns
The "Overview" column is required and the "Essentials" column is filled in according to the actual situation.
Correct writing: First write the following specific work, and then extract the summary, important content to "overview", and then extract more need my attention to the "important" column.
"Overview" of the content is a project or a system in the main results of this week or key issues to deal with progress.
Second, the "Progress of Work" column (including this week's work and plans for next week) several requirements:
1. As far as possible in the written language, Non-verbal, chat (dialogue)-type statements;
2. The description of the progress of each piece of work; (Chinese semicolon) end;
3. Each description is as complete a sentence as possible, describing project progress/objectives, encountering problems (and solutions), and it is easy to see "progress" or "work objectives" rather than a long sentence;
4. To classify the progress of the work as far as possible and to describe the progress of the stages rather than the very specific work;
5. Describe the style as uniform as possible, do not two weeks the description of the same work as if not written by a person; be consistent weekly every week and plan to get a little bit of progress last week;
Give some examples:
"Gateway Big Small Channel separation transformation"-noun, this week carried out this work, but the transformation work when the week progress is what, encounter what problem?
"First and two new bank tests"--nouns, what are the new banks? What is the test progress? Test, complete the test?
"Assist to solve the problems encountered by the technical support access merchant", "customer complaints problem"--daily meaningless, to write, to write a representative of specific issues
"Cashier Configuration Center Development"-nouns, no goals and progress
"Add database connection way information from profile", "Modify the bug in ZK operation, create node without judgment"--too specific
"Travel delays, perfect pre-CDs application preparation, current fundamentals OK, it is worth mentioning the operation of the environment and the process is more complex than expected," the enterprise station is still far from being developed, estimated to be 2015 things "," MSP training because can not book to the conference room, did not "-too colloquial, and only described the problem, No solution or suggestion
"Completed December 1 transaction data, accounting data, inventory between banks, and provide an explanation of the difference"--good example
Third, continuous follow-up matters column
This column is for the selection, there is a long-term follow-up responsible matters to write, such as the agile promotion of marketing platform, or other have a clear plan of their own or team follow-up matters.