My post proposing a structured plan-do-check-act prompting cycle in code generation was featured in the Agile Alliance newsletter today.
Originally published on LinkedIn on Aug 25, 2025. Enhanced for this site with expanded insights and additional resources.
I have formalized my approach to LLM code generation into a Plan-Do-Check-Act cycle. By analyzing the problem, planning with clear agreements, coding with oversight, checking for completeness, and reflecting on the process, I ensure discipline in my work. This method not only helps me stay on track but also creates valuable artifacts for my team.
My answer to the lawn dart of a question, “should scrum master be a fulltime role?”…
A full throated consulting, “it depends.”
Saying a team is running Scrum and has a Scrum master is data without information.
Is the team proficient and performing? Is the scrum master a capable coach or just a facilitator/project manager. Does the org invest in learning, team leadership and continuous improvement?
It’s like a sport where most teams aren’t allowed to practice, don’t field all the positions, and are coached by an office admin. Then asking if that coach is necessary.
What value are they creating, what harm are they creating, what outcome does the team and org need, and can they learn and adapt?
Existential Joys of Agile Practice - Revisited. Text of my pecha kucha at #agileday2011 for #agilenyc http://jkat.me/pNcdrM