Reputation
413
Top tag
Next privilege 500 Rep.
Access review queues
Badges
3 10
Impact
~8k people reached

  • 0 posts edited
  • 0 helpful flags
  • 19 votes cast
Jan
20
awarded  Popular Question
May
10
awarded  Yearling
Nov
5
awarded  Notable Question
May
10
awarded  Yearling
Dec
15
awarded  Popular Question
Aug
1
awarded  Nice Question
Jul
10
accepted Are There Any Examples of Uncle Bob's High-Falutin' Architecture?
Jun
21
accepted How to handle estimates for programmers joining the team?
Jun
20
awarded  Nice Question
Jun
19
comment How to handle estimates for programmers joining the team?
Unfortunately the situation was pretty much that - someone estimated the work then we lost a good amount of manpower. Now new manpower has the tasks that were estimated by old manpower.
Jun
19
asked How to handle estimates for programmers joining the team?
May
11
awarded  Scholar
May
11
accepted Agile - Spikes and the Overall Timeline
May
10
comment Agile - Spikes and the Overall Timeline
Sounds reasonable. I guess my question then would be given this viewpoint, what is the purpose of a spike, and when should they be used?
May
10
comment Agile - Spikes and the Overall Timeline
Oh sure, I understand the value of estimating in terms of relative complexity as opposed to hours. The part I'm confused about is if this approach were correct for the situation I've described, it would seem that spikes wouldn't ever be used on any project (the devs would just say "eh, that seems like a 3, this seems like a 5", even though nobody knows anything about integrating with the Fizzbot System)
May
10
comment Agile - Spikes and the Overall Timeline
I think in this case they have to be spikes, because nobody on the team has ever worked with the Foo Payroll system, XYZ89 files, or the Frobnobdicator before. We have no idea how long integration with those systems will take.
May
10
awarded  Supporter
May
10
asked Agile - Spikes and the Overall Timeline
May
10
awarded  Teacher
May
10
awarded  Student