Agile, Uncategorized

I first learned about Agile from Canadian Hockey

I’ve been trying to put this post together for a while and I finally got my four points completed. This post has been sitting around in an unfinished state and I figured I needed to complete it before the NHL returned to Winnipeg. 🙂

Go Jets Go!

The four Agile rules I learned from hockey

Play for the crest on the front of the jersey rather than the name on the back – Simply put, the individual cannot have a personal agenda or an ego. Every member of the team must be willing to do whatever it takes to have the team succeed. This is seen again and again in the Stanley Cup playoffs. You never see a good Canadian boy saying he doesn’t get the puck enough.

Mistakes cause you to lose games – Mistake or defects cause you to lose a game and also have bad projects. These things just cannot happen. Good teams do everything they can to eliminate these mistakes and defects. Good coaching can eliminate mistakes from a hockey game and Test Driven Development can eliminate defects from a Software Development Project.

Winning the game/satisfying the client is the only thing that matters – It doesn’t matter if you scored a hat trick, had 7 assists (sorry Darryl Sittler, but I’m a Habs fan), or delivered just what the contract stated. None of that matters at all. The only thing that matters is if you won the game and the client was delighted. Too often in both Hockey and Software Development we seem to be more focused on these small victories and sacrifice the end goal.

Shoot the darn puck/deliver the darn iteration – You can’t win the game unless you shoot the puck at the net. You can’t succeed in satisfying the client unless you actually deliver something to the client. Iterations and trying to score often is at the heart of success in both Hockey and Software Development.

Editor’s note: Sorry Don Cherry, I tried and failed to think of an analogy for fighting. 😦

Re-posted from

About Terry Bunio

Terry Bunio has worked for Protegra for 14+ years because of the professionalism, people, and culture. Terry started as a software developer and found his technical calling in Data Architecture. Terry has helped to create Enterprise Operational Data Stores and Data Warehouses for the Financial and Insurance industries. Along the way Terry discovered that he enjoys helping to build teams, grow client trust and encourage individual career growth, completing project deliverables, and helping to guide solutions. It seems that some people like to call that Project Management. As a practical Data Modeller and Project Manager, Terry is known to challenge assumptions and strive to strike the balance between the theoretical and real world approaches for both Data Modelling and Agile. Terry considers himself a born again agilist as Agile implemented according to the Lean Principles has made him once again enjoy Software Development and believe in what can be accomplished. Terry is a fan of Agile implemented according to the Lean Principles, the Green Bay Packers, Winnipeg Jets, Operational Data Stores, 4th Normal Form, and asking why


No comments yet.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: