Many product teams fall into the trap of fixating on the work they need to do and forgetting about the impact their work is supposed to have. When that happens, the work often doesn’t produce the desired result. When you work as part of a product team, five questions can help you to avoid this trap by re-focusing on the customer problem you are trying to solve – and why.
Most people and organizations want to have an impact. They don’t exert effort for no purpose; they want to accomplish something. Waste – spending time and energy on things that don’t contribute to an outcome you want to create – gets in the way of that. Wasteful activities reduce our personal and organizational effectiveness. Waste comes in many different forms, and one of the most pernicious is task switching.
Your meeting should have a purpose, and everyone in the meeting should agree on what it is.
This is the most common advice that I give people when they ask how to make their meetings more effective. It’s also one of the most powerful.
Many people are working from home at this point and this will obviously continue for a while. Many organizations had already been working remote. I’ve worked on a number of remote teams and with a number of remote organizations well before the current situation we are in. I’ve done remote work as a coach, trainer, product manager, and team member well before the current situation we are in. Each of those instances I found myself enjoying some aspects of the work and also wishing for aspects to be in person. One of the most challenging things to do remotely is to listen.
The history of lean and kanban is a challenge to boil down, so inevitably, I know there are aspects that are missing here. The title says “short” because, while there is a lot of information here, it is short in terms of how more is out there! Additionally, there are often disagreements on certain aspects and points around the history, and we’ve sourced the various elements included in this outline. A key part of understanding kanban is going beyond the principles and practices, to understand what is behind it work. The history points us to a critical key.
The kanban principles we use and I mention in What is Kanban? are fairly straightforward, yet often ignored in organizations who say they are doing kanban. I want to dig into a bit more depth on each of the principles, for those are are less familiar with them (or perhaps even for some that are).
This is a common question, since Kanban can have several word uses and meanings in the agile space. The term gets thrown around a lot, making it even more confusing. In order to understand Kanban and where it comes from, let’s start with some basic definitions and the foundations. We start with the basics, because there is often confusion around what kanban is.
Simple definitions of kanban:
I hear these requests all the time. “What are the best agile metrics?”, “How can we measure an agile team?” and “I know we can’t just measure agile. . . but, what should be on an “organizational agility checklist?”
There are so many places you can go with these questions and there are even various companies selling ways to measure agile organizations and agile teams. When someone asks me about agility checklists or agile metrics, I tend to start with a few core themes of elements. I use these themes to have conversations with the people who want the measurements and the people who will be measured (before anyone starts using them).
We have done a huge disservice to leaders and managers, as well as teams. There are plenty of people that will say we don’t need managers and leaders. People can lead themselves. While there is an aspect of this that may be true, there are a lot of steps to get close to that idea.
This article will explore what leaders and managers need to do to succeed as they get started with agile or to help teams move from individuals to a team or even a high-performance team. It builds on Agile Leadership Myth #2: Self-Organizing Teams Don’t Need Any Help.
Self-organizing teams do need help. Self-organizing teams are not instant, automatic, or magically created, despite what is often implied. There is a process to become this type of team, and it is rarely, if ever, a straight line. The help they need differs from more traditional directive assignments and task management.
To unravel this myth, we must look at what self-organizing means, what teams and managers experience, and what you can do to shift your help to a more ROI-friendly approach!