Hi Harith,There are a few basic rules that provide broad guidance on defining ownership. For instance, who was the key user while the system was conceived and requirements were finalised? Who is the most relevant user? Who is requiring the system the most? Who is updating and utilising the system the most? Whose business is impacted how much if the system is not available? Who is currently making most decisions about the system as of now? Just do similar probes and create a matrix so the highest scoring top three departments of functions become the candidate owners.Now you go to the steering or similar committee with all of the above information in a condensed form that they could consume (i.e. the three candidates and how did you reach to the three candidates) and then they make recommendations for the ownership which is endorsed by the CEO.Above may not strictly be followed but provides basic steps.Hope this helps.
Jim Scardelis, CISA, CISSP, PCI 3DS, PCIP, CIPP/US, CIPP/C, CIPP/E, CIPT, MCSE ✉️ firstname.lastname@example.org |�� http://www.linkedin.com/in/jimscard/
Any views or opinions contained in this communication are solely those of the author, and do not necessarily represent those of any organizations or entities the author may be associated with.
It may help if you go back to project documentation. Who sponsored the project? Who were the key stakeholders/users? Whose budget paid the consultants? Might be CS or Sales, but you can check.