Like economics, the discipline of software development suffers from a weakness that prevents the resolution of competing theories, in that it is generally impossible to perform controlled experiments. It would take an extremely brave manager to ever try out two competing development theories by having two teams build the same product simultaneously. However, it is possible to borrow a technique from theoretical physics and perform thought experiments. Such an experiment would involve having more than one team develop the same product simultaneously, but using different techniques. That type of experiment is the premise of this novel.
The main character is a recent victim of downsizing who is kidnapped and taken to a formerly communist country where the educational level is high and the costs are low. Once there, he succumbs to his fantasies and agrees to perform the experiment of his dreams. With six products to build and a large staff of developers, he splits them into eighteen groups where each product is being built by three teams simultaneously. Each group of the three then uses a different development method. Throw in impossible deadlines and you have a microcosm of software development.
It would appear that such a premise would guarantee a boring book, but nothing could be further from the truth. The book is entertaining and enduring, as developers will recognize most of their development problems, albeit couched in somewhat unique circumstances. Many of the leading figures in the theory of software development management make cameo appearances, including a certain very rich man. The end result is a true stroke of genius that has somewhat of a surprise ending, but actually quite natural, given the current climate in the computer business.
It is rare when a book about the management of software development is not as dull as baked dirt, and this book is indeed the exception. Not only is it entertaining, but you can even learn some management skills in the process.
每读一个章节,都能够在现实的工作中找到或多或少的影子。 想做好项目管理 -- 或者是更广泛意义的管理工作,都应该去翻翻这本书。
评分这本书的风格不是我所喜欢的,它是一本根据结论虚构案例的书,好像童话,但是故事远不及任何童话精彩。爱思考的人想读这本书,只需要读者个帖子:http://blog.163.com/xingsword@126/blog/static/232081202007123103439794/ 说是不负责任,是因为我只在书店看了一章,十页不到...
评分因为有遇到估算项目进度的问题,找到了这本书。花了一天的时间把这本书给读完了,顺便还记录了一下书摘。 读这本书的时候,仿佛置身于其中。里面的101条法则是值得我们学习的!书中不乏一些搞笑的片段。不知道是因为我笑点低还是怎么的,反正我在读的过程中笑了很多次。希望周...
评分每读一个章节,都能够在现实的工作中找到或多或少的影子。 想做好项目管理 -- 或者是更广泛意义的管理工作,都应该去翻翻这本书。
评分《最后期限》-项目管理重要原则 优质管理的四大要素: 选择正确的人。 为他们分配正确的工作。 保持他们的积极性。 帮助团队凝聚起来并保持团队的凝聚力。 (其他一切都只是"文案"。) 安全和变化 除非感到安全,否则人们就不能去迎接变化。 在...
本以为这是一本讲管理的书,最后才发现是码农的YY片儿
评分本以为这是一本讲管理的书,最后才发现是码农的YY片儿
评分台湾旧书店随手买的,豆瓣竟然有~
评分软件工程课推荐的枕边读物
评分本以为这是一本讲管理的书,最后才发现是码农的YY片儿
本站所有内容均为互联网搜索引擎提供的公开搜索信息,本站不存储任何数据与内容,任何内容与数据均与本站无关,如有需要请联系相关搜索引擎包括但不限于百度,google,bing,sogou 等
© 2025 book.wenda123.org All Rights Reserved. 图书目录大全 版权所有