About the schools of thought around how to better develop software.
This is near and dear to me, as I spent the first several years of my career at the consulting arm of Pivotal - Pivotal Labs. Where we worked with clients to try to help them get better at writing software. I definitely drunk the kool-aid in a way that’s still affecting me today.
The basic idea behind Extreme Programming (usually abbreviated as XP) is to take the good parts of older software engineering practices and take them to “extreme” levels. For example, from wikipedia: Code reviews are good, why not do them all the time? i.e. pair programming.
Pivotal came up with a variant of Extreme Programming they called the “Scaled Agile Framework”. Despite the corporate name, it’s fairly good and something I’m comfortable with.
- Extreme Programming Explained is the primary/default resource on XP.
- The Art of Agile Development. A bit dated, though.
- Matt Parker’s book on Pivotal’s practices.
- Extreme Programming Pocket Guide is “basically the Cliff’s Notes/Spark Notes for the 1st edition of [Extreme Programming Explained] - which is far more dev-centric than the 2nd which has a lot more Product Owner stuff in it. [It] is a good way to introduce a lot of the HOW and justify it in terms of the values.”
Last updated: 2020-04-30 11:22:49 -0700