New answers tagged

1

You should talk about this in your retrospective (or whatever regular process your team does to inspect and adapt), and come up with a solution that works for you. You already aren't doing "pure" scrum because you are doing design work in your standups. That's perfectly okay. Keep adjusting your process based on feedback. The way I see it, you're really ...


10

It sounds like you are at the extreme thresholds of Scrum. According to the Scrum Guide, a Development Team that has fewer than three members has less interaction or doesn't need as much interaction as a slightly larger team. Therefore, you may not see benefits from using the Scrum framework in a way that slightly larger teams would. It also sounds like the ...


3

I'm going to lean towards breaking it down. Yes what they asked for is all of it and they might not find any final use for the parts. I like to break it down anyway. Here why: At the end of every sprint you show something. That something might be a miserable failure but you show it when you're supposed to show it. That showing gives them some idea where ...


7

I see two possible options. First, don't break down the item. In this case, the work item (the story, ticket, whatever) represents the minimum valuable delivery of the work and can be estimated by the team and worked on. The team may break this out into subtasks (either in a tool or informally) and work on it, but the work is tracked at the level and is ...


1

It's very tempting to answer your question with "it depends", since that's the answer to many "should I...?" questions. In this case, however, the answer is no. You should not create a sprint test plan. At least, not a formal one. The only test plan you need for a sprint is "verify that every completed story is well tested". As a QA engineer on a scrum ...


Top 50 recent answers are included