Agile+ Concepts

Understanding information (data) and process is at the heart of Agile+ and understanding people and behavior is at the core of executing those concepts.

First let us introduce you to Data and Processes in the Agile+ world:

Data

We have found in our research that business data can be segmented into four types:

Information (usually representing 70% or more)
Derived (representing almost all of the remaining 30%)
Base (only a very few in any application)
Transient (again a relatively small number)

This segmentation is critical as it helps the stakeholder to analyze how the data is used and simplify the process of understanding even the most complex of business systems. The stakeholders can quickly partition their data, and work on each segment in order to apply rules and explanations to each. For example, Information data elements are the simplest to define, and in Agile+ these are addressed and moved off the work surface very quickly. The result is that the team’s attention is focused very quickly onto the complex components – already the task has been reduced by 70%.

By working with the stakeholders at the lowest data level we have found the comfort zone for discussion and probing. Stakeholders are very confident about exploring at this level and the interesting by-product is that the business rules are deduced and written very quickly.

The rules that govern the business processes are divided into several categories, and systematically worked through by the team. The most complex rule is what we call the Update Rule, which establishes the computations of derived elements from base elements. In most business processes (an example of a business process might be accounts receivable) there are very few of these, perhaps even only one. This does not mean that the processes are inherently simple, far from it, but it does mean that effort can be focused on the most important areas, and the understanding of complex rules is understood very early in the design process.

A unique and specific benefit of using Agile+ is that even complex business processes can be broken into their simplest components very rapidly, and what seemed like an enormous task when you started, rapidly becomes less daunting.

As an illustration of how even complex systems can be broken into simple elements:

a warehouse management process has only one update rule
a vehicle-rental system also has only one
accounts payable and receivable systems have two
a capacity planning application also has only two

The underlying information that these rules work upon, probably already exists in your organization, and we have found that files, tables or entities (whatever you call them) can be readily linked through relationships and defined once with unique paths. Equally, it is possible to create whole new sets of data to your own precise specification. The great thing is that either way, you have to define this once only and then re-use it again and again, saving time, effort and cost in the longer term. We also find that this gives organizations extraordinary flexibility in adapting their processes and systems.

Processes

A process is a series of steps that moves data in, around, and out of, a system. Where processes appear complex, it is broken into subsets. We emphasize the word "appear" as most complexity is removed when the subsets, or building blocks, are exposed. One of the great complexities in constructing the systems that support business processes arises when deciding how stakeholders will interact with it. Again, because of the methods that we use, we simplify this by breaking it into digestible components.

A program, for example, has three subsets - a Range or Search area (e.g., show me records between two dates), a Grid with the results of the search (e.g. a list of the records between those two dates), and a Detail (e.g. the record you select is displayed). Combining any of these in related programs provides the building blocks to do almost anything.

People and Behavior

Data and Processes are the dry facts that we deal with every day, however, equally important are the people involved in the process. We spend time on our certification course teaching approaches to understand the learning behaviors of stakeholders, how to conduct productive and inspirational workshops, and how to take responsibility as well as effectively delegate it. These are vital concepts and often overlooked as part of an analyst’s career training.

Capturing data and processes, writing on flip-charts and displaying the specification around a room as the workshops develop, lead the stakeholders down a comfortable path. Visualization comes quickly and easily and brings new thinking to the fore that is often inspirational, insightful and sublime.

Ultimately, with Agile+ the emphasis for everyone is on results, whether that is a meeting, a research exercise, a proof, or the delivery of the completed project. Teaching the Practitioner to get the best out of clever and willing stakeholders often surprises both parties with early and unexpected success.