Project prediction conflicts

I am a programmer in an Internet company. Due to the need to develop new products, I am not enough people. I recruited a programmer B, and I joined the artist mm c, it constitutes our development team.

Because the number of products in the company is not enough, the company has not recruited products for another month, so this product has been dragging on, and Jack B have maintained the previous products, solve some bugs.

After a while, the department manager decided not to wait for the new product manager, let the three of us work as project managers and product managers first --> write Requirement documents, design the interface and draw a prototype,

This is the first time that I have worked as a programmer. I thought it would be nice to learn more. Maybe it will be useful in the future. Well, even though we did what we did for the first time in prototype, we should do it well. The prototype has made several versions,

The meeting was also confirmed several times, and the prototype was completed. When the development start to estimate the time, the department manager sent an email saying ** is required for the interface module? I think ** is better. Your sister, what did you do when the prototype was reviewed several times earlier,

After the prototype is finalized, you have to change your sister. The three of us decided not to change it. Then I and programmer B estimated the project time and estimated that it would take about one and a half months to complete the first version of the product. Then programmer B reported to the department manager,

As the office area is an open space, I vaguely heard that the department manager did not agree. I firmly believe that we have been developing for too long, so we have to deal with it in a month. When ape B came back, he said sadly: "The department manager did not agree, saying that we have estimated a long time ",

My day is a month and a half long? So I pulled B and went to the department manager to ask if the project time could be extended to one and a half months. After all, everyone who is doing the program knows that the development time is just right, there will certainly be various problems in the middle, resulting in

After the project is postponed, I think the department manager will understand what it said before. We both went to the department manager with an uneasy mood:

Hi: Well, every one of them will be finished in 20 working days. It must be too tight. (Work in about 20 days in a month)

Ape B: Yes, it's a little tight.

At this time, the department manager turned his face on his face and stretched out in the back chair. Then, his eyes did not leave the screen, nor did he speak.

Hi: You see, it takes a lot of time to load many functions, such as the list (Department Manager: Um). To achieve high efficiency, you cannot load too much data on the list, it can only be added to dozens of entries, and others can be stored in the memory, so that the interface will not be card.

Ape B: No. If you have a lot of functions, you must be refined. Otherwise, you can only cut the functions. Otherwise, a list is directly pulled and displayed, which is of course very simple.

Department Manager: I asked you to finish it on schedule, not to cut corners, understand? (Understand the two words with an accent)

Wipe, this hanging suddenly a fire ah, said: it also needs to have enough time to ensure, isn't it?

Department Manager: Yes. You get off work on time every day. Of course you can't finish it!

Hi: We have to estimate the estimated time. Of course, we have to estimate the normal working time. If the estimated project completion time needs to work late every day, it is the failure of our project's estimated time, right?

Department Manager: No

No one spoke at this moment...

Ben has a bad temper. If he doesn't believe it, he asks: Why?

When the department manager does not speak, he may feel a loss. After half a ring, I said: Just do what I said, one month, and then I will check whether it is very tight based on the daily work intensity.

It is already quite obvious that we will go back to our seats without talking about anything.

MM asked me how the project time was discussed. He said: department managers are not happy and face-to-face, as if they owe him a lot of money.

Your sister-in-law, the time was so loose and it was a waste of time. When the development time was so tight, it was not enough for two weeks. He said this: Obviously, who told you to leave work? Look at others, work is still working overtime, work harder, leave after work is too easy, or not good work.

When should we ask employees to work overtime.

I used to work overtime every night until And, So I smiled at me.

Recently, my parents came to visit me and asked my younger brother to take some time off. I also took half a day off to help my younger brother find a job. Ape B also advocates that work time should be efficient, so it is time to get off work and have a life of its own. The reason is that we didn't work overtime.

I suddenly thought of a colleague who said to me, "Your prototype has been extended for a long time." Your sister, we have worked as a product manager for the first time and designed the product, we don't want to recruit people by ourselves.

I also thought that when I worked overtime, the department manager and a few close employees were saying, "who and who are going off work every day, and my work is not active ". Later, the employee was dismissed due to work mistakes.

Today, the department manager turned his face on his face and suddenly our relationship was far away. It turned out that we didn't work overtime recently. Haha ......

Why can't I finish my work within the working hours? Doesn't it mean that those employees who work overtime are not very efficient, or they are working overtime, not at work.

Leave a message to share your thoughts on overtime.

Anyway, I plan to finish this project first. Later I will talk about it, even if I look for another job, I will have more project experience.