To the end of the year, it is time to write the year-end summary.
A short summary of the following:
In the first half of 2016, very busy. Life, waiting for my pregnant wife (painful and happy), at work, every day to prepare the product demo (has been unable to spit groove).
In the second half of 2016, Lezizi. In my life, my son was born in August and is very handsome (with me); At work, a new version of the system was updated for the Australian customer (one of the most tired).
Thin way to:
Life, this year is a very happy year, of course, because of my son, not much to say, I stole the music.
Work, this year is a lot of harvest (pain in the growth).
In the first half of this year I had a very happy thing (the boss knew to cut me), and did more than two years of product stop (here all dev applause). Really upset every night and night to prepare the demo, in exchange for the result is: very good, but, sorry, we do not need!
This project can be said to be a failure, my post-mortem personal summary:
- Product positioning, the individual feel that product positioning is a failure, the beginning is doomed to failure. The following is purely personal yy, management ideas I can't guess. It is said that our high-level after countless days and nights, countless meetings before deciding to do this product. But I personally feel that it is entirely because we want to give the client's project (very large and complex, did a small 10 years) privatization. The key is what makes our senior high-level confident can put this complex, trouble and cut for a narrow industry field system to sell it??
- Product design and implementation, why don't you go to heaven? In the beginning of the six months, we are busy, but feel very substantial, because constantly beaten chicken blood and constantly to the team to play chicken blood. However, the personal feeling behind the development is becoming more and more outrageous.
- The project continues to expand, bringing in all the things that can be made in the previous project. I am still wondering, have not opened, the shop is open so big, really willing. This is also my most annoying place, each time to prepare a demo, to deploy n applications, but also for the N application mock a set of demo data. When the market is not clear, on the chatty of things, really have confidence! Indeed is the idea of development.
- Changing the change, the function of everyone is acceptable, but incomplete statistics, each module of the project UI has been redesigned to achieve more than 5 times. I was wondering, no customer, we ourselves old toss ourselves have what meaning? It's a waste of our money, but I'm not the boss.
- Too tangled in the details, said the good point is serious, but we do not have customers, are their own in that yy, tangled what? Often a bunch of soy sauce, a meeting on a half-day, the more the more thin, the more fine function more. And that time is not as good as the daily use of the function to do simple.
- The whole thing is a lot of platform stuff in the project (ESB, ID server,bps ...). ), the results are only for use, and then the egg, but also to make the project explosion complex, deployment and server requirements are several times higher.
- Developer configuration, kindness tired, good sad. In addition to the management of the soy sauce, the project team started with me and another small partner (working two years), with a job for a year's sister, and 10 students just graduated/internship three months of new people.
For this project, my personal summary is: Product positioning failure (5 stars); over design (5 stars);
When this project was shut down, it just started the Australian client project. According to the previous experience of giving them a newer version, I think this is easy and easy. However, the fact is that I am most tired of the first time.
A summary of the following:
- As a project planner, I was a bit dismissive and casual, many things did not plan well in advance; as a development Leader, I did not check the development code. Results in the late stage of the project a bunch of problems should not appear, self-face.
- For some of the less well-known team expectations are too high, the result is the most problematic of these members.
In the second month of 2016, I was transferred to another project group (the end of the previous one, which would not leave me idle).
My predecessor, TL, has done well, and the customer's running-in period is almost over, at present I just install the routine to be able to.
Look forward to the work behind ...
2016 year-end summary
