Faça download dos Aplicativos de Leitura Kindle Gratuitos e comece a ler eBooks Kindle nos mais populares smartphones, tablets e computadores pessoais. Para enviar o link de download para seu smartphone por SMS, use o formato internacional sem espaços (Código Internacional+DDD+Número. Exemplo: +551199999999)

  • Apple
  • Android
  • Windows Phone
  • Android

Para receber o link de download digite seu celular:

Preço Kindle: R$ 101,72
OU

Essas promoções serão aplicadas a este item:

Algumas promoções podem ser combinadas; outras não são elegíveis. Para detalhes, por favor, acesse os Termos e Condições dessas promoções.

Entregar no seu Kindle ou em outro dispositivo

Entregar no seu Kindle ou em outro dispositivo

Anúncio do aplicativo do Kindle

The Art of Lean Software Development: A Practical and Incremental Approach 1 , eBook Kindle


Ver todos os 2 formatos e edições Ocultar outros formatos e edições
Preço
Novo a partir de Usado a partir de
eBook Kindle
"Tente novamente"
R$ 101,72

Número de páginas: 128 páginas Configuração de fonte: Habilitado Page Flip: Habilitado
Idioma: Inglês

Novidades da Loja Kindle
Novidades da Loja Kindle
eBooks novos para sua biblioteca digital. Veja aqui

Descrições do Produto

Descrição do produto

This succinct book explains how you can apply the practices of Lean software development to dramatically increase productivity and quality. Based on techniques that revolutionized Japanese manufacturing, Lean principles are being applied successfully to product design, engineering, the supply chain, and now software development. With The Art of Lean Software Development, you'll learn how to adopt Lean practices one at a time rather than taking on the entire methodology at once. As you master each practice, you'll see significant, measurable results. With this book, you will:

  • Understand Lean's origins from Japanese industries and how it applies to software development
  • Learn the Lean software development principles and the five most important practices in detail
  • Distinguish between the Lean and Agile methodologies and understand their similarities and differences
  • Determine which Lean principles you should adopt first, and how you can gradually incorporate more of the methodology into your process
  • Review hands-on practices, including descriptions, benefits, trade-offs, and roadblocks
  • Learn how to sell these principles to management

The Art of Lean Software Development is ideal for busy people who want to improve the development process but can't afford the disruption of a sudden and complete transformation. The Lean approach has been yielding dramatic results for decades, and with this book, you can make incremental changes that will produce immediate benefits.

"This book presents Lean practices in a clear and concise manner so readers are motivated to make their software more reliable and less costly to maintain. I recommend it to anyone looking for an easy-to-follow guide to transform how the developer views the process of writing good software."-- Bryan Wells, Boeing Intelligence & Security Sytems Mission System

"If you're new to Lean software development and you're not quite sure where to start, this book will help get your development process going in the right direction, one step at a time."-- John McClenning, software development lead, Aclara

Sobre o Autor

Curt Hibbs has always been slightly obsessed with new technologies and tracking technology trends. But he will tell you that this is simply because he is lazy, always looking for new methods and technologies to make his work easier and more productive. This led to his discovery of Ruby in 2001 (when it was still relatively unknown outside of Japan) and to his founding several highly successful Ruby open source projects.

For most of his professional career, which started in the early 1970's, Curt has been a consultant to well-known companies like Hewlett Packard, Intuit, Corel, WordStar, Charles Schwab, Vivendi Universal, and more. He has also been a principal in several startups. Curt now works as a Senior Software Engineer for The Boeing Company in St. Louis.

Steve Jewett is a software developer with The Boeing Company, where he is involved in the development of network-centric cognitive decision support systems. His software experience started with BASIC and FORTRAN on a DEC PDP 1170 back in high school. The trail from there to the present day includes a litany of languages, a broad spectrum of design strategies and development methodologies, and a bevy of software projects, some of which were actually successful. Over a 20+ year career, he has developed software for automated test equipment, weapon/aircraft integration, embedded systems, desktop applications and web applications. His primary areas of interest are software architecture design and software development methodologies, particularly agile software development and its relationship to lean processes.

Mike Sullivan has over 6 years of experience teaching at the university level, and has spent the last 4 years working with software teams in small companies and large corporations to drive valuable solutions and improve team dynamics. He is currently working in a small research team within a large corporation, implementing Lean techniques to improve the software his team delivers. Mike's interests include golf, Cardinals baseball and teaching.


