Non-functional requirements on any way of working

All organizations want a way of working with high performance, which indirectly means to fulfil non-functional requirements like; cheap, fast, qualitative and that is delivering correct and bug-free products, visualized in the picture below. Another way to put it is that an organization wants the way of working to be efficient (both flow and resource), effective and qualitative. These non-functional requirements are an acontextual part of the organizational purpose, which means that they are valid for any context; production, service or product development, etc. They go without saying, and since it is all about making happy customers, they are therefore seldom mentioned in an organization’s vision, and only sometimes in the mission or purpose. 

Other acontextual non-functional requirements on our way of working that are desirable, are for example; scalability, flexibility (as well as stability :-) ), capacity, maintainability, modifiability, to mention a few. If we fail them, we will be aware of that due to early symptoms from a mal-functioning way of working. 

Until now, it has always been easy to claim that a way of working, apart from fulfilling the performance non-functional requirements, also fulfils desirable non-functional requirements, neither of them by proving it. Many times, also as a means for the way of working or framework to be chosen, for example due to its scalability properties. But with the System Collaboration Deductions, we can now judge that. The System Collaboration Deductions originates from the organizational principles, and show us step by step how the implementation of a way of working for product development, always must look like, in order be successful with the necessary simultaneous fulfilment of all organizational principles. And by fulfilling the organizational principles, we will also fulfil the non-functional requirements, not only the performance ones, but also the desirable and mandatory, at least with easy measures. For more detailed information, also about other non-functional requirements, please see this article.