These things change based on the the volume of customer base and how
critical the app is for the organization.
I have noticed the following roles in several clients I worked with.
Director,Manager -- Usually does not have any idea of Remedy from technical
standpoint.
Just knows high level about the business
units and customer base using remedy apps.
Usually shared across multiple apps, teams
and technologies and mostly for budget and timeoff approvals.
Lucky if you get a manager who can code in
Remedy.
Lead -- Usually dedicated to Remedy but have seen shared across different
apps and technical stacks as well.
May or may not be able to code, but can understand and fill the
dots when you discuss about remedy related issues.
Times this role might not exist as well.
Sr Developer, Admin -- Multiple resources dedicated for Remedy development
only. Some might be contractors.
BSA/Project manager -- Usually have no idea about Remedy from technical
side. Just understand the GUI and functional side data flows.
But very closely work with dev team
to address user concerns,enhancements and communication.
Times this role might be replaced
with junior dev/admin in the dev team.
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"