Detalhes do produto

  • Formato: eBook Kindle
  • Tamanho do arquivo: 3161 KB
  • Número de páginas: 142 páginas
  • Quantidade de dispositivos em que é possível ler este eBook ao mesmo tempo: Ilimitado
  • Editora: O'Reilly Media; Edição: 1 (15 de janeiro de 2009)
  • Vendido por: Amazon Servicos de Varejo do Brasil Ltda
  • Idioma: Inglês
  • ASIN: B0026OR3CQ
  • Leitura de texto: Habilitado
  • X-Ray:
  • Dicas de vocabulário: Não habilitado
  • Configuração de fonte: Habilitado
  • Avaliação média: Seja o primeiro a avaliar este item
  • Lista de mais vendidos da Amazon: #575,214 entre os mais vendidos na Loja Kindle (Conheça os 100 mais vendidos na Loja Kindle)

Avaliação de clientes

Ainda não há avaliações de clientes para este título na Amazon.com.br
5 estrelas
4 estrelas
3 estrelas
2 estrelas
1 estrela

Avaliações mais úteis de consumidores na Amazon.com (beta) (Pode incluir avaliações do Programa de Recompensas para Primeiros Avaliadores)

Amazon.com: 3.6 de 5 estrelas 10 avaliações
Esta avaliação foi considerada útil por 1 de 1 pessoa(s):
4.0 de 5 estrelas Good, brief overview of lean systems development 8 de março de 2009
Por A. Tiwana - Publicada na Amazon.com
Formato: Capa comum Compra verificada
This two-hour read is a brief, 5,000 foot view of lean systems development. The substance of the book is in less than a hundred 1.5 spaced pages. It is to the point and concise, almost to a fault.

The book focuses almost exclusively on four key ideas and two "old-hat" SDLC era ideas that clearly communicate the essence of the lean philosophy:

1. Source code management
2. Automated tests
3. Continuous (unit and system) integration
4. Less code (huh?)
5. Short iterations
6. Customer participation (duh!)

I also found their brief discussion of the origins of lean systems development practices in Toyota's development process for the Prius to be unusually insightful.

Although the book is lacking in-depth details of "how tos," but is strong on substance. In other words, you will not gain working knowledge of nitty gritty details of how to implement lean processes, but you will get a crystal clear idea of the underlying principles behind lean. Which to me is a huge plus because it increases the shelf life of my twenty-five dollar purchase beyond the next toolkit, SCM system, and the next fad. I believe that focusing on the underlying principles rather than implementation details is the authors intent.

With that caveat about what to expect from this thin volume in mind, I highly recommend the book.
Esta avaliação foi considerada útil por 1 de 1 pessoa(s):
3.0 de 5 estrelas quick read 13 de junho de 2013
Por Eric Franchomme - Publicada na Amazon.com
Formato: Capa comum Compra verificada
good info; quick read.
I was expecting more details though, for example tools, process,...
but a good book to start learning about the Lean principles
Esta avaliação foi considerada útil por 1 de 1 pessoa(s):
4.0 de 5 estrelas To the point, precise, and concise 29 de dezembro de 2013
Por Arijit Chakraborti - Publicada na Amazon.com
Formato: Capa comum
The uniqueness of this book is it's size - just about 130 pages. That does not make it short, in fact it makes it concise. The book starts with the four most common problems of software development projects: time overrun, cost overrun, inability to meet the business needs, or killed in the middle. What's fascinating here is that the authors didn't even attempt to establish these are the most common problems. Instead they clearly set the expectation about the profile of the readers at the beginning, thereby saving some valuable pages. Remaining pages of the first chapter were spent in describing the various models of software development, and the basic principles of Lean techniques.

The second chapter focuses on the application of Lean techniques in software development and its comparison with the Agile techniques. By completing the first two chapters, the reader would also gather some useful piece of information on Lean techniques thereby building his/her awareness on this topic. The authors focused on only the topics of Lean that would matter most for the understanding, and did not waste pages (and readers' time) on elaborating how it worked like a charm in manufacturing (like any other Lean proponent would do).

The following six chapters described eight different practices from Lean techniques as applicable in the software development domain:
a) Source code management
b) Automated testing
c) Continuous integration
d) Less code
e) Short iterations
f) Customer participation

