|By Tad Anderson||
|April 29, 2012 09:00 AM EDT||
|This is one cool book. If you are starting to use Scrum, read it. If you are using Scrum, read it. If you are just wondering what Scrum is all about, read it. It gives the best insight into the workings of Scrum I have seen in a book.
The chapters are laid out in a really nice to read format. Each one contains sections titled The Story, The Model (or The Practices in some chapters), Keys to Success, References, and sometimes Works Consulted (although I never figured out what the difference between these and references where?).
The story is literally a story that comes from the author's field experience that introduces the topic the chapter covers and brings to light problems being solved by the next section, The Model.
The Model and the Practices sections are the guidance and suggestions to help with the problems identified in the story. Keys to Success provide advice on how to execute the model.
The book starts with an introductory chapter, Scrum: Simple, Not Easy, in which the author makes some very important points. I don't know how many times I have repeated the sentence, "Agile does not mean easy and I believe it requires much more experience to pull off than traditional processes".
The book is then broken down into four parts. I have listed the parts and the chapters below.
Part I- Getting Prepared
Getting People On Board
Using Team Consultants to Optimize Team Performance
Determining Team Velocity
Implementing the Scrum Roles
Determining Sprint Length
How Do We Know When We Are Done?
The Case for a Full-Time ScrumMaster
Part II- Field Basics
Why Engineering Practices Are Important in Scrum
Decomposing Stories and Tasks
Keeping Defects in Check
Sustained Engineering and Scrum
The Sprint Review
Part III- First Aid
Running a Productive Daily Standup Meeting
The Fourth Question in Scrum
Keeping People Engaged with Pair Programming
Adding New Team Members
When Cultures Collide
Sprint Emergency Procedures
Part IV- Advanced Survival Techniques
Delivering Working Software
Optimizing and Measuring Value
Up-Front Project Costing
Documentation in Scrum Projects
Outsourcing and Offshoring
Prioritizing and Estimating Large Backlogs
Appendix- Scrum Framework
Putting It All Together
Every chapter was great, but I really liked Documentation in Scrum Projects, Using Team Consultants to Optimize Team Performance, The Fourth Question in Scrum, and Outsourcing and Offshoring. All these chapters contain topics I usually see Scrum teams avoiding.
A lot of agile teams like using the agile process as an excuse for not doing documentation. The author makes it very clear that documentation can rarely be dismissed. It is about doing what is needed to succeed, and planning and documentation are tools for success when they aren't over done. Too much can kill your project just as easily as doing none.
The Fourth Question in Scrum rocks. This basically brings to the table all chatter that happens after the daily standup when a project is hitting rocky ground. It gives the team a chance to voice their real opinion of how things are going.
The author provides a very realistic picture of what outsourcing and offshoring actually cost and how much hidden extra effort is involved.
The team consultant model does a good job of showing how to structure a flexible team structure.
One thing I would have liked to see more of is the inclusion of the actual practices that are executed in order to produce the documentation the author mentions. An example is architecture. The architecture documentation that results from the architecture definition process (or the Architecture Business Cycle) is just an artifact of many practices that need to be preformed throughout the entire project.
The author also includes a link to supplemental material which includes some nice tools. I really like the 14 and 30 Day Sprint Backlog Templates.
Over all I thought this book was great. It pulled a ton of real project experience into one place. It was also an easy read. The author's writing style made it really easy read. The stories were all interesting and were a cool way to lead into the chapter's topics.
The Scrum Field Guide: Practical Advice for Your First Year
Puppet Labs has announced the next major update to its flagship product: Puppet Enterprise 2015.2. This release includes new features providing DevOps teams with clarity, simplicity and additional management capabilities, including an all-new user interface, an interactive graph for visualizing infrastructure code, a new unified agent and broader infrastructure support.
Sep. 1, 2015 11:45 PM EDT Reads: 534
It’s been proven time and time again that in tech, diversity drives greater innovation, better team productivity and greater profits and market share. So what can we do in our DevOps teams to embrace diversity and help transform the culture of development and operations into a true “DevOps” team? In her session at DevOps Summit, Stefana Muller, Director, Product Management – Continuous Delivery at CA Technologies, answered that question citing examples, showing how to create opportunities for ...
Sep. 1, 2015 11:00 PM EDT Reads: 506
Early in my DevOps Journey, I was introduced to a book of great significance circulating within the Web Operations industry titled The Phoenix Project. (You can read our review of Gene’s book, if interested.) Written as a novel and loosely based on many of the same principles explored in The Goal, this book has been read and referenced by many who have adopted DevOps into their continuous improvement and software delivery processes around the world. As I began planning my travel schedule last...
Sep. 1, 2015 10:00 PM EDT Reads: 554
Any Ops team trying to support a company in today’s cloud-connected world knows that a new way of thinking is required – one just as dramatic than the shift from Ops to DevOps. The diversity of modern operations requires teams to focus their impact on breadth vs. depth. In his session at DevOps Summit, Adam Serediuk, Director of Operations at xMatters, Inc., will discuss the strategic requirements of evolving from Ops to DevOps, and why modern Operations has begun leveraging the “NoOps” approa...
Sep. 1, 2015 08:15 PM EDT Reads: 419
Microservice architecture is fast becoming a go-to solution for enterprise applications, but it's not always easy to make the transition from an established, monolithic infrastructure. Lightweight and loosely coupled, building a set of microservices is arguably more difficult than building a monolithic application. However, once established, microservices offer a series of advantages over traditional architectures as deployment times become shorter and iterating becomes easier.
Sep. 1, 2015 06:30 PM EDT
SYS-CON Events announced today that DataClear Inc. will exhibit at the 17th International Cloud Expo®, which will take place on November 3–5, 2015, at the Santa Clara Convention Center in Santa Clara, CA. The DataClear ‘BlackBox’ is the only solution that moves your PC, browsing and data out of the United States and away from prying (and spying) eyes. Its solution automatically builds you a clean, on-demand, virus free, new virtual cloud based PC outside of the United States, and wipes it clean...
Sep. 1, 2015 04:15 PM EDT Reads: 436
In his session at 17th Cloud Expo, Ernest Mueller, Product Manager at Idera, will explain the best practices and lessons learned for tracking and optimizing costs while delivering a cloud-hosted service. He will describe a DevOps approach where the applications and systems work together to track usage, model costs in a granular fashion, and make smart decisions at runtime to minimize costs. The trickier parts covered include triggering off the right metrics; balancing resilience and redundancy ...
Sep. 1, 2015 03:30 PM EDT Reads: 248
SYS-CON Events announced today that G2G3 will exhibit at SYS-CON's @DevOpsSummit Silicon Valley, which will take place on November 3–5, 2015, at the Santa Clara Convention Center in Santa Clara, CA. Based on a collective appreciation for user experience, design, and technology, G2G3 is uniquely qualified and motivated to redefine how organizations and people engage in an increasingly digital world.
Sep. 1, 2015 03:00 PM EDT Reads: 511
SYS-CON Events announced today that HPM Networks will exhibit at the 17th International Cloud Expo®, which will take place on November 3–5, 2015, at the Santa Clara Convention Center in Santa Clara, CA. For 20 years, HPM Networks has been integrating technology solutions that solve complex business challenges. HPM Networks has designed solutions for both SMB and enterprise customers throughout the San Francisco Bay Area.
Sep. 1, 2015 12:30 PM EDT Reads: 915
Whether you like it or not, DevOps is on track for a remarkable alliance with security. The SEC didn’t approve the merger. And your boss hasn’t heard anything about it. Yet, this unruly triumvirate will soon dominate and deliver DevSecOps faster, cheaper, better, and on an unprecedented scale. In his session at DevOps Summit, Frank Bunger, VP of Customer Success at ScriptRock, will discuss how this cathartic moment will propel the DevOps movement from such stuff as dreams are made on to a prac...
Sep. 1, 2015 12:00 PM EDT Reads: 241
SYS-CON Events announced today that Pythian, a global IT services company specializing in helping companies leverage disruptive technologies to optimize revenue-generating systems, has been named “Bronze Sponsor” of SYS-CON's 17th Cloud Expo, which will take place on November 3–5, 2015, at the Santa Clara Convention Center in Santa Clara, CA. Founded in 1997, Pythian is a global IT services company that helps companies compete by adopting disruptive technologies such as cloud, Big Data, advance...
Sep. 1, 2015 11:45 AM EDT Reads: 326
The pricing of tools or licenses for log aggregation can have a significant effect on organizational culture and the collaboration between Dev and Ops teams. Modern tools for log aggregation (of which Logentries is one example) can be hugely enabling for DevOps approaches to building and operating business-critical software systems. However, the pricing of an aggregated logging solution can affect the adoption of modern logging techniques, as well as organizational capabilities and cross-team ...
Sep. 1, 2015 11:30 AM EDT Reads: 408
Culture is the most important ingredient of DevOps. The challenge for most organizations is defining and communicating a vision of beneficial DevOps culture for their organizations, and then facilitating the changes needed to achieve that. Often this comes down to an ability to provide true leadership. As a CIO, are your direct reports IT managers or are they IT leaders? The hard truth is that many IT managers have risen through the ranks based on their technical skills, not their leadership ab...
Sep. 1, 2015 11:15 AM EDT Reads: 373
In today's digital world, change is the one constant. Disruptive innovations like cloud, mobility, social media, and the Internet of Things have reshaped the market and set new standards in customer expectations. To remain competitive, businesses must tap the potential of emerging technologies and markets through the rapid release of new products and services. However, the rigid and siloed structures of traditional IT platforms and processes are slowing them down – resulting in lengthy delivery ...
Sep. 1, 2015 10:45 AM EDT Reads: 608
Several years ago, I was a developer in a travel reservation aggregator. Our mission was to pull flight and hotel data from a bunch of cryptic reservation platforms, and provide it to other companies via an API library - for a fee. That was before companies like Expedia standardized such things. We started with simple methods like getFlightLeg() or addPassengerName(), each performing a small, well-understood function. But our customers wanted bigger, more encompassing services that would "do ...
Sep. 1, 2015 10:30 AM EDT Reads: 279
Docker containerization is increasingly being used in production environments. How can these environments best be monitored? Monitoring Docker containers as if they are lightweight virtual machines (i.e., monitoring the host from within the container), with all the common metrics that can be captured from an operating system, is an insufficient approach. Docker containers can’t be treated as lightweight virtual machines; they must be treated as what they are: isolated processes running on hosts....
Sep. 1, 2015 08:30 AM EDT Reads: 163
Introducing Containers & Microservices Bootcamp at @CloudExpo Silicon Valley | #Containers #Microservices
SYS-CON Events announced today the Containers & Microservices Bootcamp, being held November 3-4, 2015, in conjunction with 17th Cloud Expo, @ThingsExpo, and @DevOpsSummit at the Santa Clara Convention Center in Santa Clara, CA. This is your chance to get started with the latest technology in the industry. Combined with real-world scenarios and use cases, the Containers and Microservices Bootcamp, led by Janakiram MSV, a Microsoft Regional Director, will include presentations as well as hands-on...
Sep. 1, 2015 08:15 AM EDT Reads: 364
DevOps has traditionally played important roles in development and IT operations, but the practice is quickly becoming core to other business functions such as customer success, business intelligence, and marketing analytics. Modern marketers today are driven by data and rely on many different analytics tools. They need DevOps engineers in general and server log data specifically to do their jobs well. Here’s why: Server log files contain the only data that is completely full and accurate in th...
Sep. 1, 2015 07:45 AM EDT Reads: 410
Skeuomorphism usually means retaining existing design cues in something new that doesn’t actually need them. However, the concept of skeuomorphism can be thought of as relating more broadly to applying existing patterns to new technologies that, in fact, cry out for new approaches. In his session at DevOps Summit, Gordon Haff, Senior Cloud Strategy Marketing and Evangelism Manager at Red Hat, discussed why containers should be paired with new architectural practices such as microservices rathe...
Sep. 1, 2015 01:00 AM EDT Reads: 415
What does “big enough” mean? It’s sometimes useful to argue by reductio ad absurdum. Hello, world doesn’t need to be broken down into smaller services. At the other extreme, building a monolithic enterprise resource planning (ERP) system is just asking for trouble: it’s too big, and it needs to be decomposed.
Aug. 29, 2015 10:00 AM EDT Reads: 365