Agile Development for ServiceNow

Juli T_
Tera Contributor

 ServiceNow describes a product as:  a product represents functionality that a product owner has identified as important to customers.  I work on the ServiceNow development team and trying to use the Agile module for our development, but I am a little confused over how ServiceNow describes Products and uses Products for it's own development.  

We are on Kingston, but still using Agile 1.0 right now.  We plan to upgrade to Agile 2.0 once all our environments are upgraded.  We are the only ones in our company using the Agile module for development.  My coworker and I have different opinions on the "Product".  I say the product should be the functionality we are developing which is usually requests in the service catalog.  He considers the "Product" ServiceNow unless we are developing custom apps.  It appears that the Agile module in ServiceNow functions as my coworker describes where ServiceNow is the product unless we are developing custom apps, but then everything would be under ServiceNow and we would not have any other "Products".  I think this structure would limit our reporting. 

If I were to create additional "Products" for requests, how would I categorize the product model?

Has anyone else used Agile for their own internal development of ServiceNow?  

Thanks in advance for any insight! 

1 ACCEPTED SOLUTION

Tony Wong
Kilo Guru

Hi,

Yes, we used the Agile module (v1.0 from memory) on my previous implementation project. At the time, we didn't have the Service Catalog in place and there were no Products or Product Models standards for us to align to. So we basically did what worked for us. We were building out the core IPCC (Incident/Problem/Change/Config) functionality so we had the products organised something like:

  • ServiceNow - Incident
  • ServiceNow - Problem
  • ServiceNow - Change
  • ServiceNow - Configuration

Not sure if that helps. Appreciate you'll probably want to integrate back into your Service Catalog so that it works nicely with Request .

I'm about to spin it up for my new assignment so I'm going to have the same conundrum myself!

- tony

 

View solution in original post

1 REPLY 1

Tony Wong
Kilo Guru

Hi,

Yes, we used the Agile module (v1.0 from memory) on my previous implementation project. At the time, we didn't have the Service Catalog in place and there were no Products or Product Models standards for us to align to. So we basically did what worked for us. We were building out the core IPCC (Incident/Problem/Change/Config) functionality so we had the products organised something like:

  • ServiceNow - Incident
  • ServiceNow - Problem
  • ServiceNow - Change
  • ServiceNow - Configuration

Not sure if that helps. Appreciate you'll probably want to integrate back into your Service Catalog so that it works nicely with Request .

I'm about to spin it up for my new assignment so I'm going to have the same conundrum myself!

- tony