StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<blockquote> <ul> <li>coded</li> <li>unit tested</li> </ul> </blockquote> <p>IMHO these belong together, as both should be handled by the same person (preferably TDD, which really makes it impossible to separate these).</p> <blockquote> <ul> <li>integration tested</li> </ul> </blockquote> <p>In our team, this is usually done by the same developer, so we typically do it as part of the above task. Other teams may do it differently.</p> <blockquote> <ul> <li>commented</li> </ul> </blockquote> <p>Do you mean code comments? Then, to me, this does not deserve a separate task. Otherwise, please clarify.</p> <blockquote> <ul> <li>peer reviewed</li> </ul> </blockquote> <p>A separate task for a separate developer (or more).</p> <blockquote> <ul> <li>qa tested</li> </ul> </blockquote> <p>A separate task for testers / QA personnel.</p> <p>I would add <strong>documentation</strong> - it may not always be needed, but often is. Again, it should be a separate task, typically for the same guy who did the implementation (but not always).</p> <p>One prime concern to practically all the Scrum teams I have been working with so far is to make sure that nothing important is forgotten from the above. Partitioning into distinct tasks may help this. Then you can clearly see in your backlog what's left to do. Lumping all of these into one task makes it easy to forget about this or that little detail. For us, it was most typical to forget about code review and documentation, that was the main reason why we turned these into independent tasks.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload