How Programmers Lives Change• We write tests before code– I can’t just go write something and fix itlater• We refactor constantly– I have to accept that my code isn’tperfect, and it never will be• We Pair Program– I have to share my intellectual activitywith someone else• We communicate constantly with ourcustomer– I have to drop the idea of the “Luser”and look on all ideas as good ideas• We are part of an integral team– Sometimes I have to work on thingsother than writing code.• There is really no such thing as “mycode” anymore
Tester Stereotypes• They’re only testers becausethey couldn’t code• Man, these guys are anal!• They have a pathologicaldesire to find problems withthe code• They don’t know when to letup– Good enough is just nevergood enough
How a Testers LifeChanges•Tests are not “What Comes AfterDevelopment if We Have Time But WeNever Have Time”•We need to identify and write testsearly and often•Automation baby, Automation•The relationship of acceptance teststo requirements needs to be tight.•Relationship between programmersand testers is tighter•Collaboration over confrontation•Entering Defects is not enough•We are finally being recognized andutilized as a vital part ofdevelopment, not just a gatekeeper
Big Changes Ahead•Our Job title may actually go away•That doesn’t mean the job does•Deeply integrated into the “inner circle”•Story development is very different from what we are used to•We have to be communicating constantly with the programmers and testers.•We are actually encouraged to make changes now
Project Manager Stereotypes• Slaves to the schedule• Don’t really understandhow hard software is.• Want me to spend allmy time “updatingstatus”• Man, and I thought thetesters were anal!
Project Manager Changes• Where is the new jobthat fits our role?!• We may be asked tobecome Scrum Masters– An *extremely* differentview of a project• I’m still being asked toensure a project will beon time• Focus on scope insteadof time…feels weird