Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>It is just about impossible to force your ideas on other people and have them be accepted. You can use your own methods and perhaps others will want to learn when they see good results. Are you just expecting these things like TDD, pair programming, etc. to magically reap benefits? </p> <p>You also don't point out your role. (or at least I didn't find it)</p> <p>You might try a different tack:</p> <p>Offer a lunch time seminar about TDDor nunit. Show the benefits as you see them. Provide REAL examples and real benefits to developers/the company. Without those you will not have a receptive audience. </p> <p>At least you have people who wrote their own test harnesses - that is a good thing. I would praise that and ask to see more of it.</p> <p>Ask the developers what they see about the issue and what kind of testing they want or how the company can improve. You have to stop imposing your ideas and let it come from them.</p> <p>EDIT - from experience</p> <p>Years ago I had a similar experience. I had read many books about process and The Right Way To Develop Software (tm) and proceeded to tell everyone I saw about the right way to do things... No one wanted to hear it. I realized that I ran the risk of being marginalized was not really getting anything useful accomplished. So I just shut up and implemented some good practices in the group I was just given leadership of. After about 4 months people started asking <strong>us</strong> how we were getting the results we were delivering. </p> <p>Instead of seeking out others people came to find us. (that wasn't my plan, but in retrospect it makes sense. People want results, not hot air)</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload