Skip to main content
Project Management

Return to Question

Notice removed Authoritative reference needed by mattsmith5
Bounty Ended with Thomas Owens's answer chosen by mattsmith5
Tweeted twitter.com/StackProjects/status/1406174925359136768
Notice added Authoritative reference needed by mattsmith5
Bounty Started worth 50 reputation by mattsmith5
added 74 characters in body
Source Link
mattsmith5
mattsmith5
  • 141
  • 7

We are working on an Agile Scrum team. They mention it is good practice to work on PBI tasks first by Sprint Backlog Priority in code development.

Sometimes,

  1. When some of the tasksfirst Priority stories are hard, and I need time to think/have break, (mentally, I like to switch between hard and easy story tasks when I am stuck), makes it easier for head, I can come back and work on story with fresh mind
  2. or I see quick 1 hour PBIs in my sprint, that I can push to QA team , (QA is often time less busy during beginning of sprint writing test cases, they have more stress during middle or end). It spreads out the work, instead of everyone swarming on tasks,
  3. or first priority PBIs are requiring running a long process for integration testing ( I cannot wait all day, and code between while its running in server background)

What are the rules on working on Sprint Story PBIs in order? Is it a hard rule, or can be adjusted? Obviously Priority PBI item have most significance, however can things be accommodated during the schedule?

We are working on an Agile Scrum team. They mention it is good practice to work on PBI tasks first by Sprint Backlog Priority in code development.

Sometimes,

  1. When some of the tasks are hard, and I need time to think, (mentally, I like to switch between hard and easy story tasks when I am stuck), makes it easier for head
  2. or I see quick 1 hour PBIs in my sprint, that I can push to QA team , (QA is often time less busy during beginning of sprint writing test cases, they have more stress during middle or end). It spreads out the work, instead of everyone swarming on tasks,
  3. or first priority PBIs are requiring running a long process for integration testing ( I cannot wait all day, and code between while its running in server background)

What are the rules on working on Sprint Story PBIs in order? Is it a hard rule, or can be adjusted? Obviously Priority PBI item have most significance, however can things be accommodated during the schedule?

We are working on an Agile Scrum team. They mention it is good practice to work on PBI tasks first by Sprint Backlog Priority in code development.

Sometimes,

  1. When some of the first Priority stories are hard, and I need time to think/have break, (mentally, I like to switch between hard and easy story tasks when I am stuck), makes it easier for head, I can come back and work on story with fresh mind
  2. or I see quick 1 hour PBIs in my sprint, that I can push to QA team , (QA is often less busy during beginning of sprint writing test cases, they have more stress during middle or end). It spreads out the work, instead of everyone swarming on tasks,
  3. or first priority PBIs are requiring running a long process for integration testing ( I cannot wait all day, and code between while its running in server background)

What are the rules on working on Sprint Story PBIs in order? Is it a hard rule, or can be adjusted? Obviously Priority PBI item have most significance, however can things be accommodated during the schedule?

edited title
Link
mattsmith5
mattsmith5
  • 141
  • 7

Agile: Work on Priority PBI Stories in Beginning of SprintBy Backlog Priority

Source Link
mattsmith5
mattsmith5
  • 141
  • 7

Agile Work on Priority PBI Stories in Beginning of Sprint

We are working on an Agile Scrum team. They mention it is good practice to work on PBI tasks first by Sprint Backlog Priority in code development.

Sometimes,

  1. When some of the tasks are hard, and I need time to think, (mentally, I like to switch between hard and easy story tasks when I am stuck), makes it easier for head
  2. or I see quick 1 hour PBIs in my sprint, that I can push to QA team , (QA is often time less busy during beginning of sprint writing test cases, they have more stress during middle or end). It spreads out the work, instead of everyone swarming on tasks,
  3. or first priority PBIs are requiring running a long process for integration testing ( I cannot wait all day, and code between while its running in server background)

What are the rules on working on Sprint Story PBIs in order? Is it a hard rule, or can be adjusted? Obviously Priority PBI item have most significance, however can things be accommodated during the schedule?