By Bertrand Meyer
Are you attracted via the guarantees of agile tools yet cast off through the fanaticism of many agile texts? do you want to understand which agile concepts paintings, which of them don't subject a lot, and which of them will damage your tasks? then you definitely desire Agile!: the 1st exhaustive, goal evaluate of agile rules, ideas and tools.
Agile equipment are the most vital advancements in software program during the last many years, but additionally a shocking mixture of the simplest and the worst. in the past each venture and developer needed to deal with the great rules from the undesirable by means of themselves. This e-book spares you the ache. It bargains either an intensive descriptive presentation of agile thoughts and a perceptive research in their advantages and limitations.
Agile! serves first as a primer on agile improvement: one bankruptcy every one introduces agile ideas, roles, managerial practices, technical practices and artifacts. A separate bankruptcy analyzes the 4 significant agile equipment: severe Programming, Lean software program, Scrum and Crystal.
The accompanying serious research explains what you have to hold and discard from agile principles. it really is in accordance with Meyer’s thorough realizing of software program engineering, and his large own adventure of programming and undertaking administration. He highlights the constraints of agile tools in addition to their actually terrific contributions — even these to which their very own authors don't do complete justice.
Three very important chapters precede the middle dialogue of agile principles: an summary, serving as a focus of the total ebook; a dissection of the highbrow units utilized by agile authors; and a assessment of classical software program engineering thoughts, similar to standards research and lifecycle types, which agile equipment criticize.
The ultimate chapters describe the precautions corporation should still take in the course of a transition to agile improvement and current an total evaluate of agile ideas.
This is the 1st booklet to debate agile equipment, past the brouhaha, within the normal context of recent software program engineering. it's a key source for initiatives that are looking to mix the easiest of verified effects and agile ideas.
Read or Download Agile!: The Good, the Hype and the Ugly PDF
Similar project management books
Drawing seriously on examine into the studies of training undertaking and programme managers from throughout inner most and public area corporations, this readable, very credible and innovative exploration of the character of initiatives and programmes will ring a bell with each undertaking practitioner. it's a publication that gives a pragmatic set of rules for constructing artistic and powerful venture gamers, who comprehend the aim of what they're doing, the context during which they're operating, and the folks with whom they should interact.
The fourth version of profitable venture administration covers every thing you must find out about operating effectively in a venture surroundings, together with the way to manage and deal with powerful venture groups. conversation is additionally emphasised, with a spotlight on the best way to rfile and converse venture advancements, either inside of and out of doors of the crew.
The forty two principles of Product administration (2nd version) is a set of product administration knowledge from 40 specialists from all over the world together with Adrienne Tan, Linda Gorchels, Jeff Lash, Marty Cagan, and wealthy Mironov. The participants every one percentage one rule they believe is important to reach product administration from their event with businesses resembling Apple, eBay, Intuit, SAP, and Yahoo!
John Zinkin's new booklet on demanding situations in enforcing company Governance is a great addition for board individuals and senior administration on tips on how to increase company governance within the post-crisis interval. John competently identifies that the majority forums on underperforming businesses have 3 components of failure: an absence of right realizing of the company and its process; a complete loss of appreciation of either the strategic and systemic dangers created by means of new product markets; and a complete failure by means of forums to make sure that the motivation buildings for high administration replicate long term wishes instead of non permanent gains, thereby placing the company's destiny in danger.
- Management by Projects
- Effective Work Breakdown Structures (The Project Management Essential Ibrary Series)
- Managing Projects as Investments: Earned Value to Business Value
- Collaborative project procurement arrangements
- Software extension to the PMBOK guide
Additional resources for Agile!: The Good, the Hype and the Ugly
If verbally communicated requirements were truly superior to written ones, engineering of any kind could discard such old-hat techniques as design specifications and plans, relying instead on frequent interactions between engineers and other stakeholders. After all, our forebears did build pyramids and cathedrals that way. But modern engineering is possible precisely because the build- ? 1 ers of houses, bridges, aircraft, circuits — and software — do not stop at a friendly chat and a handshake, but insist on consigning the specifications on paper and having all sides endorse the result.
The senselessness of the intended lesson should not hide the gems of wisdom that the anecdote contains, even if they are not what the author emphasizes. Let us start with the attempted argument. Its first problem is that it follows a form of logic that appears worryingly often in the software literature (particularly but not exclusively in agile books): proof by anecdote. An anecdote is not a proof; as we saw in the preface, ← “Analysis: all it can prove is that a generalization does not hold.
2 THE TOP SEVEN RHETORICAL TRAPS I tried to imagine the kind of circumstance that might draw one to issue such a definitive indictment of an entire industry. You can find the result in a “postscript” to this chapter. Software engineering faces enough obstacles, obvious to anyone in the industry and to any user of software products, that we do not need to conjure up imaginary scandals. ”, page 30. The Standish episode also reminds us of the dangers of exaggeration — of either kind, aghast at others’ failures or boastful of one’s own triumphs — and of software engineering’s dire need for sound, credible empirical results.