logo

EbookBell.com

Most ebook files are in PDF format, so you can easily read them using various software such as Foxit Reader or directly on the Google Chrome browser.
Some ebook files are released by publishers in other formats such as .awz, .mobi, .epub, .fb2, etc. You may need to install specific software to read these formats on mobile/PC, such as Calibre.

Please read the tutorial at this link:  https://ebookbell.com/faq 


We offer FREE conversion to the popular formats you request; however, this may take some time. Therefore, right after payment, please email us, and we will try to provide the service as quickly as possible.


For some exceptional file formats or broken links (if any), please refrain from opening any disputes. Instead, email us first, and we will try to assist within a maximum of 6 hours.

EbookBell Team

Lean Architecture For Agile Software Development 1st Edition James Coplien

  • SKU: BELL-2347186
Lean Architecture For Agile Software Development 1st Edition James Coplien
$ 31.00 $ 45.00 (-31%)

4.3

98 reviews

Lean Architecture For Agile Software Development 1st Edition James Coplien instant download after payment.

Publisher: John Wiley and Sons
File Extension: PDF
File size: 1.83 MB
Pages: 378
Author: James Coplien, Gertrud Bjørnvig
ISBN: 9780470684207, 0470684208
Language: English
Year: 2010
Edition: 1

Product desciption

Lean Architecture For Agile Software Development 1st Edition James Coplien by James Coplien, Gertrud Bjørnvig 9780470684207, 0470684208 instant download after payment.

More and more Agile projects are seeking architectural roots as they struggle with complexity and scale - and they're seeking lightweight ways to do itStill seeking? In this book the authors help you to find your own pathTaking cues from Lean development, they can help steer your project toward practices with longstanding track recordsUp-front architecture? Sure. You can deliver an architecture as code that compiles and that concretely guides development without bogging it down in a mass of documents and guesses about the implementationDocumentation? Even a whiteboard diagram, or a CRC card, is documentation: the goal isn't to avoid documentation, but to document just the right things in just the right amountProcess? This all works within the frameworks of Scrum, XP, and other Agile approaches

Related Products