We had a short discussion in the office about my post about the difference between Scrum and Integrity.
The discussion was:
“I don’t understand, there is no difference, we do exactly the same things in Scrum and in Integrity. The Customer will know after the sprint what we managed to do.”
This is exactly the difference. The customer will know only AFTER the sprint, when there is nothing left to do except find excuses why we didn’t meet our commitments. I must point out that scrum and integrity don’t clash and they work together well. But the focus is altogether different. Scrum is about how we, the pork-developers, can perform in a complex and changing environment. The customer/manager can come into our den and look at the Burn-Down Chart (What?! you don’t know how to read it?), and know where we are. That is their responsibility, not ours. Leave us alone to do our jobs.
Integrity is about responsibility. We know that you will do your best to get the job done. But we can’t afford to wait until the end of the sprint to tell the customer, “Sorry, we are developers and we did our best”. This doesn’t cut it. Excuses are cheap. Be a man and tell everyone involved that we won’t make our commitments as soon as you can. (Yes, I know that you still believe that in 5 hours you will be able to finish 50% of the tasks, but in reality you know we can’t)
Guess what, once you start doing that, your managers and customers will be able to make a decision in time, and that will allow them to help you, You the developer to keep your commitments.
This is the reason that we don’t allow to warn about ‘not making it’ a day or two before the deadline, we have to get the warnings way before, that will allow the customer and the management to help reach our goals.
The astute reader will notice that using Scrum, the customer/manager must poll the development team while Integrity is an event-driven process. We all know that polling wastes more time and energy then event-driven systems.