I'm gonna guess that this slack group will be used for future books given the way it's setup. I was planning on buying a copy of The Unicorn Project for our devs as an early christmas present after reading through the first few chapters of the excerpt that was posted yesterday. If I did that and showed proof-of-purchase, would they then also be able to access this slack? If so, would I just need to include a list of emails to send invites to? Also, would they be able to access the Team Topologies channels or only the channels for whatever books they purchased or that someone purchased for them?

I'm gonna guess that this slack group will be used for future books given the way it's setup. I was planning on buying a copy of The Unicorn Project for our devs as an early christmas present after reading through the first few chapters of the excerpt that was posted yesterday. If I did that and showed proof-of-purchase, would they then also be able to access this slack? If so, would I just need to include a list of emails to send invites to? Also, would they be able to access the Team Topologies channels or only the channels for whatever books they purchased or that someone purchased for them?

I haven’t gotten around to reading it. That good @jerreck.moody?

I think so. I'm not quite finished with the excerpt, but I can tell from the conflicts it's setting up what the lessons are going to be. Seems to be written with developers as the audience in mind as opposed to CIOs, so I feel like it will do a better job of hitting home with our devs than the Phoenix Project.

I'm particular interested because after reading "The Phoenix Project" I went around telling everyone that due to the key learnings it should have been called "The Unicorn Project" 😏

I'm looking forward to reading the Unicorn Project. The Phoenix Project was a revelation for me back in 2013: https://www.infoq.com/articles/phoenix-project-book-review/

Same! (Except 2014 for me; I was late to the party.) That book was the inspiration for my transition from a data center ops focus to a software/devops focus in my career. So far the excerpt is interesting but I don't think I'll read the whole thing. I'll wait for the book.

We might do a joint TT/Unicorn piece at some point - watch out for IT Revolution news! 🙂

I'm coming into all of this pretty recently. I picked up TPP in July after a colleague recommended it to me. Finished the audiobook over that weekend (I drive to Oklahoma and back a lot for family/friends), and it was so good that I picked up the Devops Handbook audiobook and finished that the next weekend. I probably listened to it all the way through three times before I bought a box of ten DHB paperbacks for folks at the office. Most of our senior leadership had already read TPP a couple years ago that prompted us to run what's been a very successful experiment with cross-functional teams and SCRUM, so I gave one to each of them and some other folks then put the rest of the copies on our shelf at work. I've since read/listened to Value Stream Mapping by Karen Martin and Mike Osterling, Beyond the Phoenix Project, Team Topologies (of course), about halfway through the Machine That Changed the World, and just picked up the rest of the books from IT Revolution yesterday. Reading through Project to Product now that yal have recommended it here. Going to hand it to our product manager when I'm done. We've started to practice some of the small things that we can do from these books and it's already making a difference at work after just a couple weeks. We're about to wrap up our first set of microservices that we're now building a CI/CD pipeline for with some automated tests, static code analysis, and other cool stuff that have obvious benefits for flow. We've also started mapping value streams for some of our smaller products (already identified some small things we can do to reduce queue times), and I'm talking to our CIO next week about getting a weekly meeting between our dev and IT teams. Anyway, didn't mean for this to turn into such a long post, but so far I've received nothing but good advice from IT Rev books and the sources they cite and I'm recommending them right and left. Handed my CTO a copy of TT that I bought him last week. I'm thinking the ideas there about inverse conway maneuvers, managing cognitive load, becoming a sensing organization, etc. that we've been discussing in the TT channel will be more essential to our success the next few years than anything else.

I'm coming into all of this pretty recently. I picked up TPP in July after a colleague recommended it to me. Finished the audiobook over that weekend (I drive to Oklahoma and back a lot for family/friends), and it was so good that I picked up the Devops Handbook audiobook and finished that the next weekend. I probably listened to it all the way through three times before I bought a box of ten DHB paperbacks for folks at the office. Most of our senior leadership had already read TPP a couple years ago that prompted us to run what's been a very successful experiment with cross-functional teams and SCRUM, so I gave one to each of them and some other folks then put the rest of the copies on our shelf at work. I've since read/listened to Value Stream Mapping by Karen Martin and Mike Osterling, Beyond the Phoenix Project, Team Topologies (of course), about halfway through the Machine That Changed the World, and just picked up the rest of the books from IT Revolution yesterday. Reading through Project to Product now that yal have recommended it here. Going to hand it to our product manager when I'm done. We've started to practice some of the small things that we can do from these books and it's already making a difference at work after just a couple weeks. We're about to wrap up our first set of microservices that we're now building a CI/CD pipeline for with some automated tests, static code analysis, and other cool stuff that have obvious benefits for flow. We've also started mapping value streams for some of our smaller products (already identified some small things we can do to reduce queue times), and I'm talking to our CIO next week about getting a weekly meeting between our dev and IT teams. Anyway, didn't mean for this to turn into such a long post, but so far I've received nothing but good advice from IT Rev books and the sources they cite and I'm recommending them right and left. Handed my CTO a copy of TT that I bought him last week. I'm thinking the ideas there about inverse conway maneuvers, managing cognitive load, becoming a sensing organization, etc. that we've been discussing in the TT channel will be more essential to our success the next few years than anything else.