2020

The Hidden Waste in Software Projects

It’s invisible, yet it’s right in front of you. It’s invisible, yet it’s the most common topic covered in most of your project meetings. It’s invisible, yet everyone knows it’s a problem. It’s invisible, yet you’re unwilling to make any effort to improve visibility. It’s the most costly impediment to success within every phase of the software development life cycle (SDLC). And it continues to rob productivity and profitability throughout the lifespan of the software product. Read More…

Which Comes First, Requirements or Use Cases?

That was a question posed on the r/businessanalysis Reddit community recently. Below was my response comment to the post. Read More…

How to Estimate Business Process Mapping for Software Projects

There is no industry standard or common formula for estimating the work of business process mapping and modeling. That’s primarily because of the wide range of variables involved in the work. Secondarily, few organizations have any experience in performing or managing the work of business process mapping and modeling. Read More…

A Practical Framework for Business Process Modeling

Several years ago I wrote this article, then posted it on a site called ArticlesBase. According to Wikipedia, "Articlesbase was an online directory of syndicated articles on 26 core topics," that eventually included more than 3 million articles published by more than 300,000 authors. The site went offline in early 2017 and my article disappeared from the Internet. I decided to revise the document and republish it here: A Practical Framework for Business Process Modeling

The Case for a Business Process Modeling Tool and Repository

Your organization's business processes can be thought of as intangible assets. One of the components of a business process asset is its documentation . But while maturing organizations might have their processes documented, the ability to quickly and easily access that content is often a challenge. A step up from widely scattered documentation is the implementation of a centralized Business Process Modeling Tool and Repository. Below is a list of benefits to consider. Read More…

The Difference Between Accuracy and Precision in Business Process Modeling

The greater the level of precision, the greater the return on investment (ROI) in the work of business process mapping and documentation. In other words, an accurate yet imprecise workflow diagram has less value to an organization than a workflow diagram that is both accurate and precise.

Aren’t they Synonyms?
Outside of business process mapping and documentation, the word pairs are often considered synonymous. But in the context of business process mapping and documentation they are specifically different. In this post, I’ll explain that difference by first examining the dictionary definitions of the words. Then I’ll explain my interpretation of the differences and how they apply to the quality and utility of business process mapping and documentation.
Read More…

The Difference Between Thorough and Complete in Business Process Modeling

A business process flowchart alone does not represent a thorough business process model. A thorough business process model is one that illustrates and specifies all of the relevant details of a process. While a good flowchart can communicate many process details, other types of content can detail or present information more effectively, efficiently, or purpose-driven.

The type of audience or consumer of the business process model is the criteria for determining what is relevant. If one of the objectives of the business process model is to provide value for the widest range of audiences, then an illustration and specification framework should be used to guide the business process model developers. Read More…

The Risk of Memory-Based Event Triggers

A business event triggers a response. The response is a business process. When a business event is triggered (initiated) only when a human performer remembers to trigger it, I call that a Memory-Based Event Trigger (MBET). MBET’s are risky because the business depends on a performer to remember to trigger the event. If the performer forgets, the process doesn’t happen. If the performer takes a day (or week or month) off, the process doesn’t happen. Read More…