As one would understand these are not necessarily new practice in software development, but comes back with a renewed emphasis. Fundamentally, it puts back the focus on improving quality and productivity all through the release cycles. Each of the topics are to the point, and the precisely defined without leaving anything ambiguous. That has improved its readability a lot.

This book is not for someone who is hoping to learn software engineering, agile programming, or lean techniques. One should know at least two of these before starting to read this book. This book essentially bring a fresh perspective into the practices of software development, so that the practitioners can try it out on job quickly. The book has used some codes as examples and gives everybody the freedom to use those as needed. Such a good gesture is also uncommon in the books of computer programming.

I would recommend this a refreshing book to seasoned practitioners of software development - across the roles and ranks.
Esta avaliação foi considerada útil por 7 de 7 pessoa(s):
2.0 de 5 estrelas Too Lean An Intro to Lean 18 de março de 2009
Por James Holmes - Publicada na Amazon.com
Formato: Capa comum
This is a concise work weighing in at around 120 pages. Its point is to give people a 30,000 foot overview of many things relating to Lean software development, and it's absolutely targeted to technical and business decision makers who are trying to learn a bit about how they can benefit from Lean.

The problem with the book's approach is that the authors fly past points so quickly that there's not enough serious discussion of the crucial topics central to Lean. I also think the authors spent the majority of the book covering topics which aren't specific to Lean. I'm all over source control, continuous integration, test driven design/development, etc., but these are fundamentals for many other methodologies or approaches. The authors don't spend enough time hitting hard the concepts of eliminating waste, value stream mapping, tight cycles, etc.

Worse yet, in the authors' attempts to give only high-level coverage of concepts they do a bad job of describing some critical issues. As an example, I screamed, literally, when I found this passage in their section on Reuse Existing Software:

"Software reuse exists in many different forms, each of which affects codebase size differently:

* Copying source code from one component to another reduces coding time and debugging, but it actually increases codebase size."

Dudes. Really. Copy and Paste development is awful for so many reasons. An increase in codebase size is utterly the last issue you should be talking about when discussing why you should never do it. Instead, focus on the impact of copy/paste on code complexity, violation of DRY principles, the loss of clarity, increased dependencies, and the replication of bugs throughout your codebase.

This isn't an awful book, and the authors generally did a good job laying out the material. I also loved that they included a good intro to Kanban. The problem is a lack of focus and a sacrifice of vital information in an attempt to turn an introduction to Lean into some sort of 30 minute infomercial.
Esta avaliação foi considerada útil por 5 de 5 pessoa(s):
3.0 de 5 estrelas Lean development 12 de março de 2009
Por Dwayne Phillips - Publicada na Amazon.com
Formato: Capa comum
I saw this book on the shelf in the local book store. I had read several things by the Poppendiecks on Lean Development; O'Reilly publishes high quality books, and so I bought it. I like the book with a few mild disappointments. First, the book is thin - about 120 pages. That is fine, but the publisher made it thin by using tiny print. Why do they do that? Second, the chapter that taught me the most was the final one. I didn't like waiting to the end to find the best part of the book.

The authors start the book with the Standish Group Chaos study. I didn't think anyone did that any more. The publisher or editor should have removed that section. Then they move into descriptions of Agile methods and Lean methods. They have plenty of good material here. If you are in management and do not recognize these terms, this book is for you. The authors give proper credit to Tom and Mary Poppendieck.

I didn't like their description of the Waterfall or serial model. I have seen that model work quite well in many projects under the right circumstances. A description of how to pick a model depending on the circumstances would have been good here.

The major part of the book (chapters 3-8 of a 9-chapter book) describes the main practices of Lean software development. The authors present the practices in the order they recommend the reader adopt them. The practice and their recommended order of adoption are:

Practice 0: Source code management and scripted builds
Practice 1: Automated testing
Practice 2: Continuous integration
Practice 3: Less code
Practice 4: Short iterations
Practice 5: Customer participation

There is little that is new in this book. Its good points are that, even with the tiny print, it is brief, to the point, and gives the reader a path to follow to work lean practices into an existing organization. If you are unfamiliar with lean or haven't considered it for a while, pick up this book.
click to open popover

Onde está meu pedido?

Frete e devoluções

Precisa de ajuda?