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.
- 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
- 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,
- 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?