Reputation
336
Top tag
Next privilege 500 Rep.
Access review queues
Badges
1 6
Newest
 Editor
Impact
~3k people reached

  • 0 posts edited
  • 0 helpful flags
  • 18 votes cast
Jun
17
revised Early subtasking at the beginning of each sprint
Expanded answer to address some elements more specific to the question.
Jun
17
comment Early subtasking at the beginning of each sprint
We're product based, but the product's features are heavily customer driven (hence the need to be able to plan features further in advance). I think that task breakdowns are very valuable for the kinds of story we use, and adding in the estimates is usually pretty easy (by the point at which you're estimating the task it should take less than 30 seconds to give an estimate and move on). So in that sense, it doesn't cost us productivity - there are some differences between our method and yours which I'll edit into my answer.
Jun
17
awarded  Editor
Jun
17
revised Early subtasking at the beginning of each sprint
added 139 characters in body
Jun
17
answered Early subtasking at the beginning of each sprint
Jan
27
awarded  Informed
Mar
1
awarded  Yearling
Feb
18
awarded  Nice Answer
Feb
18
awarded  Teacher
Feb
17
comment Is having C++ header files without extension a good practice?
@kotlinski In general, I guess that depends how much old code you would be working with, whether it would be viable to change it all to the new convention and what the impact of mixing conventions would be. In this case though I agree with Paul Manta - it's mostly personal preference, with an extension being preferred by most for practical reasons.
Feb
17
answered Is having C++ header files without extension a good practice?
Mar
1
awarded  Supporter
Mar
1
awarded  Autobiographer