Knowing why OVER knowing what

What does it mean to know why over what? What I do A focus on “what” we do creates many problems. It’s easy, though. It’s the first thing that comes to mind. I write code. I test. I gather requirements. I manage projects. Unfortunately, when we do this, it’s easy to lose sight of why

Working with OVER working for

What does it mean to work with a client as opposed to working for one? Handling Unknowns Consider a situation when there is a question or some uncertainty about how to solve a client issue, what does the conversation look like? Is it just you? Does the delivery team have a meeting? Do a few

Why Manifesto

Because people in software like “manifestos”, try this as a litmus test for the decisions to make sure you’re thinking about value and not just staying busy.  As in the agile manifesto, the things on the right have value, but not as much as the things on the left. Working WITH clients OVER working FOR clients Knowing why OVER knowing what

The Why of Lean

Conventional lean tools include timing a process and tagging each action as value added or waste. That may work in a factory, but not in software development; or can it? The same precision and clarity is not possible in a knowledge industry. You cannot apply a stop watch to mental problem solving. Sometimes getting away

User Stories as Lean

User stories are a useful and well established agile tool. Could they also be thought of as a lean tool? Definition We’re not going to do what’s been done a million times. If you aren’t familiar with stories, check this out. For more information, google it. How Stories Support Agile By avoiding the “how”, the story

The Worst Waste – Unused Human Creativity

Busyness may be the prime waste and a cause of the others, but it is not the worst. Only one of the wastes is an asset that is lost forever if not used; human creativity. Unused Creativity > The Other 7 Let’s consider the other 7 wastes. Waiting wastes time, which also cannot be recovered for

Microsoft as Agile, but not Enterprise Agile

Microsoft is a dominant player in IT. But is it agile? Does it display enterprise agility? Organization Microsoft has gone through some re-orgs in the period we’ll look at. The most recent re-org created 5 engineering groups and a bunch of non-engineering groups. Those engineering groups are largely responsible for themselves are are: Operating Systems