20 February 2013

Quality versus speedKwaliteit versus snelheidKvalitet kontra snabbhetQualität versus Geschwindigkeit

About Hugo Messer

Hugo Messer is a Dutch entrepreneur, distributed agile team specialist, and author. He is the founder and owner of Bridge Global, a software services provider, and ekipa.co., an agile coaching agency. He has been building and managing teams around the world for the past several years. His passion is to enable people that are spread across cultures, geography and time zones to cooperate. Whether it’s offshoring or nearshoring, he knows what it takes to make global cooperation work.

2 thoughts on “Quality versus speedKwaliteit versus snelheidKvalitet kontra snabbhetQualität versus Geschwindigkeit
  1. I agree with you that we need to add task for testing.

    Mostly what happens is when we estimate, we give the time that we will take to finish . That means the productive hours. In a day I assume only 6 Hours will be productive out of 8 . That means we have IM, calls and in middle frustrations for things needs to be changed / bugs reported.

    So when small tasks comes in middle, like say 15 minutes . We want to login to Jira , look into the functionality, implement it , test it, commit to server and yes we are not just in 15 minutes sometimes.

    So that means there should be some room for the person to breath :-) .

    And I agree that most people in India thinks we need to finish the sprint . I never thought of moving out from the Sprint for I was also the person who made the Sprint . So thank you for the point that we can move a task to next sprint when we need.

  2. I think the point is that a lot of engineers all over the world, even college educated ones, live and are raised in a culture where you ought to obey your role in an organization at all means.

    So, if you are a programmer you are not a researcher and also not a project leader.

    The scrum master in this article wants to have the best of two worlds. The low fee from the Indian programmer and the flexibility and entrepreneurship from the scrum master.

    And yes, a Dutch programmer would not mind to reuse software from somebody else. But there are cultures who see this behavior as not done (to put is mildly). You pay them fore programming work and that is what they do and deliver.

    So probably, in this situation the scrum master better had hired a Dutch programmer.

    My two cents for today

Leave a Reply

Your email address will not be published. Required fields are marked *