- Capa comum: 200 páginas
- Editora: O′Reilly; Edição: 1 (10 de junho de 2005)
- Idioma: Inglês
- ISBN-10: 0974514047
- ISBN-13: 978-0974514048
- Dimensões do produto: 19 x 2,1 x 23,5 cm
- Peso do produto: 408 g
Ship It! - A Practical Guide to Successful Software Projects (Inglês) Capa Comum – 31 mai 2005
|Novo a partir de||Usado a partir de|
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)
Para receber o link de download digite seu celular:
Todos os dias, novos eBooks com desconto. Vem.
Detalhes do produto
Descrições do Produto
Sobre o Autor
Avaliação de clientes
Avaliações mais úteis de consumidores na Amazon.com
If you and your team already are using source management, doing code reviews, and writing tests that you frequently use (chances are you probably follow most if not all of the best practices in the book) and if you have read more generic time/project management books many of the management tips probably will not be new either. If your development process is not a well oiled automated machine or perhaps struggle with team communication you will find the book very helpful and enjoyable readable.
Despite being familiar with most of the items put forth in the book, I especially enjoyed the trace bullet development chapter. That method of development struck a good balance between planning out the software and completing it in stages concurrently rather than focusing a teams effort only on one interface/module at a time.
While I was familiar with most of the content and practices of the book I would still highly recommend it for both developers and managers (actually anyone who works at a software company could probably benefit from reading it).
The list of critical practices are well defined and each one is simple enough to implement. It makes you feel like maybe you could do it. Most important, it explains why you should do it - in compelling terms so that even if you are skeptical of "continuous integration" or "pair programming" or "unit tests", well, you won't be after you read this book.
"Tracer Bullet" development isn't another methodology, but a way of incrementally developing a project so that the status is more clear to the customer and so that you can quickly turn abstract ideas that the team has into something more concrete to react to. In doing so, you maintain an integrated view of the product you are working on and help people understand their ideas more quickly. It is priceless for any non-trival software. Most of us probably have learned to do this anyway, but now there is a name for it and a guide to understand why we do what we learned through trial and error.
Most of it corroborated the practices we have seen to work. The rest showed where we can make amends for better results. I recommend it wholeheartedly to every project manager, technical architect, and strategic thinker at IT companies.
Had it been one of my first project management books I would have rated it higher.
It's a quick and easy read, good beginner material. It may be a little "lightweight" for some.