This post is a continuation of the implementation of the Learning Management System application demonstrating my concept for the new team structure and process in the age of AI-driven development.
In the first post of the implementation series, we created a requirements document with the whole team and Claude Code. In the second post, the whole team, using Claude Code, created a backlog of tasks from that requirements document and uploaded it to Stride. The entire process and team structure is outlined in the post titled “The New Team.” If you haven’t read the initial post, I recommend you do so before reading this one and follow along with the implementation via the links at the bottom of that post.
In this post, we continue to show how the process we outlined in the post The New Team works. If you haven’t read the initial post, I recommend you do so before reading this one.
In the previous post, we created a set of requirements for the Learning Management System. In this post, we will turn that set of requirements into a backlog of tasks that we will use to build the system.
In this post, we start to show how the process we outlined in the post The New Team works for a real application. If you haven’t read the initial post, I recommend you do so before reading this one.
This step is performed by the Product Owner and the Developers. Both are involved because knowledge of the business requirements as well as the technical details of the application is needed in order to create a complete set of requirements.
