Visualisation Limits in Enterprise Agile Planning

Natalie Hunter
Tera Contributor

Please advise if there are any visualisation limits set in Enterprise Agile Planning like there were in Scaled Agile Framework. 

What are the outer limits that were stress tested for displaying Stories with dependencies, Features with dependencies, Epics with Dependencies (at the various layers)?  

 

 

2 REPLIES 2

Scott Townsend1
ServiceNow Employee
ServiceNow Employee

Hi Natalie,

Are there any areas of concern?  We set up EAP to be scalable (e.g., through the pagination on the backlog and by setting the context to the iteration on the Home tab at the Team and ART/Group of Teams levels).  We did put a original limit of 500 cards on the Planning Board, as you will see some slowdown if going over this amount (but that also depends on how much data is being viewed on the cards, your environment, etc).  I should mention that the Planning Board filter can be used to focus in on exactly what you need to view. 

Thanks!

Scott Townsend  

Hi Stuart

In SAFe, the OOTB limits on the "safeboardbigroomplanningmetadataservice" did not support the size of the ARTs and we had to increase the "teamlimit" and the "featurelimit", and yes this did impact the performance of the Big Room Planner.  This resulted in teams informally exporting their Features and actually planning outside of ServiceNow.

As the use of SPM within the organisation is expanding to include other operations, we will be running multiple solution trains in EAP and we anticpate them being quite large with +- 10 ARTs with a minimum of 8 teams in each ART in each Solution Train.  Are you able to share the structures/limits that were stress tested?