In our organisation, BPM is hardly realised, although there is a strong will of the management tot digitalise all workflows, and go for a complete clean desk. Since BPM is not really introduced, projectleaders are appointed, without knowledge of the other ongoing projects. Since there is hardly any communication, there are frequent problems with projectscopes, since projects interact and interdepend on each other. Since there are only 2, rather inexperienced BA's in our organisation (my new collegue and I): how can we help them out?
Ik would propose to make some turtles of all the ongoing processes, to chart the dependencies, so helping the projectleaders scope there projects. Other ideas?
Chris,
I left with a number of questions regarding your companies projects. However, you are 100% correct that teams need to understand the dependencies between projects, whether the project is a business process that is being revamped or a software project that is intended to automated some of the business process.
Process Flows can definitely help identify dependencies. Understanding the Data of your organization and who touches each bit of data is another. Afterall, process typically exist in order to move or communicate data/information and transform data throughout the process.
Input Data>>Transform Data>>Output Data
brought to you by enabling practitioners & organizations to achieve their goals using:
enabling practitioners & organizations to achieve their goals using: