Project suspension

  When a project stumbles into the middle of coding , But I received the news that the customer had suspended the project . ha-ha , At that moment, everyone was stunned , But I was strangely relieved . I really want to rest , It's too much pressure , Plus the demand is done in a mess , Whether the customer can accept or not is a problem . But look back , But I feel pity , Some practices for obtaining requirements in the early stage , Time evaluation and other methods can no longer verify whether it is correct ; Finally, the running performance and performance of the software are unknown . A lot of things seem to have never happened .

  PM A lot of things we do , It's hard for me to accept . For example, most of the requirements are determined by ourselves , Then the customer decides ; We've sorted out a lot of demand issues , But each time only a little raw to the customer , I'm afraid the customer is only busy with simple things , Whatever is important . This leads to a lot of late demand because it is not sent to the customer , Or simply forget , So it is up to us to decide , There are also some cases where the customer didn't take it seriously and we diagnosed their acquiescence . Whether such a system can be used in the end , I really put a big question mark . Of course I'm playing drums myself , Maybe this is an effective method in frustration , But I am waiting for the facts to prove .

  in addition , There is still a problem in this project , The coding phase , It turns out that no one is always responsible for , and PM I don't manage coding at all . Become a few programmers can only talk about doing , And no one dares to decide , The result of comity is that the code is so messy . Different styles are common , Document storage method 、 There is no unified hierarchy , Naming methods and so on are also messy . If the project continues , It will take a lot of time to sort it out later , More likely to bring some invisible BUG. So I personally think this is not desirable .

  Last , When we estimated the time , In fact, it is too optimistic , The coding time is still not enough , It is only enough to make a rough interface , Performance and functions cannot be refined . We should be more pessimistic when estimating the time in the future .

 

Leave a footprint after the project is suspended