What do you call this job ?
-
The bank where i work is having a re-org, and I need to choose a title for myself :cool: My current title is "Senior IT support", where i get to handle tickets, either directly by development or by assigning tickets to vendors. My new responsibilities are the following: 1. Working exclusively on ongoing projects, no support. (Yay! :thumbsup:) 2. No internal development, all projects assigned to vendors, closed box with no source code. (Boo :thumbsdown:) 3. Handling all technical aspects of new and ongoing projects (technical review, deployment, testing, giving feedback to PMs, etc.) The following titles are initially rejected during brainstorming with my team members: 1. Software Developer (no development going on!) 2. IT Consultant (rejected since we are the on the client side (Que unfunny puns)) 3. The Man (i thought it was good) 4. IT Specialist (too broad) 5. IT Architect (invalid since the vendor will usually architect the system, we only review) 6. IT Analyst (implies you are doing analysis most of the time, while most of our work will be review, implementation and testing. So what do you call a software developer, that doesn't do any development, is involved in the technical aspect of projects and is on the receiving end of projects ?
Amr Abdel Majeed Senior Software Developer
I don't agree with your view of support. I worked mostly on projects for many years, but always managed to do some support as well. Apart from helping people who would have been helped much more slowly (if at all) by the formal processes it gave me the following benefits. 1. A better understanding of what is really going on in the user community 2. Often, a problem / investigation is also a learning experience 3. It widened my contacts within the business so whenever I needed help from someone in country X or function Y, I had a good chance of finding it quickly and easily. So by all means work mainly on projects, but never give up support completely.
Roger
-
The bank where i work is having a re-org, and I need to choose a title for myself :cool: My current title is "Senior IT support", where i get to handle tickets, either directly by development or by assigning tickets to vendors. My new responsibilities are the following: 1. Working exclusively on ongoing projects, no support. (Yay! :thumbsup:) 2. No internal development, all projects assigned to vendors, closed box with no source code. (Boo :thumbsdown:) 3. Handling all technical aspects of new and ongoing projects (technical review, deployment, testing, giving feedback to PMs, etc.) The following titles are initially rejected during brainstorming with my team members: 1. Software Developer (no development going on!) 2. IT Consultant (rejected since we are the on the client side (Que unfunny puns)) 3. The Man (i thought it was good) 4. IT Specialist (too broad) 5. IT Architect (invalid since the vendor will usually architect the system, we only review) 6. IT Analyst (implies you are doing analysis most of the time, while most of our work will be review, implementation and testing. So what do you call a software developer, that doesn't do any development, is involved in the technical aspect of projects and is on the receiving end of projects ?
Amr Abdel Majeed Senior Software Developer
-
To me, it sounds like the Scrum role, Product(s) Owner. Owners get paid a lot, right?
-
To me, it sounds like the Scrum role, Product(s) Owner. Owners get paid a lot, right?