Wed Jun 06 11:59:50 HKT 2018
Linus share about project management, most importance is people, and also discuss about tools, how to collabrate people and how to delegate - http://h30565.www3.hp.com[..]Software-Development-Management/ba-p/440
Only the programmer who is going to write the code can schedule it. Any system where management writes a schedule and hands it off to programmers is doomed to fail. Only the programmer who is going to do the work can figure out what steps they will need to take to implement that feature. - http://www.joelonsoftware.com/articles/fog0000000245.html
Never, ever let managers tell programmers to reduce an estimate. Many rookie software managers think that they can "motivate" their programmers to work faster by giving them nice, "tight" (unrealistically short) schedules. I think this kind of motivation is brain-dead. - http://www.joelonsoftware.com/articles/fog0000000245.html
Micromanagement or Macromanagement? http://boncey.org/2006_10_29_how_to_mentor_programmers
But, unfortunately, as a general rule, Project Managers have no training. Even if they do have training in the form of an MBA, MBA education is impractical and useless; the academic community has completely failed us in this respect. Furthermore, Project Managers are more often based on personal friendships and company politics; they are rarely based on management skill.
And, finally, most managers do not acknowledge that management is a skill that they must study and learn so they don't study or learn it.
An explanation of agile, I think it is more about project management - http://blog.objectmentor.com/articles/2007/04/23/short-reach
Some common problem of software project management - http://ajaxwidgets.com[..]thomas/9_reasons_why_software_project.bb
Brief description of thoughtworks codejam - http://blog.nona.name/200804274.html
Listen first. Measure later. http://digerati-illuminatus.blogspot.com[..]gspot.com/2008/05/measure-or-listen.html
Paper of burn up and burn down - http://alistair.cockburn.us/Earned-value+and+burn+charts Per my understanding, we can say burn down is push by management where DEV work as task consumer and completing per define tasks within limited time; where burn up work in the other way round.
Why rewrite usually bad - http://www.jroller.com[..]astianKuebeck/entry/why_version_2_0_will
Why need to manage user/client - http://dreamhead.blogbus.com/logs/48408290.html
The blog list several software projects fail case study - http://www.codinghorror.com/blog/archives/000588.html
The law of late project - http://www.commonsense4commonpeople.net[..]et/2009/11/the-law-of-late-projects.html
Friendship, what make one big team working - http://blog.objectmentor.com/articles/2010/04/26/pair-management
On an Agile Team, a person is removed from the team by assigning them work. - http://www.agileadvice.com[..]e-between-agile-teams-and-project-teamd/
Some say an method "Impact Mapping" is very useful - http://mysoftwarequality.wordpress.com[..]com/2014/07/15/complexity-is-the-excuse/
Transfer project to products - https://www.infoq.com/articles/transform-projects-products
Frequent planning - https://www.jrothman.com[..]can-lead-to-short-and-frequent-planning/
(google search) (amazon search)