Clarification on Scrum tasks in Project

[kellykaufmann]

I'm reading through this documentation Themes, Epics, Stories, and Tasks in Scrum - ServiceNow Wiki on assigning a Story to a Project, and have a few questions/ points of clarification I need help on.

The documentation says:

"When a story is assigned to a project, the settings in the following fields are cleared:

• Release
• Product
• Sprint
• Team
• Epic
• Theme "

1. Does this mean a Story that is assigned to a Project can't also be managed in SDLC? What if we still want that story to go out with a Release or Sprint?

2. If the answer to #1 is 'yes', does that mean we can't use a Story Progress Board or a Task Progress Board for those Stories that are part of Projects?

3. If the answer to #1 & #2 is 'yes', does this mean the story isn't included in the Sprint burn down chart (since the story can't be assigned to a sprint?)?

4. (this is a different/bigger question) If this means stories can totally be disassociated from Products now, which our organization doesn't use anyway.... does this mean we could have a field day in setting up SDLC to no longer require Products?

Thanks for your help! Anthony Okumura Pradeep Bansal

[pradeepbansal]

Hi Kelly,

The answers are as follows -

1. When a story is assigned to a project, it becomes part of that project's backlog and remains no longer part of the product's backlog. Each project has an agile phase, project team and the team sprints. The story can still be part of sprints (sprints defined for the project team) and can go out with project phase. There is no concept of a release yet within a project.

2. The story progress board and task progress boards are available for the stories part of projects too. Go to Agile->Teams-> Sprints and see the link for story and task progress boards in the related list.

3. The story is included in the sprint burndown for the sprints of the project team.Go to Agile->Teams-> Sprints and see the link for Burndown chart in the related list.

4. If you think that Agile - PPM integration would meet your requirements then you don't need to setup SDLC.

Just a side note, this may be a requirement by some organizations but currently we don't support managing stories of a project and a product together within the same sprint. Each project team defines its sprints and project/sprint backlog.

Regards,

Pradeep

[kellykaufmann]

Hi Pradeep Bansal

I created a project, 3 phases, and 3 stories all within the Project Workbench. In the stories list in Project Workbench, it says "Total Backlog: 0". What is this number updated from?

Thanks

- Kelly

[anna_scheib]

Hi Kelly, the total backlog is the total of Story points coming from stories that are not yet assigned to Sprints.

And it could also be that you did not assign points to Stories. As a PM, you would probably not being doing the point assignments, it would be up to the individual Developer/Agile team member.

Hope this helps.

[sonja1]

Thanks, Pradeep - the answers for Kelly are helpful to me.   This raises an additional question for me on the Release item....   you indicated in your reply to Kelly that "There is no concept of a release yet within a project" - I am wondering whether there is a possibility for Sprints within a Wagile project to be tracked on a Release record (perhaps outside the project?), but without removing the stories from the project - to allow tracking the story item readiness to be moved into production?

Thanks!

Pradeep Bansal