Tag Info

New answers tagged

0

First, I think that the use of the term "bug" is a bit off. There are some questions here on Programmers about this (1, 2, 3). Generally, the word "bug" refers to a defect in code. The software does not do what we expect - it crashes, it produces incorrect results, or something along those lines. I prefer to use the word "defect", and this other answer ...


1

My experience; Although there is a 'bug/defect' object in RTC (the collaboration tool used to capture user-stories in my workplace) for the most part my associates tag everything as a general 'task', regardless of whether it can be considered a bug (or group of bugs) or a non-bug task. We do have a Trac-style tool to keep track of the discovery and ...


4

Scrum doesn't really care about the type. A Feature, story, bug, thing, item, use-case... Anything can live on the product backlog. So it doesn't really matter what you call them. The items on the top should have a decent enough level of detail so you can forecast as far as you need and so that the scrum team knows enough to start the work and be ...


0

You quoted the Wikipedia article out of context. It actually says: The Controller pattern assigns the responsibility of dealing with system events to a non-UI class that represents the overall system or a use case scenario. A Controller object is a non-user interface object responsible for receiving or handling a system event. A use case controller ...



Top 50 recent answers are included