Win Free Copies of New Book on Continuous Delivery and DevOps

by on December 20, 2012 · 22 comments

CD and Devops

We’ve teamed up with Packt Publishing to organize a giveaway of their new book “Continuous Delivery and DevOps: A Quickstart Guide” as a holiday gift to you our readers!

Four lucky winners stand a chance to win copies of this new book. Keep reading to find out how you can be one of them.

Continuous Delivery and DevOps

As the author puts it, the book is a “collection of suggestions based upon experience and observations.” It’s all about:

  • Real world examples of how to go about implementing continuous delivery and DevOps
  • Learning how continuous delivery and DevOps work together with agile tools
  • An honest and open guide to consistently and quickly shipping quality software

Read more about this book and download the free Sample Chapter

How to Enter?

All you need to do is head over to the Continuous Delivery and DevOps book page and look through the product description of the book. Drop a line via the comments below this post to let us know what interests you the most about this book. It’s that simple.

Winners from the U.S. and Europe can either choose a physical copy of the book or the eBook. Users from other locales are limited to the eBook only.

Deadline

The contest will close December 31, 2012 at midnight Pacific Time (PST). Winners will be contacted by email, so be sure to use your real email address when you comment!

Don’t lose any time and head over to the Continuous Delivery and DevOps book page right now. We’re looking forward to your comments here on our site. Happy hunting and good luck!

Did you enjoy this article? Get new articles for free by email:

Comments

  1. Jem says

    I’m definitely interested in learning more about the “Culture and Behaviours”. The motivation for CD is clear to me, and the tools and techniques can be learned from various places, but knowing how to convincingly shift the organisation to functional continuous delivery is perhaps the hardest challenge.

  2. says

    I think the main problem in bigger companys is the cultural part, so i hope this book will help me in the new job/company to gain a better stand and maybe some solutions to change that first.

    Humans tend to go back to well known behavior, this book should change this.

    /jd

  3. MR says

    In my experience tools are never the problem. You set them up, you learn them. The cultural change that has to happen within a company is by far the bigger problem. As jd already noted… Humans tend to go back to well known behavior. I hope the book gives some tips on motivating people stick to new mantras. :-)

  4. Markus says

    As we are slowly starting to move towards establishing a DevOps Culture an Continuous Deployment, i think this book will be a valuable source for what to look out for and tips for getting everyone on board with the same excitement, as the once who want to embrace the change.

  5. says

    The culture topic is the one that most interests me the most. How does one move to a culture that enables continuous delivery?

    Sean

  6. Brian says

    ‘Show me. Don’t tell me’ is the best way to change a culture. I’m looking forward to the concrete examples for implementation.

  7. says

    I am a developer, and one of my best friends is sysop at my company, I would like to explore the cooperation paths between dev ops at those places where they are now fully apart, especially the sections about code on the last chapter:

    Code versus comments, Code complexity, Code coverage, Commit rates, Unused/redundant code, Duplicate code, Adherence to coding rules and standards…

    becasue I am quite certain that you can open the way from mere dev to devops from there.

  8. Wim says

    Another one for Culture and Behavior. I still see seasond sysadmins frowning when one mentions dev tools to take up into their daily work arsenal. Similarly, managers can be just plain dumbfounded by the whole concept.
    Not to mention developers who’d have to get used to sysadmin concepts! :)

  9. Larry Shatzer says

    All of the chapters look good to me.

    Chapter 1: Evolution of a Software House

    If you don’t know history, you are doomed to repeat it…

    Chapter 2: No Pain, No Gain

    The tie ins with lean (Value stream mapping) are important, and especially if your company already is behind lean concepts.

    Chapter 3: Plan of Attack

    “He who fails to plan, plans to fail.”

    Chapter 4: Tools and Technical Approaches

    Tools should be secondary over people and process, but a still important ingredient.

    Chapter 5: Culture and Behaviors

    Culture is important!

    Chapter 6: Hurdles to Look Out For

    Knowing what to look out for is important.

    Chapter 7: Measuring Success and Remaining Successful

    If you can’t measure it, you can’t improve!

  10. Dan says

    For once, this seems like a book that may apply to smaller teams. That’s what’s frustrating about most of the books on these subjects, they are written for teams that have lots of members working in an enterprise environment.

  11. says

    I am most interested in how they recommend conducting an initial assessment of your organization’s capabilities, gaps, and determining the root cause. I am also interesting in how they recommend evaluating progress (measurements) and how to evolve a culture. In my experience, these things (the soft skills and cultural changes) are much harder than raw technology decisions and implementations.

  12. Eric Garcia says

    I had just started to get really into Agile before I left my last job as an Operations Engineer. In my new position we are a new team and this book looks like it will be great for helping us get started and merging with our developers. We have the people, but no processes. These two chapters are the ones I am looking forward to reading, Chapter 3: Plan of Attack and Chapter 4: Tools and Technical Approaches.

  13. Asa Gage says

    Would love to hear how others have faced the challenge of implementing a dev ops culture and to learn from their experience.

  14. says

    While I`m mostly interrested in the Culture part as most others I`m also interrested in the Measuring Success part .. and also about the definition of Success … what is success ? .

    Oh and I`m interrested to read the Elephant in the Room definition .. I’ve seen many of them .. not a single identical Elephant :)

  15. says

    The thing that interests me the most is definitely:
    “An honest and open guide to consistently shipping quality software quickly”

    There is so much buzz around Continuous Delivery and mainly about DevOps that it would be great to hear the honest and transparent opinion from someone from the field.

    I guess that everybody talks about these two subjects but very few really know about them. Looking forward to read this book. :)

  16. Bert Van Vreckem says

    I teach Linux system administration. I’m looking for material to teach my students current topics in the field, specifically in the DevOps space…

  17. Sytse Sijbrandij says

    I look forward to sharing the book with co-workers and using it as a conversation starter to implement DevOps practices together.

  18. Rich says

    I’m super interested in reading about different approaches to testing infrastructure (as code!)

    - Incorporating automated tests
    - Combining automated tests and system monitoring

  19. Kola says

    The cultural change chapter of the book looks particularly interesting but I am also interested in the chapter on Measuring Success and Remaining Successful.

    Part of proving a business case for change is being able to identify some measure of success and demonstrate progress towards such goals.