Stack Exchange Network

Stack Exchange network consists of 175 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.

Visit Stack Exchange
The results are in! See what nearly 90,000 developers picked as their most loved, dreaded, and desired coding languages and more in the 2019 Developer Survey.

New answers tagged

0

No, it does not state how oft you need to test/ roll out build on test environment. Increment can be marked as "Done" only if it has been developed AND tested AND covered acceptance criteria. It depends from involved people, how many cycles you will need to get there. Some will be done with 1 or 2, other can take 10-15. I suggest you as well to read Scrum....


2

There is nothing about story points or scrum that makes assigning story points to something impossible or even difficult, unless you have massively altered the definitions within your own process. Story points are an estimate based on complexity, with only a vague relation to time. In most times story points eventually become more time based which makes ...


0

The Scrum Guide only talks about ensuring that, at the end of the Sprint, there is "a "Done", useable, and potentially releasable product Increment". However, there is also nothing that precludes creating such a Product Increment more frequently than once at the end of the Sprint. If your team or organization states that, for a Product Increment to be ...


0

The official guide gives no guidance about building OR releasing. The guide is very carefully written to only proscribe behaviors that are core to Scrum, and to recommend a few others, and to leave the rest of your process up to you. This is what it means when it says it's a "lightweight" and "a framework". One similar place teams seem to get confused ...


2

As Thomas correctly stated, your process isn't the least bit related to Scrum. I can offer 2 approaches to improve your process: Take any existing methodology (like Scrum, for example), and try to implement it. Only by actually implementing it will you really learn why any methodology does things in certain ways. To implement an existing methodology, you'...


1

In our team we don't have dedicated Scrum Master so one of the developer is playing the role of SM. I know this is wrong This is not against scrum. That's a misconception. Some agile founders have even advocated for the SM duties to rotate through members of the team. but it can't be changed. This is against scrum. The whole point of the retrospective ...


1

There is one main thing which I think will solve your issues. Break your stories up into Task's and dont pre-assign Tasks to developers Tasks should not be longer than 1 day Agile works best with very clear requirements for small simple jobs. If you can make your sprint consist of lots of little well defined jobs then you will zoom through them and any ...


9

My first suggestion would be to fix your terminology to improve communication, both internally and externally. You are using terms like "Scrum Master", "Sprint", and "Sprint Review". These are terms from Scrum. Scrum is a well-defined process framework with specific roles, responsibilities, events - it has rules and those rules are defined in the Scrum Guide....


3

In Scrum, all of the requirements (and all other changes needed to the product) are maintained in the Product Backlog. The Product Owner is ultimately responsible for the content and ordering of the Product Backlog. The Scrum Guide is light on guidance for multiple teams, but there are lightweight scaled Scrum frameworks such as Nexus (from Ken Schwaber and ...


Top 50 recent answers are included