>since I plan to end our first iteration try on the next Friday (4th) and
I'm
not very comfortable with the things we achieved so far, I would like to ask

for further feedback here... In the end everything showed up green and I was
happy
...From my point of view I have not been successful in this area when
looking at the Fixture code I produced during the last week. Organisational
we
reduced the scope of our iteration, since we could not make that good
progress
as it would like to have.

>Therefore I have a 1:2 situation and I'm not that happy on the success I
have
met during the last week. I hope I can smooth out to meet at least the
technical success needs, which I would like to have by the next Friday, but
unfortunately I'm currently not that convinced about that.

If you're not sure, one thing you could do is to give yourself a little more
time; or subdivide the tasks; or collaboratively delegate the tasks; or some
combination of all three.

>Maybe it could help to get to know, what we have been doing wrong and how
to react on this in the
next iteration planning. Hopefully someone from this list can give me more
feedback on this.

Well, I for one am shocked, shocked to hear that someone didn't get exactly
what they wanted the first time they tried something.

Why do we call this work development? It isn't just about writing programs;
it's about developing projects, and developing people, and developing
skills, and developing models, and developing understanding. Development of
anything is rarely linear and often unpredictable. When you learn
something, you greatly increase the value of any failure that you might
encounter.

So instead of focusing the fact that you failed to get exactly what you
wanted, consider what you could learn from the experience.

---Michael B.