Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Passing deadline with only two days, taking your problems into acount, sounds ok to me.

    The sprint is what worries me, but sometimes sprints are necessary and as long as they do not last throughout the entire project or more that a few nights its ok. You should be carefull not to end in a sprint by the end of next iteration.

    Your thoughts on team sizing seem to be in line with my ideas of some of the good things, 4-5 people teams seem to be the right size and 4-5 people can accomplish alot, they can communicate orally and very fast and knowledge and understanding can propagate very fast and decisions can be made very fast.

    What was the primary reason that the cooperation with a consultant broke down:

    of-site?

    expectations?

    agenda?


    What did you do up front to set your delivery date for first iteration?

    How did you cope with wearing two hats team-leader/developer?

    • Two days late is almost ok for a four week iteration with no slack. But it was a tough decision to delay the delivery. That's another lesson: see the truth and take the consequences, before rather than later. That way you have more time to deal with it.

      Regarding the sprint, I'll revise the iteration plan with the delay in mind and with the intention of actually making it without overtime. It actually exhausted us in a few days. I can't imagine doing that for a week, let alone a year like some Marathon Marc