LightWithoutHeat.net

Book Review: Making Things Happen

2011-07-24T15:45:00.000-04:00

Making Things Happen: Mastering Project Management, by Scott Berkun, is easily the most practical book I have ever read about project management. One of the real strengths is the lack of dependency on any particular methodology, and instead a deep treatment on the thought processes and collaboration that leads to project success. This book covers all areas of the project life cycle, and is applicable to any particular approach or processes you may follow.

Berkun has a very easy tone in the book, never stretching for frivolous words or ego-based examples. Reading the book often felt like a successful friend was sharing his hard-won insights and experiences. He finds a way to encourage you while also challenging you to improve.

He develops great explanations of three perspectives on projects: business, technical, and customer. Each of these views can provide valuable questions that should be answered when developing your project plans. Finding the right balance between these sometimes competing needs will strengthen your project team and improve your chances of success.

Throughout the book, he often focuses on questions that need to be considered, and emphasizes the importance of digging beyond the surface answers to gain deeper insights. I especially liked the chapter Where Ideas Come From, where he explores a variety of categories of questions that can be helpful when exploring ideas. His explanation of “focusing questions” was particularly thought provoking for me, and I have tried to ingrain some of those ideas into my own approach to problem solving and teamwork.

Another great chapter is How To Make Good Decisions, where he again explores a great series of questions that will be helpful in evaluating decisions in a variety of contexts. I also appreciated his comments on reviewing decisions after they have been made. This kind of review is easy to skip, with project emphasis tending to be more forward-looking. By taking a little time to reflect in something of a mini post-mortem, later tasks and decisions are likely to be better informed.

This book has provided me a wealth of ideas about how to approach the many aspects of project management. I have a number of small post-it flags stuck on various pages to mark topics and ideas that stood out to me as I read the book. In reality, I could have marked just about every page. Regardless of where I am in a project, Scott Berkun’s work continues to stimulate my thinking.

Book Review: Winning

2011-05-22T15:13:00.000-04:00

Although Jack Welch is among the most recognized names in business, he was not really on my radar screen until I started to expand my career into project management. In August of 2010, I had the opportunity to see him interviewed by Bill Hybels at the Global Leadership Summit. In that interview, Jack Welch talked about authenticity, energy, and candor. His genuineness was quite apparent as each of these qualities seemed to be at the core of who he really is. When Bill Hybels said that he re-reads Winning every year, I was convinced to pick it up. Having recently finished reading the book, I can understand why Bill feels this way.

The early chapters set the tone of the book, particularly on the topics of candor, differentiation, and the importance of voice and dignity. He does a great job of clarifying what he means by a lack of candor, and observes that this is something far to common in the business world.

I am talking about how too many people - too often - instinctively don’t express themselves with frankness. They don’t communicate straightforwardly or put forth ideas looking to stimulate real debate. They just don’t open up. Instead, they withhold comments or criticism. They keep their mouths shut in order to make people feel better or to avoid conflict, and they sugarcoat bad news in order to maintain appearances.

As with all topics in the book, he speaks honestly and directly. He does not gloss over challenges, and he consistently provides practical guidance to improve your approach and your results.

With a basis in candor, his outline of differentiation becomes far more understandable and realistic, though still ambitious. He notes that this can be a controversial approach, where:

Companies win when their managers make a clear and meaningful distinction between top- and bottom-performing businesses and people, when they cultivate the strong and cull the weak.

In this chapter, he deals directly with a number of criticisms of the approach, drawing from his experience cultivating this as a key part of the business culture at GE. I found his comment about implementing this across a variety of cultures to be particularly clarifying:

Once we made the case for differentiation and we linked it to a candid performance appraisal system, it worked as well in Japan as it did in Ohio.

Covering a full spectrum of subject areas from leadership & strategy to hiring & firing, from career development to a surprisingly interesting chapter on Six Sigma, this book has earned well-deserved praise from a diverse readership.

