Thank you for taking my reply as serious as i took your post. I think i understand what temptations you have to face. Try to stay passionate about delivering 100% quality. And discipline; IMHO that’s so important…
Keep sharing your thoughts with your colleagues, all thought i have to agree that one learns most by doing and experiencing. And it should be possible to do so.
When your colleagues are not there try contacting them via your website, your wiki, email, telephone or msn. They love you and will help you remember.
Overzealous managers. Ha, it sounds a bit like a oxymoron (words that form a logical inconsistency) :-scroll

Be well!

Thanks for the thoughtful reply.
Some of your assumptions are right, others aren’t.

It’s a fully agile managed project and I am in a cross-functional team, but due to circumstances I was at the customer while the rest of my team where at our offices. So that did leave me to make that particular decision on my own.
The client, as most clients, is somewhat interested in quality, but it’s not the main driver it should be.

As for my lesson learned, I am sure it’ll stick for a while again, but it is always tempting to do something quick without realizing what risks you are taking. I learned my lesson again for a while and I, and probably we all, could use some help remembering.

Which is why I am hoping someone else is reminded of it again before bumping into that particular rock. Or driven to it by an overzealous managers

You share your thoughts and experiences with your colleagues, clients and other interested parties.

I like that a lot. Though i do not understand the technical stuff i understand what happened. I can learn from that.

Because “Een gewaarschuwd mens telt voor twee”: A Dutch proverb that means: Forewarned is forearmed.

But it also makes me curious about some things.

What i understand is, that you and your colleagues/teammembers work with time boxed sprints in which you select an increment of ‘the most important functionality’. The nr. 1 on the clients prioritized list. You choose the content of the increment in such a manner that there is time for analyzing, design, all required testing, review, debugging and so one. You work together in multifunctional teams so you can help, advice and learn from each other.

From the story you wrote i can conclude the following:

“Oeps, you did it again”.

You were not working in a project that was managed agile.

You were not working in a multifunctional team or there were no colleagues around you could ask for advice.

You had to take decisions by yourself and on your very own.

Your client made it obvious that quality was less important than speed.

You are not sure if this experience for you is a lesson well learned. In a while you could forget this. You ask us to please help you to remind.

If these conclusions are true i admire your honesty the more and our benevolence should be your part. And i am sure that help is ‘on the way’.

If these conclusions do not apply an other Dutch proverb comes to my mind: “Een ezel stoot zich in het algemeen geen twee keer aan dezelfde steen’. For our English readers: “In general a donkey does not bump into the same stone twice”. The meaning is “One who makes the same mistake twice (or more) is not that smart.” Knowledge can be acquired; attitude is everything

Keep up the good work.

Mary