In-depth articles that take 5 or more minutes to read.
In my exploration of AI coding tools, I've discovered that while they promise productivity gains, they can also introduce challenges in the software delivery lifecycle. By measuring code quality, batch size, and delivery, rather than just adoption rates, we can gain valuable insights. I share five key metrics derived from GitHub's API that can help teams identify problematic development patterns early on.
In my recent experience, I faced the challenge of creating a clear interface guideline for a third-party platform while dealing with legacy code. By leveraging AI assistance, I was able to streamline the process and produce comprehensive documents for four SDKs in just one day. This approach not only clarified our requirements for potential vendors but also enhanced our project's efficiency.
Today, I successfully converted a code file from Elixir to Node.js, a language I'm more familiar with. I utilized LLM assistance to not only translate the code but also to create comprehensive unit tests, achieving over 90% coverage in just 30 minutes. While I still need to ensure the functionality of the converted code as I address other dependencies, this experience highlights the efficiency of leveraging AI in coding tasks.
In my experience, using LLM chat assistants can significantly streamline the process of creating a project backlog. I leverage their speed to minimize repetitive tasks, organize information, and generate valuable insights, all while ensuring that my team reviews and takes accountability for the final content. Let me share my approach to effectively building a software project backlog.
I discovered that my theater experiences didn't directly prepare me for the corporate world, but they instilled in me a strong ethical framework rooted in empathy and collaboration. I learned to navigate complex team dynamics, respect diverse perspectives, and prioritize well-being in the workplace. My journey from engineer to C-Level executive took time, but it was driven by a commitment to create environments where people can thrive and take risks safely.
I know how daunting it can feel to face a day filled with back-to-back meetings at the end of each sprint. By adopting a rolling wave planning process, my team has transformed our Scrum experience. We dedicate just 30 minutes each day for collaboration, allowing us to clarify and estimate stories efficiently. This approach not only empowers us to make commitments but also enhances our retrospectives, ensuring we continuously improve without the burden of excessive meetings.
In my experience, Dual-Track Agile Product Development is about balancing the discovery and delivery processes. I believe that by pursuing discovery continuously while delivering, we can reduce risks and improve alignment. This approach not only helps us meet immediate objectives but also ensures we create long-term value for our users and stakeholders. It's a delicate dance of creativity and efficiency that I find essential for successful product teams.