Ebook Agile and Iterative Development: A Manager's Guide, by Craig Larman
By downloading this soft file publication Agile And Iterative Development: A Manager's Guide, By Craig Larman in the on the internet link download, you remain in the first step right to do. This site really offers you ease of how you can get the finest publication, from best vendor to the new launched e-book. You could find more publications in this site by going to every web link that we provide. One of the collections, Agile And Iterative Development: A Manager's Guide, By Craig Larman is one of the most effective collections to offer. So, the very first you get it, the very first you will get all positive regarding this e-book Agile And Iterative Development: A Manager's Guide, By Craig Larman
Agile and Iterative Development: A Manager's Guide, by Craig Larman
Ebook Agile and Iterative Development: A Manager's Guide, by Craig Larman
Why must choose the headache one if there is very easy? Get the profit by buying guide Agile And Iterative Development: A Manager's Guide, By Craig Larman below. You will certainly obtain various method to make an offer and also obtain the book Agile And Iterative Development: A Manager's Guide, By Craig Larman As understood, nowadays. Soft file of the books Agile And Iterative Development: A Manager's Guide, By Craig Larman end up being popular amongst the users. Are you among them? And right here, we are providing you the new compilation of ours, the Agile And Iterative Development: A Manager's Guide, By Craig Larman.
When obtaining this e-book Agile And Iterative Development: A Manager's Guide, By Craig Larman as recommendation to read, you could obtain not just motivation however additionally new expertise as well as lessons. It has greater than usual advantages to take. What sort of book that you review it will work for you? So, why need to get this book qualified Agile And Iterative Development: A Manager's Guide, By Craig Larman in this write-up? As in web link download, you could obtain the book Agile And Iterative Development: A Manager's Guide, By Craig Larman by on-line.
When obtaining the e-book Agile And Iterative Development: A Manager's Guide, By Craig Larman by on the internet, you can read them wherever you are. Yeah, also you remain in the train, bus, hesitating checklist, or other places, on the internet book Agile And Iterative Development: A Manager's Guide, By Craig Larman could be your good friend. Every single time is a good time to check out. It will improve your understanding, enjoyable, enjoyable, lesson, and also encounter without investing even more money. This is why on the internet publication Agile And Iterative Development: A Manager's Guide, By Craig Larman becomes most wanted.
Be the first which are reviewing this Agile And Iterative Development: A Manager's Guide, By Craig Larman Based upon some factors, reading this publication will supply even more benefits. Even you require to review it step by action, page by page, you can complete it whenever and any place you have time. As soon as more, this on the internet e-book Agile And Iterative Development: A Manager's Guide, By Craig Larman will certainly provide you simple of reviewing time and also task. It likewise provides the experience that is affordable to get to as well as get significantly for better life.
Using statistical research and case studies, the author presents the most convincing case ever made for iterative development. He offers a concise summary of the key ideas that drive all agile and iterative processes, with the details of four noteworthy iterative methods: Scrum, XP, RUP, and Evo.
- Sales Rank: #210611 in Books
- Published on: 2003-08-21
- Released on: 2003-08-11
- Original language: English
- Number of items: 1
- Dimensions: 8.90" h x .90" w x 7.00" l, 1.49 pounds
- Binding: Paperback
- 368 pages
From the Back Cover
Agile/iterative methods: From business case to successful implementation
This is the definitive guide for managers and students to agile and iterative development methods: what they are, how they work, how to implement them—and why you should.
Using statistically significant research and large-scale case studies, noted methods expert Craig Larman presents the most convincing case ever made for iterative development. Larman offers a concise, information-packed summary of the key ideas that drive all agile and iterative processes, with the details of four noteworthy iterative methods: Scrum, XP, RUP, and Evo. Coverage includes:
- Compelling evidence that iterative methods reduce project risk
- Frequently asked questions
- Agile and iterative values and practices
- Dozens of useful iterative and agile practice tips
- New management skills for agile/iterative project leaders
- Key practices of Scrum, XP, RUP, and Evo
Whether you're an IT executive, project manager, student of software engineering, or developer, Craig Larman will help you understand the promise of agile/iterative development, sell it throughout your organizationaeand transform the promise into reality.
About the Author
CRAIG LARMAN is known throughout the international software community as an expert and passionate advocate for object-oriented technologies and development, and iterative and agile development methods. He serves as Chief Scientist at Valtech, a global consulting and skills transfer company, where he has led the adoption of iterative and agile methods. Larman also authored Applying UML and Patterns, the world's best-selling text on object-oriented analysis and design, and iterative development.
Excerpt. � Reprinted by permission. All rights reserved.
Introduction Overview
- What's in this book?
- Predictable versus new product development.
What value will you get from studying this book, an introduction to iterative and agile methods?
First, you will know the key practices of four noteworthy methods, Scrum, Extreme Programming (XP), the Unified Process (UP), and Evo (one of the original iterative methods). This is a "Cliffs Notes" summary, each chapter has something useful to you as a manager, developer, or student of development methods.
Second, your learning curve will be shortened, as this is a distilled learning aid. The four method chapters have the same structure, to speed comprehension and compare-contrast. There's a FAQ chapter, a "tips" chapter of common practices, and plenty of margin pointers to related pages—paper hyperlinks.
Third, you will know motivation and evidence. Some organizations accept the value of iterative development, but others are still reluctant. If you need to make a case for an iterative project experiment, you will find in this book the key reasons, research, examples of large projects, standards-body acceptance, a business case, and promotion by well-known thought leaders through the decades. The research and history sections are also of value to students of software engineering methods.
Note that agile methods are a subset of iterative methods; this book covers both types.The chapters may be read in any order; the big picture is this:
1. Introduction, and predictable vs. inventive development.
2. Basic iterative and evolutionary method practices.
3. Summary of agile principles and methods.
4. An agile project story to pull some ideas together.5-6. Motivation and evidence chapters for iterative and agile methods; useful for some.
7-10. Four method summaries on Scrum, XP, UP, and Evo. Note: practices can be mixed.
11. A tips chapter that expands on some of the method practices, plus others.
12. A frequently asked questions (FAQ) chapter.
Finally, people trump process. Every process book should probably include this standard disclaimer:
Process is only a second-order effect. The unique people, their feelings, qualities, and communication are more influential.Some problems are just hard, some people are just difficult. These methods are not salvation. Software Is New Product DevelopmentConsider building mobile phones on an assembly line: It is possible to unambiguously define the specifications and construction steps. After building some phones and measuring things, it is possible to reliably estimate and schedule the building of future phones.
A different problem: Build a custom house. The owner wants to use new environmentally friendly materials and methods, but isn't exactly sure what they want, and is going to change or clarify their decisions as they see the house, costs, and weeks unfold.
At one end of the spectrum, such as manufacturing phones, there are problems with low degrees of novelty or change, and high rates of repeated identical or near-identical creation—mass manufacturing or predictable manufacturing.
At the other end, there are problems with high degrees of novelty, creativity, and change, and no previous identical cases from which to derive estimates or schedules. This is the realm of new product development or inventive projects.
The development process, management values, planning and estimation models appropriately associated with these two domains are different (Table 1.1).
Of course, the point is,
Most software is not a predictable or mass manufacturing problem. Software development is new product development.Plus, many projects use new and buggy technologies that exacerbate the degree of novelty and unpredictability. Note also it is a new product for the inexperienced even if it has been done before.
Since predictable manufacturing is the wrong paradigm for software, practices and values rooted in it are not helpful.
This mismatch lies at the heart of many of the challenges associated with traditional approaches to running a software project.A "waterfall" lifecycle, big up-front specifications, estimates, and speculative plans applicable to predictable manufacturing have been misapplied to software projects, a domain of inventive, high-change, high-novelty work.Factors CP86 preventing reliable up-front specifications include:
- The clients or users are not sure what they want.
- They have difficulty stating all they want and know.
- Many details of what they want will only be revealed during development.
- The details are overwhelmingly complex for people.
- As they see the product develop, they change their minds.
- External forces (such as a competitor's product or service) lead to changes or enhancements in requests.
This deep appreciation—that building software is complex, new product development with high change rates, and not predictable manufacturing—is at the heart of the motivation for agile and iterative methods.
Certainly, another driving force is the desire to compete and win. Iterative and agile methods foster flexibility and maneuverability—a competitive advantage. In Agile Competitors and Virtual Organizations GNP97 the authors examine the limitations of the mass manufacturing model and the need for agility:
Agility ... is about succeeding and about winning: about succeeding in emerging competitive arenas, and about winning profits, market share, and customers in the very center of the competitive storms many companies now fear. What's Next?The next two chapters summarize basic practices and ideas of iterative, evolutionary, and agile methods. After that, a story chapter illustrates these practices with a concrete scenario.
Web ResourcesRelated book or journal article suggestions are given in their respective chapters. Web resource suggestions include:
Broad Link or Article Siteswww.agilealliance.com — Collects many articles specifically related to agile methods, plus links.
www.cetus-links.org — The Cetus Links site has specialized for years in object technology (OT). Under "OO Project Management—OOA/D Methods" it has many links to iterative and agile methods, even though they are not directly related to OT.
www.bradapp.net — Brad Appleton maintains a large collection of links on software engineering, including iterative methods.
www.iturls.com — The Chinese front page links to an English version, with a search engine referencing iterative and agile articles.
More Specific Sitesc2.com/cgi/wiki?FindPage — This important, vast Wiki site was the home ground where many of the agile leaders (and design pattern leaders) held their original discussions on XP and other agile methods.
www.extremeprogramming.org — Don Wells' (an early XP leader) introduction to XP.
www.xprogramming.com — Ron Jeffries' (an early XP leader) introduction to XP.
www.agilemodeling.com — Scott Ambler's site contains many articles related to agile modeling practices.
sunset.usc.edu — Associated with the work of Dr. Barry Boehm, a long-time researcher into iterative (e.g., Spiral) methods. Articles related to iterative methods.
www.cutter.com — Cutter's site has an Agile Project Management specialty area.
www.martinfowler.com — Martin Fowler is an early agile methods thought leader (XP method). Articles and links.
www.jimhighsmith.com — Jim Highsmith is an early agile methods thought leader (Adaptive Software Development method). Articles and links.
alistair.cockburn.us — Alistair Cockburn is an early agile methods thought leader (Crystal methods). Articles and links.
www.controlchaos.com — Ken Schwaber is an early agile methods thought leader (Scrum method). Articles and links.
jeffsutherland.com — Jeff Sutherland is an early agile methods thought leader (Scrum method). Articles and links.
www.gilb.com — Tom Gilb is one of the very earliest iterative and evolutionary thought leaders (Evo method). Articles and links.
www.craiglarman.com — My site. Articles and links.
www.objectmentor.com — Company led by Robert C. Martin, an early agile thought leader (XP related). Articles and links.
www.nebulon.com — Company led by Jeff De Luca, an early agile thought leader (Feature-Driven Development method). Articles and links.
www.dsdm.org — Official site for the DSDM method.
www.rational.com — Official site for the Rational Unified Process (RUP) iterative method.
name.case.unibz.it — Network for Agile Methodologies Experience (NAME). A European site that describes research into agile methods, and with links to other sites.Most helpful customer reviews
12 of 12 people found the following review helpful.
Adios Waterfall
By Wintersmith
Yes, indeed, Finally. Abundant proof in one book that the traditional waterfall approach is a terrible way to manage software projects, and is therefore slowly being displaced by agile and iterative approaches. Larman does a devastatingly thorough job of debunking waterfall once and for all.
The book cogently and painstakingly explains how several of waterfall's practices have been conclusively linked to project failures, and how, on the other hand, the practices of Agile and iterative methods like Scrum and XP reduce project risk. Larman summarizes research findings encompassing thousands of projects, and quotes the supporting opinions of standards bodies and industry thought-leaders. The net effect is compelling, to say the least.
If you are an Agile skeptic, this book may rattle your conviction. If you are fence-sitter, it may convince you. And if you already have Agile fire in the belly, then certainly this book will stoke that fire. After reading it, I am left wondering how intelligent, experienced software development management can justify the continued use of a process that has wasted so much money and caused so much pain.
2 of 3 people found the following review helpful.
Excellent survey of iterative and incremental development (IID) methodologies
By Erik Gfesser
This work by Larman shares some commonalities with Balancing Agility and Discipline, a work by Boehm and Turner (see my review for that book) in which a wide range of methodologies are compared side-by-side to determine the best fit for teams. However, rather than serving as a guide to determine best fit from a wide assortment of methodologies, Larman's work is limited to a discussion of Scrum, XP, Unified Process (i.e. RUP/UP), and Evo, within the broader context of what the author categories as iterative and incremental development (IID). In my opinion, this book is probably the best organized text on this subject currently available in the marketplace. Although the subtitle for this work categorizes itself as a manager's guide, the content Larman has included here will prove beneficial for anyone involved in software development. And this is the case even if one does not read the four methodology-specific chapters. After a thorough explanation of iterative and evolutionary development, the author discusses its relationship to agile development and the motivation behind adopting such methodologies. The subsequent chapter on the evidence behind the effectiveness of IID is the most concise listing of research findings I have come across. While this chapter begins with a warning that "exhaustive data can make for exhaustive reading" and that it is "probably best spot-read as a reference", at only about 30 pages in length it is well recommended. While many in technology recognize the benefits of IID and have used the ideas brought to the table by various IID methodologies to some extent, the author reminds the reader that not only do many technology shops simply remain paralyzed by waterfall methods that view software as a predictive process, but that IID has been around for decades. David L. Parnas, a software engineering pioneer who developed the concept of module design, is quoted by Larman as follows. "Q: What are the most exciting, promising software engineering ideas or techniques on the horizon? A: I don't think that the most promising ideas are on the horizon. They are already here and have been for years, but are not being used properly." I found the following sections within the specific methodology discussions to be especially beneficial: common mistakes and misunderstandings (or how to fail with a particular methodology), signs that one has not understood a particular methodology, sample projects, process mixtures, and adoption strategies. In addition, the reader might be interested in knowing that the last chapter consists solely of questions and answers summarizing many of the main discussions presented elsewhere in the preceding eleven chapters, serving as a quick reference by pointing to specific portions of the text where ideas are elaborated upon.
2 of 2 people found the following review helpful.
Excellent overview to the topic
By Amazon Customer
I found this to be an excellent review to the topic of agile development. It methodically covers Scrum, XP, UP and Evo, and unlike other computer books, provides detailed references and a bibliography, so you can see how the author got to his conclusions.
Agile and Iterative Development: A Manager's Guide, by Craig Larman PDF
Agile and Iterative Development: A Manager's Guide, by Craig Larman EPub
Agile and Iterative Development: A Manager's Guide, by Craig Larman Doc
Agile and Iterative Development: A Manager's Guide, by Craig Larman iBooks
Agile and Iterative Development: A Manager's Guide, by Craig Larman rtf
Agile and Iterative Development: A Manager's Guide, by Craig Larman Mobipocket
Agile and Iterative Development: A Manager's Guide, by Craig Larman Kindle
Tidak ada komentar:
Posting Komentar