It is worth approaching this simply as a fact

[jarinislamfatema]

Your business process should solve the task at hand, answer the question that is being considered within the project. Everything else is a question of possible future cooperation. This is exactly how you should explain to customers why you do not detail some processes or do not draw another business process related to the one being discussed. Myths and misconceptions about business processes In the process of studying business processes, communicating with colleagues and customers, I heard many myths and misconceptions on this issue. Some of them are so common that I decided to share them with readers.

Myth 1. Business processes can be end-to-end I have tunisia whatsapp number data even come across this term in some books that claim to be training and reference manuals. It can also be found in online publications, and, as a result, in professional communities where business process modeling is discussed. In fact, this term does not make sense. The word "end-to-end" itself suggests that the process passes through something. But what can a business process pass through? Through an enterprise? Through a division? So any business process passes "through" in one way or another from this point of view.

Moreover, if there are "end-to-end" business processes, then there must be "non-end-to-end" ones? And how do they differ from each other, how to separate them? It would be possible to refer to "established terminology", but in this case there is no such thing. Because there is no clear definition, classification. There are business processes - each of them is the way you create it. Business processes have description languages ​​with their structure and rules. But you will not find any separate classes or types of "end-to-end" business processes in serious literature. Most likely, this term was born, like many similar ones, from the desire of yet another not very conscientious "coach" to invent his own terms either due to ignorance or for other reasons.