George C Blog

 For my 5th Software Process Management blog, I reviewed “There’s got to be a better way: your guide to process improvement” by Lauren Moon This blog post on process improvement frames process work as a disciplined, iterative activity that blends feedback, metrics, and small experiments to make teams more effective. The post defines process improvement as intentionally evaluating workflows and tools, collecting feedback from stakeholders, and running incremental changes (experiments) to remove friction and increase value delivery. It surveys concrete tactics, mapping workflows, identifying pain points, prioritizing improvements that unblock flow, and measuring outcomes, and shows how familiar Agile practices (retrospectives, small batch sizes, and continuous feedback) fit into a larger process-improvement lifecycle. The article stresses that process improvement is not a one-time audit but a cultural habit: document existing flows, try minimally invasive changes, measure results, an...

 For my 4th Software Process Management blog post, I reviewed “Continuous Integration” by Martin Fowler.  Martin Fowler’s long-form blog on Continuous Integration lays out the practice as a cornerstone of modern software process management: developers integrate small changes frequently into a shared mainline, and each integration is verified by an automated build and test suite so integration problems are discovered early. Fowler explains the motivation (which is reducing integration hell and long rebasing cycles), the mechanics (frequent commits, automated builds, fast tests, and a visible build status), and practical patterns and anti-patterns that teams encounter when adopting CI. He walks through how CI reduces risk by shortening feedback loops, how it supports other practices (like trunk-based development and test automation), and common traps, slow test suites, poor branching strategies, and insufficient test coverage, that blunt CI’s value. The piece mixes concrete prac...