Reflection 2¶
How This Reflection Works
Below is a question bank. As a team, look through the questions and pick two or three that connect to what you experienced during the second build sprint. Discuss them among yourselves. There are no wrong choices; pick the ones that spark the most interesting conversation for your group.
-
You added automated tests to your application. Did the tests catch anything that manual review missed? Did writing tests change how you thought about what you were building?
-
Think about the autonomy slider: human-in-the-loop versus human-on-the-loop. For the software your team built today, where would you set that slider? What factors drove that decision?
-
Quality gates prevent untested or insecure code from shipping. What would it take to adopt that practice on a real project in your organization? What barriers would you expect?
-
AI can produce code, features, and prototypes faster than ever. But output is not the same as impact. How do you make sure that what gets built fast also gets built right?
-
Today you learned that specialization still matters, even when everyone can build. Where does deep expertise matter most in your domain? What kinds of judgment can AI not replace?
-
Think about a real project or system in your organization. If you applied the practices from today (user stories, context files, automated tests, quality gates), what would change? What would stay the same?
-
The Lesson on human judgment introduced the idea that reversibility and consequences determine how much autonomy to give AI. Can you think of a decision in your domain where getting that balance wrong would matter?
-
What is one practice from today that you could bring back to your team next week? What is the smallest step you could take to start?