New answers tagged

2

Unlike the Product Backlog, which is an "ordered list of what is needed to improve the product", the Scrum Guide does not specify if the Sprint Backlog is ordered or, if it is, how it is ordered. Instead, it describes the Sprint Backlog as a "plan by and for the Developers" and a "highly visible, real-time picture of the work that ...


2

What are the rules on working on Sprint Story PBIs in order There are none. All the things you mention are sensible reasons why you might not go in strict priority order. However, you may want to discuss some of these reasons in your retrospectives. Is it possible that by changing the approach the team takes you might be able to make these exceptions less ...


0

Good question and many good answers, including those that highlight that there is no one single correct answer :) Many replies do stress that iterating in smaller chunks allows for a better flow, though coupled with lack of reliable planning (or mid-way change of plans - which is a large factor of what agile is about) it can lead to mess in code and project. ...


0

Is there any way out of my dilemma? You write about the "old guard": They also complain that in depth review is impossible without reviewing the entire epic as a whole. They also complain that they can not release the software if it contains a partially completed epic that is merged into the main branch. It sounds like the old guard may actually ...


0

I have a suggestion that may help you to get your so called Old Guard to see what they are doing is not the most productive way. In the book The Phoenix Project the problem with very large software releases(amongst others) is explained very understandable. https://itrevolution.com/the-phoenix-project/


2

There is no single answer to this question. The purpose of branching is to facilitate parallel development. But exactly what kind of parallel development you need to support could differ from company to company, team to team, and even project to project. It's like asking "what kind of vehicle is best?" Well, that depends on your needs. Do you need ...


2

The long-lived feature branches and the merge conflicts are both symptoms: you have a lot of people working on the same codebase, but coordination is lacking. Now there are two ways of dealing with this: take the most recent version from the main branch, make the minimal change that implements the interface you need and that doesn't break anything else, and ...


14

Long-Lived Feature Branches and Infrequent Merging are Anti-Patterns Which is better large feature branches or merging frequently? Which is better small work items vs large work items? This question has both engineering answers and project management answers. In general, though, the answers will be similar for both disciplines, although perhaps for ...


23

There is a lot to unpack in your question, but from what I read I see two main issues: the old guard (as you name it) doesn't want to change their way of working. What they did might have worked before, or not, but they found themselves a certain pace of doing things and the changes you want to bring forth are not to their liking. Since you mention a new ...


Top 50 recent answers are included