Joined: Mar 04, 2008 Posts: 1883 Location: Newcastle-under-Lyme
Posted: Thu Sep 29, 2011 5:59 am Post subject:
Firstly, I'm not sure how you can call development third line. I usually think of these lines as being lines of support.
Secondly, I'm not sure how (in a theoretical sense) development can raise a change, since development's role is to develop things that are requested.
Putting one and two together, and adding your bit about development being primary in the business impact analysis (presumably along with the business), I think that you would have a clearer discussion if the roles were better defined and labelled. If development are really a support level as well as developers, then the two roles must be understood clearly. Think of the case where all development work is outsourced. They third party would certainly not be requesting changes (I hope!).
Who requests a change? Well surely it is the person who will benefit from the change. so, if an application is giving operational problems, then Operations will request the change. If the application is not meeting a business need then the business will request the change. If the application is performing poorly, then the performance manager will request the change. These are not rules, but suggestions of a logical approach, in which the person who feels the need for the change requests it.
In the case you outline, you almost imply that second line support identified the need for a change and asked development to do it if they agreed. Why should second line not raise the request formally? They have certainly taken the view that there is a case for it and demonstrated that they understand the issue and they have an interest in it being done, since it will relieve the support role by reducing the probability of incidents.
I'm not sure if there is complete consistency in the above paragraphs, but hopefully they will help you to think about the question. _________________ "Method goes far to prevent trouble in business: for it makes the task easy, hinders confusion, saves abundance of time, and instructs those that have business depending, both what to do and what to hope."
William Penn 1644-1718
Last edited by Diarmid on Wed Nov 02, 2011 2:20 am; edited 1 time in total
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum