In an attempt to speed up our development process, my teammates and I took a somewhat controversial route – we introduced pair programming. And it worked.
The term was coined by Ward Cunningham in 1992. at the OOPSLA conference [1] as a metaphor for developing a software asset. He concluded that the development process leads to new learning, as it depends upon artifacts he coined as technical debt.