Wil Sinclair, a previous head of Zend Framework, has written a new post on his blog discussing “Process Patterns” and coining a new term, hack·le. (You’ll have to visit his blog to get the definition and why it’s relevant.
Wil’s point in writing the post is that regardless of your development methodology, there are some common process patterns we all follow. Good development teams define these and then use them to define their own development methodology.
Pair programming. Daily status meetings. A ‘product backlog’. Test driven development. Various and sundry UML diagrams. Each of these are solutions to common problems in team development. Methodological systems- methodologies, if you will- can be assembled from these basic building blocks. And the methodologies that have become common hackle-hold names are fine examples of these systems.
This is an interesting, albeit short read. Take a moment to click on through and see what Wil is saying. Consider it for a moment and think about your methodology. How does your hackle manage development and can you make it better?