Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

Limitation in Hybrid Projects: Agile Phases Only at Top Level?

jordimsant
Tera Guru

yesterday

Hi everyone,

I’m working on structuring a project in SPM (ServiceNow) and I’ve run into a limitation I’m not sure how to handle. I created a hybrid project so I can use both Project Tasks and Agile Phases. Ideally, I’d like to create a Project Task and then add Agile Phases under it, but it seems Agile Phases can only be created at the top level, not nested under a Project Task.

Has anyone else encountered this situation? If so, how did you approach or solve it?
Any guidance or best practices would be greatly appreciated.


Thanks!

0 Helpfuls
  • 78 Views
1 REPLY 1

Namita Mishra
ServiceNow Employee
ServiceNow Employee

an hour ago

Hello @jordimsant ,

Thanks for raising this point in SPM community.

 

As a best practice, In a hybrid project, first you should create Agile phase and then beneath that agile phase create the task.

Because Agile phase represents the time-boxed iteration. It is a container under which different activities (tasks) can be planned.

Just like in Waterfall projects, you first create the phase (Planning \ Execution etc) and tasks are associated with that waterfall phase. 

 

Best Practice:

Project contains phases (Waterfall \ Agile) and then each phase can have multiple tasks.

Grouping related tasks under a phase ensures that all the activities (work) related to that phase is grouped together. This makes your project plan easy to track \ manage.

 

Hope this helps and if it does, please mark the response as correct.

 

Happy SPM Learning!!

 

Thank You!

Namita Mishra

 

0 Helpfuls