bestoffice's Blog

First, sesame big point things need to be reflected
 
 
 in the program. Planned, but sometimes good of course for some suddenly appeared issues, such as user requirements on the front page links to add a blog garden, small a requirement, if applied to plan, then CMMI to demand, change design... If the light change code word May 10 minutes, changing the document to half a day.
Second, every meeting have meeting record. Important meeting of course want to remember, but sometimes temporary, 10 minutes half an hour of meeting seems to have no the necessary
Anyhow I feel CMMI too formalist, too dogmatic, document too much. Large project application CMMI may be better, but to small and medium-sized project is a bit dearly purchased, 8 months of a project if application document this piece, if CMMI may be more than a one month's workload.
Recently I is also watching the people thing ", was watching the second time. It and CMMI focused on two different aspects, CMMI focused on system, management, and one thing is about people, think people are the core of software development, how to improve the environment, improve research to give full play to people culture, the passion, to form gum frozen type team.
Two: I think one thing compared more suitable for general software enterprises. Drain the management concept, abolishing CMMI of trival, useless document (the necessary documentation of course is needed), then application mentioned in the some person thing makes several glue frozen type way, so that should better team.
Above is just a preliminary view, only represent my personal opinion, I believe there are many project management expert right, welcome the discussion.