How have you organized your ServiceNow Dev Team(s)?

[sgoldberg]

Hello,

I would love to understand the different ways companies have organized their ServiceNow development teams.   Your feedback is most welcome.   I'll offer some sample models to get the juices flowing.   Choose 1 or more models.   Add your own models.

1. Dedicated SN developer team within the group that owns/manages the SN implementation.
2. BU Developers who view SN as yet another development platform/toolset.   (e.g. leverage domain specialists from the dev teams that exist within BUs.   HR developers w/in HR dept & Legal developers w/in the Legal dept, for example)
3. Tiered Developers based on complexity of project.   (e.g. more junior SN devs are assigned simpler projects while more experienced SN devs handle the complex projects)
4. Admin "Developers".   (e.g. experienced SN admins who can configure their instance and create customizations to a lesser degree)
5. Developers for hire. (e.g. 3rd party Consultants. Perhaps a complement to model #4 above for custom application development)
6. Agile methodology.
7. Waterfall methodology.
8. ScrummerFall, WaterScrum methodology.

Thanks for your help.

Steve

[vkambham]

We used a combination of 1,2 & 6 ( and dash of 5) in our company.   We took a service oriented approach- offering ServiceNow platform and applications as a "service". BU's were our service consumers and could bring business and technical resources to the table( or bring in developer for hire).

The "service" managed the agile(SCRUM) projects   that the resources would staff as prioritized by BU's. The "service" was ultimately responsible for the ServiceNow deployments resulting from the project. Making sure ServiceNow skilled resources were balanced across projects was also the "service" responsibility. I would say this model work great will multiple BU needs met simultaneously.

[sgoldberg]

Thank you Venkatesh for your kind reply.

Steve

[lisamcghee]

We use #2, with mixed results. Since everyone has a primary job SN is often lower on the priority list. Also, not every department has an Admin or Dev role so we share or one of the SN admins takes it on.