[bind10-dev] R-Team Task Estimates

[Stephen Morris]

R-Team Members

Task Estimates
==============
First off, the task:

"Merge tickets #393, #401 and #402 back into #327"

... has been removed as I have been informed that it is complete.  Apologies for the confusion.


I have the five estimates for the tasks we identified at the sprint planning meeting yesterday.  The figures below (where multiple figures are given) are in the order Stephen, Likun, Jelte, Ocean, Michal:

Refactoring: put in library for DNS services
Estimate:	5	?	5	5	5
Consensus: 5
			
Review of All Tasks related to #327				
Estimate:	5	3	8	5	2
Ranges from 2 to 8 - need to discuss this.

Merge #327 back into trunk
Estimate:	1	1	1	2	2
All agree that this is a short task and the 1's just have it.
Consensus: 1

Demux: design phase 1
Estimate:	3	5	3	3	1
The consensus seems to be 3, the two dissenters not being a long way from that estimate.

Demux: design phase 2
Expanding Evan's thoughts into a more detailed   design.	
Estimate:	3	3	8	5	2
A more even distribution.  Need to discuss this.

Ticket #408: General Control Logic/Logic to Handle NS and A Queries
Estimate: 3
			
Logic to update RTT
Estimate: 8	
		
Address Selection Logic/RTT Banding
Estimate: 2
			
Add basic support for addressing individual list items
Estimate: 3	
			
Fix bindctl printing of config data
Estimate: 5
		
Recursor Cache: Requirements
Estimate:	5	13	8	5	2
Quite a spread - need to discuss this.

Recursor Cache: API Design
Estimate:	5	5	8	5	2
The 5's seem to have it (the score of 8 being the next one up from 5 so perhaps in the margin of error)

Recursor Cache: Test Code
Estimate:	5	8	8	5	8
Close, as there is no available score between 5 and 8.  The 8's have it.
Estimate: 8

Outline design for Recursor processing logic
Estimate:	5	5	13	5	1
Quite a spread - we need to discuss this.

Logging: Requirements
Estimate:	2	5	5	3	3
A more or less even spread, so I suggest using a consensus value of 3.

Logging: API Design
Estimate:	2	3	8	5	2
A spread here from 2 to 8, skewed to the lower end.  Can we discuss this?

Logging: Test Code						
Estimate:	5	5	5	5	5
Consensus of 5

			

Bugs
====
In the meeting we agreed that an aim of future sprints would be to tackle the backlog of bugs, at the rate of five bugs per team per two-week sprint.  Jeremy has sent me a list of bugs and for the R-Team I've taken the first five.  These are:

http://bind10.isc.org/ticket/390
easy task to remove unused configuration

http://bind10.isc.org/ticket/85
bug was fixed, needs a unit test

http://bind10.isc.org/ticket/202
needs to complain about unknown configuration

http://bind10.isc.org/ticket/226
running msgq from source tree should set environment variable to choose 
socket file

http://bind10.isc.org/ticket/229
bind10 should report the exit status of the dead child


Could you please do an estimate for these as well.  Although they are fairly simple, they are tasks that form part of the sprint.  I would like to have the estimates so that at the end of the sprint I have a better idea of how many "estimate points" we have got through.

If possible, I would like to extend tomorrow's scrum call by 10-15 minutes to discuss the variations.  I don't think we need to spend too much time on each point - really to understand any concerns to see if we have missed anything.

Thanks

Stephen