Create a template to standardize Breakdown Stories in Agile team | Community
Skip to main content
S
shirinshaikh
Level 2
August 21, 2023
Question

Create a template to standardize Breakdown Stories in Agile team

  • August 21, 2023
  • 1 reply
  • 960 views

Hello,

 

We have a use case where we will Convert a request to task for an agile team to be able to break it down into stories & create iterations. They have fixed set of steps that they need to do. Is there a way we can standardize the breakdown of stories for them similar to templates in waterfall method?

Any suggestions would be helpful. 

 

@nicholevargas 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

1 reply

Madalyn_Destafney
Community Advisor
Madalyn_DestafneyCommunity Advisor
Community Advisor
August 21, 2023

Hi there, instead of converting the request to a task, it sounds like you’d want to create a project template that captures your general process/stories and convert the request to a project instead, so you can task out the steps/tasks. You can assign the tasks into any of your iterations. Since you have many steps, converting the request into 1 task doesn’t sound like an ideal solution. Am I understanding you?

If this helped you, please mark correct to help others : )
    S
    shirinshaikhAuthor
    Level 2
    August 22, 2023

    Hi Madalyn,

    The team would like to use Agile scrum methodology and want to be able to use Agile boards to manage their work. If we convert the request to a project, then would they be able to create iterations based on backlog?

     

    Kurt_Jones
    Community Advisor and Adobe Champion
    Kurt_JonesCommunity Advisor and Adobe Champion
    Community Advisor and Adobe Champion
    August 22, 2023

    Hi Shirinshaikh,  our WF Admin team has a project queue so our users can submit requests to us, that could be small or a large scale project.  We use the filter in Boards to bring those requests in using the Iteration template to create our sprints for the work we take on.  We keep the items as requests and work in that manner as they are not well-defined and use the checklist function to break them into parts as you can make assignments at the request and checklist level.  This sounds similar to what you might want to do.

     

    The other item you could do is convert your requests into tasks within that same project queue and work them as tasks using the filter on tasks instead of requests; potentially reporting may be better going this route as well.

    If my response answered your question, please mark it answered, so others can find the answer
    Terms & ConditionsAccessibility statement

    Loading footer...