agile - In a Scrum project, should testing and peer reviews be worked into each sprint as individual tasks? -


this seems point of contention work. complain lack of verification structure in scrum projects, while scrum purists it's not scrum about. both sides bring great points, see people outside circle subject. thoughts? why?

in scrum project, needs done should entered task.

one of key points of scrum being able accurately predict team can done in sprint. in order this, must account going consume developer's time.

this means things documentation, testing, , peer reviews must taken account tasks.

edit: based on mendelt's post, i'm going clarify things bit.

from wikipedia :

product backlog: product backlog high-level document entire project. contains broad descriptions of required features, wish-list items, etc. "what" built. open , editable anyone. contains rough estimates, in days. estimate helps product owner gauge timeline and, limited extent, priority (e.g. if "add spellcheck" feature estimated @ 3 days vs 3 months, may affect product owner's desire).

sprint backlog: sprint backlog detailed document containing information how team going implement requirements upcoming sprint. tasks broken down hours no task being more 16 hours. if task greater 16 hours, should broken down further. tasks on sprint backlog never assigned, rather tasks signed-up team members like.

items on product backlog not show things documentation or testing, tasks on sprint backlog should.

i'll give example. there "feature a" on product backlog, , estimated time 1 week. on sprint backlog, might broken following tasks:

 initial design document:              4 hours   development of subset 1 of feature a: 8 hours   peer review of subset 1 of feature a: 2 hours   testing of subset 1 of feature a:     6 hours   development of subset 2 of feature a: 8 hours   peer review of subset 2 of feature a: 2 hours   testing of subset 2 of feature a:     6 hours   user documentation feature a:     4 hours --------------------------------------------- total time                           40 hours 

edit #2: idea behind sprint backlog specific humanly possible have spend time. why tasks cannot more 16 hours long , how point can reliable in schedule predictions.

if follow sprint backlog guidelines religiously , make sure include everything spend development time on pleasantly surprised @ how accurate scheduling can after few sprints of practice.


Comments

Popular posts from this blog

windows - Why does Vista not allow creation of shortcuts to "Programs" on a NonAdmin account? Not supposed to install apps from NonAdmin account? -

c++ - How do I get a multi line tooltip in MFC -

unit testing - How to mock PreferenceManager in Android? -