Agile workflow design

Works for implementation as well

The notion of agile software development appeared around the time when academics took interest in what the software engineers have been doing to make their job easier. In this iterative, 'small-steps' methodology aimed at getting projects done in time, extensive analysis are performed and problem identification is clearly separated from the actual development. The very same ailment plagues workflow design.

More often then not, implementers of workflow management systems get shy from implementing process in the system before full analysis is done and fancy complex graphs are produced. This leads to a lengthy analysis process and long wait period before the system is set up and presented to end-users.

The thing is, it is the wrong approach. No matter how insightful consultants are and regardless of the end-users' openness, the analysis is destined to be incomplete and imprecise. Presenting an ideal image of the process rather than a real one, amount of information that gets lost in communication, even terminology misunderstandings — these are just some of the reasons why this approach fails.

It is important to decide on a tool that allows for a „quick'n'dirty“ implementation of process concepts

How to approach the workflow design then? Agile development can lend us a hand here. Using the same principle, it is important to decide on a tool that allows for a quick'n'dirty implementation of process concepts. This in turn should result in a minimum viable model that can provide some immediate benefits to end-users.

Once the end-users are enticed by the benefits of workflow management systems, they will be more than happy to provide their feedback and insights in a readily implementable form. The key thing to remember here is that you need to offer something to end-users, otherwise they will not engage in working with a half-baked product.

Simple and flexible workflow designer is another important piece of the puzzle. You need to be able to model workflows as you receive inputs and to show actual results straight away.

Previous
Previous

Spreadsheet & email syndrome

Next
Next

Designing a workflow model: Where to start