A number of great quotes from the book are presented as sidebars in each chapter, making even a few minutes of reading time worthwhile. I also appreciate that each chapter can stand on its own, though the common core themes established in the opening chapters are woven throughout the book.

I know that I will return to this book many times - whether for a quote or chapter or more - to refresh my thinking and to focus on what winning really means.

Alabama Tornado Impact

2011-05-01T10:20:00.000-04:00

The images and stories on the news following the terrible tornado outbreak across Alabama and other southern states on April 27 are difficult to really comprehend. I have a personal connection to some wonderful people and communities that were directly impacted by this disaster, and I feel led to share some information and ask that anyone who is able to please prayerfully consider how you can help, even with a modest donation. Thousands of people have been severely impacted, hundreds have been killed, many have lost nearly everything they had, and hundreds more are still missing.

Red Cross, Mid-Alabama Region: http://www.alredcross.org
United Way of West Alabama: http://www.uwwa.org

Many of my fondest childhood memories from are from time spent with a great family in the small town of Haclkeburg, Alabama. My family would travel there from Michigan once or twice a year and be welcomed into their home. The friendship, love and laughter are still with me all these years later.

Haclkeburg was virtually destroyed by a strong tornado. Tuscaloosa, where my friend Amy now lives, was hit by an even larger tornado. Entire neighborhoods have been smashed to pieces and left as piles of debris.

The following is from my friend Amy who survived the tornado and has been volunteering in the rescue efforts:

I would encourage you to consider the Red Cross and earmark it for the Alabama tornado relief efforts or possibly the United Way of West Central Alabama. I know they would appreciate anything you can do. I spoke to mom earlier and Hackleburg is destroyed. I haven't been up there yet but understand it's quite difficult to get in at this point. More than anything pray for the people in these affected cities. They need the strength, patience, understanding, and peace to start rebuilding their lives.

The video below shows some of the unbelievable devastation that was left behind in the Haclkeburg area.

The tornado that hit Tuscaloosa was even larger, and the video below shows the actual tornado on the ground, tearing a huge path of destruction through the heart of the city. I know these videos are "impressive" in a storm-chaser sense, but please remember the severe human impact these tornadoes caused.

Again, please consider how you can help.

Book Review: Design Patterns Explained

2011-04-17T18:54:00.000-04:00

This post continues a series about books that are classics in software development, and which I have read over the years.

You might question placing this book on a list of software development classics. After all, it isn’t the "Gang of Four" book. Design Patterns Explained delivers on its ambitious subtitle, A New Perspective on Object-Oriented Design. While most text on object-oriented development tell you to focus on the nouns in the problem domain and encourage the use of inheritance, this book successfully shows the limitations and complications this can introduce when applied to more demanding software systems.

Many of the patterns covered are supported by examples from a common software system, a program to extract information from a CAD/CAM for use in another complex software system. The authors do an excellent job of presenting background on these systems without getting lost in the minutia of the systems. I thought the use of a consistent basis for the examples contributed to the cohesiveness of the book, as various design patterns were introduced within this context. While not as detailed as a case study, the examples gave the book a very practical feel.

The authors tackle the development and technical implementation of many of the most significant patterns in object-oriented design. More importantly, they address the broader concerns of how the patterns are arrived at and why they are useful. One of the quotes from this book has stayed with me since I first read it:

The pattern that is "right" for your problem is in the problem, not something to be imposed upon it.

If you are looking to broaden your understanding of object-oriented design and the world of software design patterns, you will learn a lot from this book.

Book Review: Code Complete

2011-01-23T16:25:00.000-05:00

This post continues a series about books that are classics in software development, and which I have read over the years.

Quite simply, Code Complete: A Practical Handbook of Software Construction should be required reading for anyone who aspires to be a competent software developer. I think what impresses me most about this book is the density of great information in every chapter which Steve McConnell communicates so effectively that it somehow never feels overwhelming. The material transcends any particular programming language or platform, and consistently provides practical advice and techniques to develop robust and reliable software.

