Hi Community,
First, a big thank-you to Julia and Josh for sharing your experiences and thoughts on using a consolidated JSM project structure — your input has been incredibly helpful as we weigh our options.
That said, I’m still curious if anyone has taken a different approach by creating separate projects for each core ITIL process: Incident, Problem, Change, and Release.
If you’ve done this (or seriously considered it):
Did this approach improve long-term scalability and ownership — or introduce more friction?
Really looking to understand both the technical and organizational impact of going this route. Appreciate any insights or lessons learned!
Thanks again,
Kim
Hi @Kim Galway
thanks for your question. I would not recommend going that way and I haven't seen any customer in the last 10 years setting JSM up that way.
I curious whats your thoughts behind that scenario? Are these processes handled by completely different teams?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.