September 17, 2015
At the core of most of the important work done in this world you will find a small, multi-skilled team with effective leadership focused on delivering a product of value to a customer.
Note that teams such as these are found in contexts as different as Jazz bands, Rock groups, filmmaking, Agile Software Development and Lean Manufacturing, to name just a few obvious examples.
It’s now commonplace in business to take the work of teams for granted, but in my experience that passive acceptance doesn’t always translate into active support.
Let me break my opening assertion down, and explain the significance of each of its components.
July 29, 2015
The Apple Watch is much like the Velvet Underground: just as it was famously said by Brian Eno that not many people listened to the original VU albums, but all of them started their own bands, so it is true that “not many” people are buying the first generation of the Apple Watch, but all of them are writing their own reviews of it. And so here’s mine.
I’m a fairly tech-savvy guy who already has at least one of just about everything Apple makes. I’m six feel tall. I walk and run, but not competitively. I’ve worn a watch all my life.
I ordered the 42MM Steel Case with the Milanese Loop. Anything smaller would have looked silly on my big wrist. The steel case seemed much more like a real watch than the aluminum sport model. And I like the infinite adjustability of the Milanese loop, as opposed to some of the others. I also purchased a black Sport Band to use for running. And I also got a mophie watch dock to use for overnight charging.
June 11, 2015
Many software development teams seem to treat “Agile” and “Project Planning” as if they were mutually exclusive concepts. The tendency, it seems, is to simply jump straight into Agile iterations — at best starting with an Iteration Zero — and then trust that things will sort themselves out strictly through a team-based Scrum-like approach.
In practice, though, teams seem to regularly run into trouble with this sort of naïve approach to starting up an Agile project — especially any sort of large, ambitious project operating within the context of a major enterprise.
Rather than proceeding blindly ahead with nothing more than faith in Agile iterations as a panacea, here are some of the planning considerations that I think projects should explicitly address at their outset, before their first sprint.
March 21, 2015
For those who have not yet heard of it, the Scaled Agile Framework, or SAFe® for short, is a “publicly available framework for applying lean/agile practices at Enterprise scale.”
I believe that the SAFe model offers a number of benefits to those who may be considering its use. Let me enumerate them.
December 14, 2014
I sometimes wonder if many of us in Information Technology are yet taking an informed perspective when contemplating investments in new software development efforts. Here are several things I think we should be keeping in mind.
December 4, 2014
Some of the most troublesome topics in software development are those surrounding defects:
Let me introduce my thoughts on this topic with a little story.
November 19, 2014
I’ve written in the past about the importance of understanding polarities and how they need to be managed.
My previous post involving Polarity Management concerned process improvement, but the topic is equally relevant to other aspects of software development.
A polarity is most simply defined as a complex problem that has no solution. It might also be stated as an either/or question that has no single right answer. A more complete definition might be “A set of two opposing or contradictory extremes permitting wide variation along a spectrum of choices, with both opposing poles offering advantages and disadvantages.”
The pros and cons of a polarity are often represented in the form of a polarity map, in which each quadrant represents the pros or cons of one pole or another.
Now that we know what a polarity is, let’s look at a number of different polarities that need to be commonly addressed during a software development project.
September 8, 2014
It occurred to me recently that there are really three essential functions of management.
Strategy: setting a direction for your organization.
Alignment: getting organizational resources lined up to execute the strategy.
Execution: delivering expected results as part of the fulfillment of your strategy.
One might argue that there are many more functions of management, but I think it is helpful to understand that these three are the primary and in fact essential functions, and that all the other things managers do must be understood to support one or more of these three functions.
Let’s take a look, then, at the essential nature of these three functions.
August 1, 2014
In order to survive and thrive, any organization must possess the following four characteristics.
November 23, 2013
A sure sign of danger on a software development project occurs whenever anyone says, “Don’t worry about the problem – just trust the process.”
This danger is equally present whether the process to be followed is of the waterfall variety, or of an agile persuasion.
The chief danger is not in picking the wrong process, but in placing an excess of faith in any process, no matter what it is.