Team building path (6)-work methods

When discussing performance goals for November with the team members a few days ago, they found that some team members had a problem: lack of planning,
I always think that everything is to be done. It's just a step-by-step task.

There are two examples:

1) question: "What are you going to do in November ?"
Answer: "self-test, change bug"
Ask again: "When will it be changed ?"
I replied, "I don't know. The change is complete. There will always be new bugs for me to change ."

2) question: "What are you going to do on the 11th day ?"
Answer: "discuss the requirements with the customer and then implement them. Then show it to him and modify it based on his opinion ."
Q: "Can I set a general work plan in November ?"
"No, how do I know what the customer will ask me to do, and how can I know the workload of this task in advance ?"

==================
If the test case testing framework and the acceptance case have been developed before development, where are the bugs that cannot be changed?
When the software can be accepted and paid back, the bug modification is stopped!

We are not a customer's tool. How can we do what he says? How can customers walk by their noses? How can I
What is the customer's software OEM?

Besides, the work plan and development plan I need are exactly the same. In this year, apart from coding, the formation of a software
It also includes "requirement research, requirement analysis, and test case writing.

I hope that the team members can realize what they are doing, what their goals are, and work out their work plans and work arrangements with a clear mind,
For example, the working method of the second member can look like this:

A. When we have a meeting with the customer to discuss the requirements in a few days, it means that the cycle for us to respond to the new requirements is one month, that is, there are
You can raise any requirements, but if it is not a special case, development will be arranged in the next month's plan.
The development plan for this month has been arranged.
B. After discussing the requirements, make the meeting minutes, sort out their ideas, estimate the workload, and send an email to the customer.
Confirm. The project will be officially started only after confirmation. If the customer does not recognize the account at that time or asks for different ideas, record the email
Use it as evidence.

========================================================== ==============================
Excel (one color) · 2006-11-09