Meet the team behind CircuitTrakGary’s the founder and CEOAna and Ryan are the lead engineersLate nights and weekends lead to code problemsXP brings a mindset that helps the team and the codeIterative development helps teams stay on top of changesXP teams use stories to track their requirementsXP teams plan their work a quarter at a timeXP teams use one-week iterationsSlack means giving the team some breathing roomCourage and respect keep fear out of the projectVenn MagnetsVenn Magnets Solutionthere are no Dumb QuestionsTeams build better code when they work togetherA whole team is built on trustTrust means letting your teammates make mistakesXP teams don’t have fixed or prescribed rolesTeams work best when they sit togetherXP teams value communicationTeams work best with relaxed, rested mindsLeave yourself enough time to do the jobLet yourself make mistakesGet rid of interruptionsWork at a sustainable pacethere are no Dumb QuestionsQuestion Clinic: The “which-is-NOT” questionXP teams embrace changeFrequent feedback keeps changes smallBad experiences cause a rational fear of changeXP practices give you feedback about the codeXP teams use automated builds that run quicklyContinuous integration prevents nasty surprisesThe weekly cycle starts with writing testsAgile teams get feedback from design and testingWireframes help the team get early feedback about the user interfaceBuild spike solutions to get an idea of a feature’s technical difficultyUsability testing means testing your user interface on real usersPair programmingthere are no Dumb QuestionsComplex code is really hard to maintainWhen teams value simplicity, they build better codeSimplicity is a fundamental agile principleWhen units are tightly coupled, it adds complexity to the projectIt’s tempting to sacrifice simplicity for reusabilityEvery team accumulates technical debtXP teams “pay down” technical debt in each weekly cycleIncremental design starts (and ends) with simple codethere are no Dumb QuestionsExam QuestionsExam Answers