Table 8 Overview of qualitative... | Emerald Publishing

Table 8

Overview of qualitative validation

Circle	Based on ProMi	What do we learn after we used process mining within an IT demand?	Impact on demand/Decision	Side-effects
Process A – change 1	N	Higher overall effort because of detailed description	* no impact (except total effort for demand)	Early involvement of BPM department and process manager
	N	Initial cost for process mining data can be very high	* If the data is not available and not funded by other activities, then process mining for a particular change makes only sense at very big changes	Scoping for process mining projects
	Y	Business analyst, user and developer have the same picture of the problem	* Faster Effort estimation because of better overview and faster problem understanding * Better risk analysis	Avoidance of misunderstandings between user and developer
Process B – change 2	Y	Improved creation of qualitative testcases and test planning	* Test planning and execution improved because of better integrative testing	No impact of effort for testing but high qualitative improvement!
Process B – change 2	Y	PCA was able to analyse dependencies on printing and DMS (document management system) services	* Clear responsibilities (internal and external) * Faster effort estimation from third party	Change led to additional tasks for other team, but revealed responsibilities very early

Circle	Based on ProMi	What do we learn after we used process mining within an IT demand?	Impact on demand/Decision	Side-effects
Process A – change 1	N	Higher overall effort because of detailed description	* no impact (except total effort for demand)	Early involvement of BPM department and process manager
	N	Initial cost for process mining data can be very high	* If the data is not available and not funded by other activities, then process mining for a particular change makes only sense at very big changes	Scoping for process mining projects
	Y	Business analyst, user and developer have the same picture of the problem	* Faster Effort estimation because of better overview and faster problem understanding * Better risk analysis	Avoidance of misunderstandings between user and developer
Process B – change 2	Y	Improved creation of qualitative testcases and test planning	* Test planning and execution improved because of better integrative testing	No impact of effort for testing but high qualitative improvement!
Process B – change 2	Y	PCA was able to analyse dependencies on printing and DMS (document management system) services	* Clear responsibilities (internal and external)* Faster effort estimation from third party	Change led to additional tasks for other team, but revealed responsibilities very early

Source(s): Created by authors