McConnell makes it clear that the focus of this book is the construction aspects of software development, and therefore there is almost no coverage of topics like requirements definition or project management. This spotlight on construction still leaves room for a wide range of topics over the course of more than 850 pages.

The most common theme I saw throughout the book was that of quality. This was not presented as dry or boring QA formalities, but rather as the underlying goal of every approach to developing software. From the guidelines for when to break code out into a routine (method, function, whatever your language calls it) to the depth provided in four chapters on the numerous topics related to variables, to coverage of testing, debugging, refactoring and tuning, everything comes back to consistently doing good work.

I enjoy referring back to this book and periodically re-reading a section or two. Regardless of what my current programming involves, the information presented is always applicable.

Book Review: Applying UML and Patterns

2011-01-09T17:06:00.005-05:00

This is the first in a series of posts about books that are classics in software development, and which I have read over the years.

Applying UML and Patterns, by Craig Larman, was my textbook in a computer science class I really enjoyed and learned a lot from. As the subtitle suggests, this book provides an excellent introduction to object-oriented analysis and design. This is accomplished by iteratively working through the design of a fictitious point of sale system using the Unified Process approach to software development.

This was probably the first software development book I read that was not specific to a single programming language or platform, and I think that is part of why I learned so much from it. The patterns explored in this book begin with a set called GRASP patterns - General Responsibility Assignment Software Patterns. These patterns are a good introduction to the ideas and application of software design patterns, and are more approachable than the “gang of four” (GoF) patterns for a developer new to this topic. A number of the GoF patterns are also covered later in this book.

I found the writing style to be very clear and instructive, and I was able to improve my software design work as a direct result of the knowledge presented in this book. I also loaned the book to a junior developer a couple years ago, and he had very good things to say about it as well.

Book Review: Getting To Yes

2010-10-31T19:21:00.005-04:00

I decided to read Getting To Yes: Negotiating Agreement Without Giving In because I felt it was an area I could improve on, particularly as it applies to project management. First published in 1991, the book is one of the most widely read on the topic, and it did not disappoint me. Before reading this book, I generally saw negotiation as something between a game and a battle, and a process that was largely adversarial in nature. Authors Roger Fisher, William Ury and Bruce Patton have expanded my perspective of what negotiation is and how it is best approached.

The core of the methods outlined in the book are listed on the back cover as follows:

Separate the people from the problem;
Focus on interests, not positions;
Work together to create options that will satisfy both parties; and
Negotiate successfully with people who are more powerful, refuse to play by the rules, or resort to “dirty tricks.”

Separating the people from the problem sounds more easily said than done, and I do think it can be a significant challenge sometimes. However, Getting To Yes provides a number of practical steps to help you make this crucial distinction. Also, the importance of forethought and preparation are referenced throughout the book, and covered in specific detail in the final “Ten Questions people Ask” chapter.

I recall a coworker once teasing me, in a good natured way, about how often I would say something like “my concern here is ...” when discussing some aspect of a software development project. I didn’t realize it then, but I suppose I was focusing more on interests than on position as we debated the merits of various solutions to the technical issues we were dealing with. I think that I still work this way, but I’m going to be attentive to this kind of approach now that I am more conscious of the benefits.

The examples of tactics, scenarios and outcomes in the book are quite effective in placing the negotiating techniques into realistic contexts, and also provide a bit of story-telling in what might otherwise become fairly dry reading. From commonplace consumer issues, to labor relations and international conflicts, the authors illustrate both the successful application of the recommended negotiating methods as well as lessons learned from failing to negotiate effectively.

Although I do not anticipate becoming a professional negotiator in any high-profile sense, it is a practice that nearly all professionals are involved in to some degree. I now feel better equipped to be aware of situations that involve negotiating, and better able to contribute positively to the outcome.

NASA Shuttle Software Team

2010-09-28T18:39:00.001-04:00

