What is PBE and Why do we need it?
As an early posting, this is a good place to start – what is PBE and why should we care about it? Why do we need it?
Let’s start with a definition – PBE is a systematic, disciplined and quantifiable approach to using pattern specifications and implementations in the development and delivery of software solutions. To succeed in learning, adopting and executing PBE we provide a set of Core Values, Patterns and Guidelines, and a Practice. The book goes into great details in describing each of these elements – and here on the blog and associated articles we’ll look to touch upon some of the aspects of each of these elements. In addition, we’ve made the entire practice available for download in both source and published configurations.
So why do we need PBE? Over the years we’ve been involved with many teams where we’ve used patterns. In earlier days, the focus was primarily on pattern specifications. More recently, a great deal of focus has been on pattern implementations. However, in all situations, we’ve seen the challenges in getting teams to use patterns – and to do so in a way that is strategic to the effort at hand. Even in cases where the project has had a high level of success it was hard to transition the key success factors to others in the organization and replicate that success. Our goal with PBE is to provide materials to help a team and organization successfully use patterns. We’ve viewed ourselves much more as archeologists rather than inventors – we’ve talked and worked with many, delivered training, consulted, researched and channeled all of these sources into our book.
In reading about PBE – we hope that you see the materials as common sense, agile, and beneficial to the productivity of yourself and your organization.