Why we having projects? building/supporting/changing the systems? - to make life better!
What is better? better is when all external project roles are satisfied! there are three key words/concepts here: BETTER for ALL EXTERNAL_PROJECT_ROLES
- each EXTERNAL_PROJECT_ROLE have interests and concerns. So to be able to make BETTER, we need to map them all, find contradictions and find quasi-optimal solution (as very little chances to find really optimal solution for all! - it's and evolution rule)
- in my case:
- Plant Maintenance manager wants to buy a spare part for their conveyor. And it will be easier and faster just to create new Spare part code and launch the Procurement process
- Finances controller wants to track all new Spare parts creation to avoid duplicates. As it may prevent them to find a Vendor for several plants together and launch the procurement process with the much stronger position (bigger buying lot - more chances for discount).
- Regional Maintenance manager wants to be able to check if the same spare part is available in another plant and just can be used not bought
- to achieve it you need to identify not only your system but the target system, and the chain of all enabling systems. As otherwise your changes will impact
- In my case -
- My System is Master Data Governance Department in enterprise
- Master Data Governance is ensuring that Master Data is created and used across organization in agreed way to support all needs across entire enterprise (Sales, Manufacturing, Procurement) avoid duplications and inconsistencies.
- Master Data is data about the business entities that provide context for business transaction (like: Products, Vendors, Customers, Materials).
- Business transactions are buy a Material from a Vendor, convert Material into Product, Transport the Product to the Customer and sell it,
- Data also is an object for IT department (how to model it, store, use, report...)
- Data is also an asset for Enterprise - meaning very careful attention of Finance and Internal control for risks and legislation requirements (see Sarbanes–Oxley Act - Wikipedia)
All the above is useless until the Product reach end customer and (s)he pays for that - so this I believe is a Target System = End Customer enjoys Payed Product
3. EXTERNAL_PROJECT_ROLES usually in my company it’s usual to consider those who are directly impacted by the project: end users, their managers and big boss who is paying for this. But as saying goes “there are minimum 15 EXTERNAL_PROJECT_ROLES and always +1 to what you have identified. Those whom you forgot will come to you when system is ready and will make your life brighter and much vibrant with their unconsidered by you concerns and interests..” So watch out here!