Content area
Full text
All modern software development processes try to help project teams conduct their work. While there are some important differences between them, the commonalities are far greater-and understandably, since the end goal of them all is to produce working software quickly and effectively. Thus, it doesn't matter which process you adopt as long as it is adaptable, extensible, and capable of absorbing good ideas, even if they arise from other processes.
To achieve this kind of flexibility, things need to change. The focus needs to shift from the definition of complete processes to the capture of reusable practices. Teams should be able to mix-and-match practices and ideas from many different sources to create effective ways of working.
In this new approach to process, which we call "EssWork," teams select practices, which are then composed and integrated seamlessly into their development environments to provide dynamic and contextualized guidance, active facilitation, and even help remove mundane tasks through clever automation.
In the first installment of this two-part article, we examine the issues facing the current generation of processes and show why we have all had enough of them. In the next installment, we present EssWork and show how it can help teams realize their investment in learning, developing, and documenting best practices.
The Current Aqe: Processes
Every project team needs to have some way of working together-a way that is effective and delivers quality results on time. While every project team works differently, the way in which they work is usually inspired by what experts-internal or external-advocate. These experts have their own ways of working-their own methods, their own strategies, their own approaches, their own processes. The experts then feel the need to publish their preferred way of working in as unique and individual a way as possible, packaging their knowledge up as product-typically as a branded process, a standalone reference, or even a process framework. There are several reasons why this is a problem.
The Problem of Denied Commonality
With denied commonality, each process has a few interesting gems, but they are embedded in a larger package of commonalities. This is because no individual is good at everything, and an individual is usually only an expert on a few things.
There are many different processes promoted...