Do we have to completely reimagine how we work? Unequivocal yes.
I'm writing this with my voice-to-text feature on my iPhone as I'm thinking about the next thing I want to develop. I have a couple of hashtags that automatically save this to a smart folder in Notes, which is then picked up by the blogging service that I developed on my own in a couple of days. From there, it takes this idea and — with a fine-tuned prompt — sends it through to a couple of different AI models to polish and present the post that you're reading today.
I'm still automating the process of auto-posting, but I can now take an idea to a published blog post in under five minutes.
How Things Used to Work
This got me thinking. As someone who has been in the technology world — especially around eCommerce ecosystems — for close to 10 years, our process usually involved months of planning: product planning, interviews, and research, which we organized into a backlog and tried to align to quarterly goals and development schedules.
Then we'd have our ceremonies — a couple of hours for refinement, a couple of hours for planning. Once work went into planning, we had two-week development cycles where new work was developed by our amazing talent, tested by another team, and either deployed automatically (if the systems were microservice-architected) or as one big deployment overnight.
How Things Work Now
But with how fast these tools are moving and their capabilities, I can now take an idea into not only this blog post, but I can also open up my Claude Code agent on my phone — which is connected to my git repository. There, I can talk through what I'm interested in, have it research and create a plan document, and commit that to the repository.
From there, I open up the Claude coding agent on my computer, have it read through the plan document, run any number of Claude skills to make sure it's well laid out and constructed, and have it start running and refining the plan. When the plan is approved, it gets to work on the coding and has something for me to review within a matter of minutes — depending on how complex the ask is.
From there, I can run all of the testing, SEO, accessibility, governance, and other agents I've developed to review the code — ensuring that when it's deployed to production, it is fully formed, ready, and won't break anything.
The Garden Office
What's crazy about all this? I can be in the garden thinking through an idea, set my phone up, talk to my agent, and within a matter of an hour have fully deployed, production-ready code. And I am just one person — with a strong understanding of systems from having worked around them for years, but with no prior coding knowledge.
I can't imagine what a team of very experienced people could do with these processes.
Beyond that, there can be developed any number of additional processes — creating architectural documentation, sending out automated summaries of work that's happening, and any number of possibilities that I haven't even considered in my more individual, smaller-scale processes that I'm using to learn and develop with these tools.
Scrum Is Dead (There, I Said It)
So, unequivocally, yes — the ways of work are changing rapidly. Personally, I believe Scrum and that whole process framework developed for the tools of yesteryear (meaning three months ago) are dead in the water. They do not apply to these highly efficient and rapidly developing tools.
While my years of experience have helped me to this point, others coming up in this world will be able to surpass even what I'm capable of in no time. The frameworks that support this new methodology will need to follow suit, because months-long planning and weeks-long development cycles just don't make sense anymore when a product manager who loves technology can do all of this and more while talking on his phone in the garden.
The future of building isn't about process gates and ceremony schedules. It's about having an idea, talking it through with an intelligent collaborator, and shipping it before your coffee gets cold.