My notes from the Scrum Alliance webinar Essential Technical Capabilities: Four Activities for Successful Incremental Software Development are below. For those coming from a dev background, these all pretty much go without saying.

I’d quibble with the presenter’s assement of first adopting these principles can take “a month.” If you know automated testing well, sure, that may be accurate. If your team has to first learn how to write and run the tests, then it could take significantly longer. Good test writing is every bit as much a skill as good code writing.

Essential Technical Capabilities: Four Activities for Successful Incremental Software Development

https://resources.scrumalliance.org/Webinar/essential-technical-capabilities-activities-successful-incremental-software-development

The Agilist’s Dilemma: doing the right things for agile delivery but it’s feeling painful; complexity of the software and rate of change is increasing and hampering velocity

essential activities

test or behavior driven development
dilligent refactoring
continuous integration
pair or mob/ensemble programming

continuous integration necessary to keep changes small and avoid merge conflicts as individual pieces of work progress independantly

adopting these can take a month as the team first adapts to them