New answers tagged

1

An additional possible approach to consider, which could be taken alongside the admirable suggestions here to split up the feature, is to 'release' sections of the feature but with a 'switch' to allow the feature to be turned off, or only turned on for specific users/in specific circumstances when the first parts of this are released. This may help if you ...


2

As a Scrum Master your responsibility is to ensure your team is following the Scrum framework. The best way to do this is to explain the consequences of not following Scrum and how it will impact on the organisation. Scrum talks about a potentially releasable Increment at the end of each sprint. The value with this approach is that: You can get regular ...


0

In Scrum team works to provide the shippable product as an output of each Sprint. It is recommended to use the same timebox in each Sprint (1 to 4 week). According to statement PM wants to put the feature in a separate branch and allow users to test for 1-2 months. Clearly, it's a product delivery from the Scrum team (assuming Scrum team already tested at ...


2

Your team produces a potentially shippable product increment at the end of each sprint. Whether this is then subjected to acceptance tests and actually being released is up to the client. Of course, you split the big feature into product backlog items that can be handled within the Scrum framework so that it will take several sprints until it is completed, ...


Top 50 recent answers are included