Integrity Inspired Solutions

It is with profound sadness that we share the passing of Noah Rhee, a valued member of our team at Integrity Inspired Solutions. Noah passed away the morning of November 14th. Noah’s kindness, creativity, and dedication left a lasting impact on everyone who had the privilege to work with him. He was not just a talented developer but also a wonderful person who brought warmth, humor, and thoughtfulness to our company. His loss is a shock and tragedy for all of us, and our hearts go out to his family, friends, and everyone connected to him. For those wishing to pay their respects, services will be held on Wednesday, November 20th at Muelbach Funeral Care, located at 6800 Troost Ave, Kansas City, MO 64131. - Visitation: Noon to 1:00 PM - Funeral Service: 1:00 PM to 1:45 PM Following the funeral, Integrity Inspired Solutions will host an informal gathering from 2:30-4:00 PM upstairs at Maloney's Sports Bar & Grill to share stories, remember Noah, and support one another during this difficult time. We hope this gathering will provide an opportunity for those who knew him, especially professionally, to grieve and celebrate the impact he made on all our lives.

If you want your software team to be efficient, you have to lose the instinct to start projects right away. When someone hands your team an important new project, it can be easy to want to jump on it right away. After all, it's important, right? But the problem is that everything claims to be important, including the project and tasks your team is currently working on. And when you pull people off of current projects to start new ones, all you're doing is slowing everything down and making everyone unhappy. It might seem like telling a stakeholder that you got started right away on their project will make them happier, but they won't be happy when their project takes longer because your team was spread too thin. Remember: We don't get points for starting work—we get points for finishing work. Listen to this full episode at the link in the comments, or find Agile Bites on your favorite podcast platform. #agile #agilesoftwaredevelopment #techleadership #cto #workinprogress #WIP

Wishing you all a safe and happy 4th of July from all of us at Integrity Inspired Solutions! 🇺🇸

In our previous episode, I talked about the importance of visualizing your current work-in-progress to uncover bottlenecks, enhance decision-making, and provide clarity on your team's workload. Now, let's tackle what often comes next: realizing you have too much work in progress. Why does this happen so often to development teams, and what can we do about it? In this episode, I'm diving into strategies to manage and prevent this overload. I cover setting WIP limits, staying responsive, and juggling organizational demands effectively. Tune in to hear how to avoid overcommitting, the perks of prioritizing and finishing tasks before jumping into new ones, and how to use Lean principles to keep your workflow sustainable. Listen to this episode at the link in the comments, or look for Agile Bites on your favorite podcast platform. #agile #agilesoftwaredevelopment #techleadership #cto #cio #WIP

Is your development team slowed down by the number of items they currently have in progress? It's hard to identify what all is in progress when the work is invisible. That's why I highly recommend finding a visualization for your team's WIP. I've worked with many organizations to map out their workflows and WIP, and jaws drop every time when the visualizations reveal how much work is currently in progress. And that's the thing about WIP—the more work items you have in progress, the slower each individual item becomes. That's why visualizing it can be a powerful part of speeding up your team. Listen to this full episode at the link in the comments, or find Agile Bites on your favorite podcast platform. #agile #agility #agilesoftwaredevelopment #techleadership #WIP

When the kind of work we do is invisible (like software development), it can be a challenge to keep track of what work is going on at any given time. That's where visualization can be a great tool for understanding your team's work in progress. Building on last episode's discussion on creating workflow visualizations, in this episode, I explore the importance of visualizing work in progress to uncover current projects in flight and find hidden bottlenecks and inefficiencies. I discuss the pros and cons of common WIP visualizations (lists, Kanban boards, etc.) so that you can decide on a visualization that fits your unique workflow, even if it means thinking outside the box. Episode link in the comments, or search for Agile Bites on your favorite podcast platform. #agile #agilesoftwaredevelopment #techleadership #cto #cio

If you're a dev team manager who doesn't want to make uninformed recommendations to your team, visualization could get you where you want to go. Visualizing your team's workflow does two powerful things: ✅ It turns the abstract journey from “request” to “deliverable” into a tangible process, aligning your team around a clear and shared understanding. ✅ The information-gathering process to build your visual workflow is a great non-threatening way to get information and spark productive conversations Have you tried visualizing your team's workflow? What insights did you gain from it? Link to this full episode of Agile Bites is at the link in the comments, or find Agile Bites on your favorite podcast platform. #agile #agilesoftwaredevelopment #techleadership #softwaredevelopment

A lot of what we do in software development is invisible. If someone is typing furiously on their keyboard, you don't know if they're about to finish that new feature or if they're complaining to their state representative. One of the things that tends to be invisible is the actual process of getting something from “request” to “deliverable.” Everybody kind of knows what that process is, but they typically only know their piece of it, and they probably haven't thought critically about it in years. Creating a visualization of this process can: ✅ Spotlight potential weak points ✅ Improve communication ✅ Reveal the complexities of your team's workflow ✅ Uncover hidden opportunities for optimization In this episode, I'm sharing practical tips for mapping out your processes, understanding team dynamics, and setting the stage for continuous improvement. Listen now at the link in the comments, or find Agile Bites on your favorite podcast platform. #agile #agilesoftwaredevelopment #techleadership #management

You've got big changes you want to make on your first day leading a tech team? Hold on a moment before diving in with solutions and recommendations. When stepping into a new role, it's important to understand the reality on the ground. Many driven and ambitious managers rush in with big plans, eager to mold the operation to the image they have in their heads. They want to add value, and that's the way they plan to do it. But here's the catch—you need context to be effective. 👉 Understand the facts and reasons behind the current situation 👉 Gather intelligence to know what you're dealing with 👉 Recognize what the teams are currently doing and experiencing Before implementing your vision, take a step back, do some reconnaissance, and truly understand the environment you're stepping into. You're laying the groundwork for your improvements to be actual improvements. Link to this full episode in the comments, or find Agile Bites on your favorite podcast platform. #agile #agilesoftwaredevelopment #techleadership #cto #cio

When managing a new team, it's tempting to come in guns blazing with new ideas and changes. Not only can this cause resistance, however, but you might be heading the wrong direction to begin with. Start with Fact-Finding and Reason-Finding before Recommendation-Making. In other words, one of your first moves should be to ask a lot of questions—"why" being one of the most prominent of them. This sets you up for success with your team because: ✅ You may discover there are good reasons for their current practices that are not immediately apparent to you ✅ It lays the foundation for future discussions, focusing on the reasons behind the practices rather than the practices themselves—making the conversation ego-agnostic. In this episode, learn how to create a safe environment to gear up your operations for change and set you and your team up for future success. Episode link in the comments, or find Agile Bites on your favorite podcast platform. #agile #agilesoftwaredevelopment #techleadership #softwaredeveloper