Hamilton Road Agility

Author: john crider

  • Why I’d Be Thoughtful When Adding a Junior Developer to My AI Team

    —

    by

    john crider
    in

    Part 5 of 10: The Team Dynamics No One’s Talking About I’d figured out how to work productively with Claude. Two-hour sessions. Clear role separation. Session retrospectives. Code review. Verification checklists. My Pomodoro timer was coming together. Features worked. Tests passed. I was shipping code regularly. Then I started thinking about what would happen if…

  • The Bug That Claude Fixed Seventeen Times (But Never Actually Fixed)

    —

    by

    john crider
    in

    Part 4 of 10: When Metrics Became Documentation Theater I was making real progress on my Pomodoro timer. The UI looked clean. Features were coming together. My two-hour work sessions were productive. Then I hit a bug in the timer display. Claude claimed to fix it. I tested it. Still broken. “Fixed,” Claude said again.…

  • The AI Told Me I Was the Problem (It Was Right)

    —

    by

    john crider
    in

    Part 3 of 10: When Your Copilot Becomes Your Coach A couple weeks into my agentic AI journey, I’d learned what didn’t work: I was running out of things to blame. Then Anthropic released an update to Claude. I opened a new conversation with fresh hope and made an unusual request: “Be skeptical. Question my…

  • The Week I Thought I’d Solved Software Development (I Hadn’t)

    —

    by

    john crider
    in

    Part 2 of 10: When Everything Worked (Until It Didn’t) I spent some time believing I’d discovered the holy grail of software development. It was after my “five minutes to a web app” moment with Claude Code. The time when every lunch break turned into a private hackathon. The time I seriously considered rewriting how…

  • My AI Wakeup call

    —

    by

    john crider
    in

    Part 1 of 10: When AI Stopped Being Theory and Started Being Real I’ve taught software development to over 600 students a year at Columbus State. I’ve coached engineering teams at fortune 500 companies and governmental agencies. I thought I understood where technology was heading. Then a colleague showed me what he’d built in a…

  • Getting To Done

    —

    by

    john crider
    in ,

    Introduction There is a big focus on “Done” in Agile. Instead of answering what we mean by Done or why done is so important, I will focus on common mistakes I see teams make around the concept of “Done.” Before I worked on Agile teams, I thought I knew what done was. It seemed obvious…

  • The Daily Standup

    —

    by

    john crider
    in

    Introduction The Daily Standup is an integral part of professional Scrum. My experience and thoughts on the standup have evolved over the years. I used to think it was a way for the team to understand what was being worked on and start conversations around challenges before they got large. Now, I see it more…

  • My Audience

    —

    by

    john crider
    in , ,

    I wanted to write a message about some terms you may see in my writing. It is likely that you will see me use terms that can be found in the Scrum guide. You can find a copy of the Scrum Guide at https://scrumguides.org/. It is not necessary to have this guide memorized, but it…

  • My Current Thoughts On Scrum

    My Current Thoughts On Scrum

    —

    by

    john crider
    in ,

    I have been working with Scrum teams since 2009. I had no training but needed to find a way to help my team produce more value for our customers. I had just built a continuous integration process for a team of 9 folks. With this one change, our teams incidents after release were reduced by…