I came across an article recently about the "on-board shuttle group" who are responsible for the software that launches the space shuttle. The article is They Write the Right Stuff by Charles Fishman. The scale, complexity and significance of their work cannot be downplayed, but I found the information about their approach to software development and the culture they have developed to be even more significant - which is the point of the article. I think working on this team would be amazing!

Book Review: Leading With Questions

2010-09-12T15:37:00.001-04:00

Learning is a foundational aspect of my life, and learning begins with questions. There are big questions - "what is the purpose of my life?” - and there are small questions - "what shall I have for breakfast?” - but all questions take us somewhere new. They represent an opportunity to expand our thinking and develop a deeper understanding of a topic.

Michael Marquardt’s Leading with Questions: How Leaders Find the Right Solutions By Knowing What To Ask is an insightful work that explores the importance of asking questions and the value they provide for individuals, teams, and the entire organization. I especially appreciated the breadth of coverage and insight that is contained in less than 200 pages. I marked a number of pages for future reference - guidelines and ideas I am certain will be helpful to me as I work to expand my use of questions.

After introducing the topic of questions and their broad value in leadership, there are several chapters devoted to the "how” of questions. Marquardt addresses topics ranging from the risk involved in asking questions, to the contrast between judging and learning mindsets, and ultimately the development of what he calls "a questioning culture.” He then elaborates on these ideas with chapters on managing individuals, leading teams, and developing broader organizational strategies.

This book contains a lot of very practical advice and guidance for developing good questions. This is not a simple list of canned questions. The emphasis is on the underlying goals and motivations that lead to effective questions which are applicable in any area of life and work. The book also contains a number of insights on the use of questions from leaders in a wide variety of organizations. While this topic could become quite theoretical or abstractly academic, I found it to be concrete yet broadly applicable to my life and career situation.

I highly recommend this book for anyone who wants to broaden their ability to ask valuable questions, in any situation.

Fantastic Short Video on Goals

2010-08-21T10:32:00.004-04:00

The other day, @InspiredRobin tweeted a link to this excellent video titled "Goals, Motivation, and Inspiration" from a talk given by Krish Dhanam. At just under four minutes in length, the clip is packed with insight and some great quotes. I was not familiar with the speaker, but this has definitely put Krish Dhanam on my list to investigate further.

My favorite quote, and one I have personally experienced, is "The day you practice for something you're not paid to do, is the beginning of the journey that will take you to the place where they pay you for what you've practiced."

There is another great quote at the end of the video, so I hope you'll give it a full viewing.

Book Review: How NASA Builds Teams

2010-08-08T10:20:00.001-04:00

The Hubble Space Telescope, like so many of NASA's achievements, has paid dividends far beyond what the general public typically sees in our sound-bite driven culture. Beyond the vast expansion of human knowledge directly attributable to Hubble and the other Great Observatories, you might be surprised to learn how many practical advances can be attributed, at least in part, to NASA. We owe a tremendous debt to the hard work of those at NASA. Add to that list of high impact spin-offs How NASA Builds Teams: Mission Critical Soft Skills for Scientists, Engineers, and Project Teams by Charles J. Pellerin which provides a clear and robust approach to team dynamics and the factors that contribute most to success.

The overall focus of the book is the 4-D System, a tool for evaluating and improving the crucial social context that a project team is operating within. While some may dismiss the importance of this social context, Pellerin makes a convincing case for a team's social context being central to the success or failure of projects. From Hubble's flawed optics to the tragic loss of life in the Challenger disaster, it is difficult to refute Pellerin's case for a flawed social context being the root cause of failure.

While reading the book I often experienced what I call "ah-ha!" moments where I could directly relate my own experience in software development teams to the explanations in the book. I found Pellerin's writing style to be clear and effective, almost conversational in tone without ever losing focus on the material. Although there are a number of references to the 4-D Systems web site and professional services, the book stands on its own and never feels like a sales pitch. In fact, there are many free and valuable resources provided on the web site, including a great paper which summarizes the book and approach far better than I could hope to. I encourage you to review these materials, and of course to purchase the book!

