Workflow Modeling: Tools for Process Improvement and Application Development

Arrived, Nice Aide Memoire for this kind of thing.

Can you clearly identify what is a process and what is not?Ever wanted to know where things usually go wrong in real life process improvement projects?Have you ever wondered what should be measured in a business process and what should not?When should you stop analyzing the current process so you can focus on the new one?How will you go about designing the new process so it doesn't have the same old problems?What can be done to help address those internal politics between departments that hinder your process improvement efforts?How many diagrams should you have?Should this diagram be a swim-lane diagram, a use case or something else?What is the most important, quick and easy, diagram to capture at the beginning of your process analysis?What should be in a flow diagram and what should be written out as narrative?If you ask these sorts of questions, or get asked these questions, then Sharp and McDermott's book is for you. Their combined experience as process troubleshooters, expert project managers and training consultants comes shining through in every part of the book. They are not trying to sell a product nor are they high on the latest industry buzz juice. They have technical depth that is apparent from time to time, but this is not a technical book. If you want to learn a lot about how to improve almost any kind of organizational process, this is a fantastic book. The approach would have worked well 20 years ago and it probably will 20 years from now. Nevertheless, there is some discussion about IT and how important it is to the effort. In fact, the last part of Workflow Modeling shows how to translate all the process analysis work into Use Cases suitable for a detailed software development effort, but that is not the overall emphasis.The method the author's apply is given in four steps (p29):1. Frame the process - Identify what is in and out of scope for being in the process to be improved. Make sure you are working on an actual process and if not, locate one important to the original request so it can be improved. Lots of tips on managing upper level management and non-quantifiable factors such as corporate culture, building grass roots support for the project etc. This is roughly 30% of the book.2. Understand the current as-is process - This is really the meat of this book. Even if you aren't trying to change a process, but just understanding one, this section makes the book worth its price. Using swim-lane diagrams at various levels of detail the book explains how to analyze the stuffing out of a process without getting bogged down in unnecessary detail. Constructing professional swim-lane diagrams with all the actors, milestones, areas of uncertainty, process enablers and many other important topics are covered in practical, how-to terms. Roughly 40% of the book.3. Design the new (to-be) process - using all you've gathered from previous stages, systematically apply and manage brainstorming and other creative tools to make sure the important parts of true improvement make it into the new process. Roughly 20% of the book.4. Develop Use Case Scenarios - For those who will then need to launch development work to support the new process (very common) this shows how to bridge that notorious gap between business needs and technical IT work. Roughly 10% of the book.The style of the book is almost like a manual, but still interesting. The writing style is very informal and keeps the information personally applicable where it might otherwise become dry and abstract. There is some high level management alignment, strategy information in chapter 7 that probably could have been left out, but even this has its useful points. This book is practical and as easy a read as this topic will allow. Highly recommended.

This book nicely sets forth a detailed methodology for doing swimlane diagramming for workflow business processing. This book is for analysts; the discussion is about the nature of business processes that have workflow as a key characteristic. It is not about the architecture of computer solutions for such processes. If you follow the methodology in this book and flesh out the diagrams with use cases (just briefly touched on here), you will have captured most of the requirements for a business workflow process.The book is nicely bound and well written. The authors have been around a while and the vocabulary and approach fit nicely with older concepts like business process reengineering. The authors are not unaware of the latest developments and "UML" crops up here and there but not in the index. The diagramming is very simple compared to UML activity diagrams.This is good reading for the domain experts on a team working on the requirements document and a nice primer for geeks who are forced for the first time to talk to the business side of an enterprise.

Everything started with the creation of a two days workshop: Workflow Process Modeling. The authors have continually improved the workshop with participants' feedback and ideas based on their own hands-on consulting work with many organizations. The book is very well structured and it is based on real world experience. The structure is simple with no unnecessary parts that usually fill other books with redundant content. The content is not a mere recount of personal experiences: there are plenty of references to other publications. Plus, you will find good humor in the book that makes it even more readable.Although the authors declared their work aimed at application development work as a final outcome, the book is focused very much on the business side with emphasis on process workflow. Nowadays the specialization pushes further and further apart the role of a business analyst from the system analyst, while in the past some would refer to these roles as one. This book might not be very useful for a system analyst because it is not very technically oriented. You will not find yourself drown under zillions of diagrams created with a specific software package, but you will get instead a method of how to approach business analysis from a broad, yet practical, perspective. The book does not bother even to talk too much about UML. I found that refreshing and extremely useful. I have been searching for a book that is more like a thought provoking companion rather than a software tool manual and this book fits that description.Workflow Modeling is a comprehensive book. It does not focus on a particular stage of business analysis. It provides an inventory of areas the professional business process consultant would have to consider and the rationale for each one of them. Some readers might not agree with the little amount of space dedicated to class modeling which is almost inexistent. On the plus side, the authors talk about approach in dealing with project stakeholders, pitfalls, team building and difficulties and what questions to ask in various situations. The authors appreciate the importance of the final delivery, how to map the road between the as-is process to to-be process and understand the structure of the organization. I found many things that were said here very realistic and valuable; I could relate them to my own experience. The book does not say much about class modeling, but it talks a lot about swimlane diagrams and use cases analysis.You can use Workflow Modeling to design your own work template that suits your style and formation. You can come back , re-read some parts or the whole book (I have done that) and still get something out of it. I recommend the book as a good investment that will not go out of fashion very soon.