New answers tagged

0

Identify base stories. It is very important to identify one or multiple base or reference story against which you would do relative sizing of the backlog. This story is picked from current product backlog or a different story which we have done earlier. But what is important is the understanding of this sory is same among everyone on the team. Team should ...


0

Firstly unlike traditional methodologies where the QA estimate may be separate to the developer estimate, when working in an agile way you will want your software testing estimates to be combined with your developer estimates, producing one estimate per user story. The most common way to do this estimate is using story points where your estimates is a ...


3

My team struggles with a similar issue having multiple input streams, that are running on different iteration/sprint cycles into a common product. We tried testing in the dev int area for each team for a while and then marking items done at that point, but we quickly discovered that was too early in the process. We could verify that new functionality was ...


14

Define a definition of done that includes testing. Define which testing effort is minimal needed to get the work done. Time boxed exploratory testing session for each story, just after coding is done or even during the coding sessions, pair with developers to test their work Good balance of UI-, Service- and unit-tests, read about the test pyramid ...



Top 50 recent answers are included