Pellerin's work will provide tremendous value to anyone looking for insight into team dynamics of communication and the internal motivations behind our behavior in a project team.

Book Review: Goals!

2010-07-17T15:30:00.001-04:00

I have been a goal-oriented person for most of my adult life, but often in bursts for periods of time like completing my Master’s degree, not always with a sustained and strategic method. In Goals!: How to Get Everything You Want -- Faster Than You Ever Thought Possible by Brian Tracy, I learned broader and deeper approaches to setting and achieving goals, and I have already begun to experience positive results from applying the techniques. These initial results have further motivated me to apply more of Brian Tracy’s ideas and to push harder toward my goals.

First of all, this book made me realize that there is substantial value in having a longer list of goals. Where I used to have one or two goals in mind, I now actively use a list of over a dozen. Some of these goals are long term but most are near-to-mid term, which I define as realistically achievable within months up to perhaps two or three years. In all cases, I have found it a great focusing exercise to explore what my goals really mean to me, and to envision them in detail as present realities.

Writing out my goals daily using the technique he recommends has been very worthwhile. I can be feeling a bit discouraged or unmotivated, and the simple process of writing a fresh copy of my goals energizes me. Reviewing my goals like this helps me to look for experiences and opportunities throughout the day to move closer to realizing my goals.

Other practices he covers have helped me to prioritize goals and the efforts needed to achieve them. He explains how to develop useful questions about goals and how to determine the most effective ways to take action.

Throughout the book, Brian Tracy keeps motivating and encouraging you, while keeping things realistic. Most goals we can imagine really are achievable. Yes, we have to be realistic, but we also have to avoid selling ourselves short. The real issue is our willingness to think hard and work hard to achieve the goals that have real value to us.

I recommend you give this book a try. As I write this post, you can get a free eBook (PDF) copy of the book from BrianTracy.com - look for the link on the homepage. If you are like me, you will like the book enough to buy it in hard copy or maybe Amazon Kindle format.

As I said, I have been motivated to keep working at applying his advice because I have already started to see benefits in a short time. I will post again in the future with an update as I work toward and achieve some goals.

Book Review: Thinking For A Change

2010-07-06T12:49:00.010-04:00

If you are looking for effective ways to shift your mental approach to any area of life, Thinking for a Change: 11 Ways Highly Successful People Approach Life and Work by John C. Maxwell provides a wealth of unique ideas and practical guidelines. Not only will you be motivated and inspired by reading this book, but you will also want to keep it handy for review.

Throughout the book, Maxwell uses stories from athletes, executives, homemakers, and world leaders as examples of the results that will come from effective thinking. He goes far beyond a simplistic approach and provides a depth and diversity of techniques to address all areas of our lives, from personal to professional. He does a fantastic job of covering a wide range of styles and approaches to thinking. From the personal aspects of Reflective Thinking, to the benefits of Strategic Thinking, and the importance of Creative Thinking, Maxwell expands your view of the thinking process and the value you can add to your life and work.

As someone who loves to learn and who finds so many topics interesting, I found the chapter on Focused Thinking particularly useful. I was amazed to learn that Maxwell has not read a single fiction novel since graduating from college. He uses this as an example of something he has given up in order to focus his thinking in the areas of greatest importance to him and his calling in life. While I don’t think I can give up an occasional science fiction book (not that he suggesting this for everyone) the lesson is very valuable to me: I need to be mindful of what areas are most important and focus the majority of my thinking and effort accordingly.

Thinking for a Change is tremendously practical and is written in very clear and understandable language. It is definitely not a stuffy, theory-oriented book. Maxwell has organized the book into eleven thinking skills we can develop, and in each of these corresponding chapters he provides concrete actions we can take to put these techniques into action, and the value we should expect to gain from doing so.

This book has found a prominent place at my desk at work. I regularly take a few brief minutes to look over a section that seems pertinent to my circumstances, and I always find both the motivation and the methods to keep striving to improve my thinking and the results that follow from it.