This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
Leaders must embrace these changes, finding ways to maintain team cohesion, productivity, and culture in dispersed work environments. Leading with Empathy and Agility Empathy has always been an important trait for leaders, but in today’s world, it is indispensable. This human-centered approach goes hand in hand with agility.
The agile corporate-learning business model has been getting a lot of attention in recent times. Companies are seeing the benefits of a more agileproduction, design, and even leadership development programs. But an agile model isn’t for everyone. appeared first on Clarity Consultants.
It increases productivity Capacity planning software helps ensure that the right resources are available at the right time and aren’t overloaded. This helps maintain high productivity levels. The solution serves agencies, consultants, IT teams, construction and engineering industries.
Introduction The alignment of employee skills with job requirements is not just beneficial, it is essential for maximizing employee engagement and the resulting productivity. An employee who resonates with the company’s culture and values is more engaged and motivated, further enhancing productivity.
They think that the agile tools they use, such as boards, offer a strategic advantage. However, they adopt or “install” an agile framework or process without customization. Instead, agile organizations need flexibility, not rigidity. Commodity businesses don't need agility for product development.
Several of my clients want to use some sort of maturity assessment for their agile transformations. For agile transformation, an assessment can help people see how they change—how they innovate the products and the culture. These are about the product development behaviors I see in the organization.
As a former consultant, I have a deep and abiding love for the use of 2×2 matrices in business strategy. I’ve begun to view this as the ability to hold two specific traits in balance: consistency and agility. They plan diligently and produce excellent products and experiences for clients time and time again.
As I've been speaking about the Modern Management Made Easy books, people ask these questions: We're pretty good with our agile approach. These people tell me their career ladder doesn't work to enhance agility. Organizations reward people as individuals—but agility demands collaboration. Became a consultant.
So when does it make sense to customize your agile approach to gain a strategic advantage? Example 1: Startup/Small Organization with Few Products. They offer their product in two versions: Pro and Lite. (No They want an agile approach, so they started with Scrum. Let's start with a couple of examples. Others mob.
In Part 1 and 2 of this series, I wrote about how an agile approach might offer strategic benefits. And because an agile approach changes your culture, I said the agile approach was part of your strategy. So let's ask this question: Can any tool—agile or otherwise—offer you a strategic advantage? (I
One of my clients wants to use shared services “teams” as they start their agile transformation. Their developers work on a product for months and years at a time. ” Shared service-thinking denies the reality of effective product development: A cross-functional team learns together as they develop the product. .”
I know it is critical for the leadership to embrace agile, but the sad reality is that I’m not sure our leadership team will start before it’s too late. Rather than debating the advantages of agile teams, why not start demonstrating them? Perhaps my journey to agile will help you figure out how to begin your own.
When I think about agile approaches to work, I think about how fast we can change and the cost of those changes. That's why an agile approach with deliverables every day or week doesn't fit with some kinds of projects, such as events. Here, I assume you want multiple releases for your product.
They think agile approaches are tactics and agile tools are part of their strategy. That's why they want to Buy an agile approach. Worse, the longer they maintain their custom board, the more they spend on that internal product. And the less they have to spend on products that affect the customers.
The managers don't believe the teams need product owners, so the teams don't have POs. The managers (often with the assistance of a consultancy) decided Scrum was the answer. Those outcomes can help teams decide which agile approach(es) to start with and adapt. Let's start with who wants the teams to use an agile approach.
Worse, many of these managers also want business agility. Business agility requires change. Product strategy, to define the value the products offer to the product's users/customers. In addition, you might need these product strategies too: Product architecture, to shepherd the technical value of a product.
Once the team completes that highest priority feature(s), the team can release the product. When we release, we can regroup and figure out what to do next for this product. Fork another product. (I I did this with several Lite vs Pro products using this approach.). Opportunities for More Agility.
That's because each project offers different value over the product's lifetime. See Product Roles, Part 4: Product Orientation and the Role of Projects for images of why we want ever-increasing product value, but why we might space the projects out.) However, today, I realized there are also product risks.
On the ANE panel last night, an agile coach asked, “What's my path forward as an agile coach? Focus on business results, not agility per se. People who facilitate larger efforts, such as product leaders, portfolio managers, and most middle managers, feel the pressure to “deliver” or “perform.”
For example, if your goal is to increase sales, your L&D programs might focus on enhancing sales techniques, product knowledge, or customer relationship management skills. Productivity metrics: Assess changes in output per employee or team efficiency. Output per employee: Track changes in individual or team productivity levels.
Back in Part 1 , I wrote about how stage-gate approaches were as agile as we could use at the time. We had one delivery, so our agility was about canceling the project if we couldn't finish it. ” One of the customers realized he wanted something different—something we didn't expect for this product.
This is because they are better equipped to handle tasks, solve problems, and deliver high-quality work–all of which impact organizational productivity. The more self-assured they feel, the more motivated they will be to work hard, which of course, also increases productivity. The instructional design consultants make this possible.
Strategy and Product Feedback Loops Many of my middle-management and senior leadership clients want certainty about future work. However, I don't do long consulting contracts—by design. But most of my business focuses on coaching, workshops, or consulting. Does that sound like an agile team to you?
Are you trying to make an agile framework or approach work? Maybe you've received a mandate to “go agile.” Or, maybe you're trying to fit an agile framework into your current processes—and you've got a mess. I've seen plenty of problems when people try to adopt “agile” wholesale.
Worse, most career ladders assume we can assess what a person can do, not on their contributions to an agile team. That means most career ladders don't fit agile teams or an agile culture. Instead of individual achievements, we can reward the types of agile leadership we want to see in agile teams.
Daniel Vacanti and Prateek Singh graciously invited* me to be on an episode of Drunk Agile: Episode 37 Johanna Rothman Part Deux More Bigger Aging. Ordering the work by value, even though agile approaches hope the value changes. (Re)defining That's why agile approaches emphasize “finish something and get feedback on it.”
I spoke at Agile 2019 last week. Here are my thoughts and where I think the “agile” industry is headed. Problems I See with “Agile” Here's a summary of problems I saw last week: Too many people think “agile” will solve all their problems. Do You Need an Agile Approach?
Several of my clients have internal struggles about how to internally see the future of the product. The teams want to use an agile approach so they can incorporate learning. The managers might even think this is roadmap reflects an agile approach. There's nothing about this roadmap that's agile. What can you do?
The larger your product, the more likely you have components teams. I often see component teams because of the architecture of the product. In this first image, the Integrated System Program, the rest of the product uses the Platform of Common Services as components. InterRelated Program Product.
(That link just goes to the first post) My most recent book: Project Lifecycles: How to Reduce Risks, Release Successful Products, and Increase Agility. In addition, here's the unedited transcript: Agile _ Adapt – Expert Talk – Johanna Rothman – April 2024 in docx format. I hope you enjoy this one.
More of my clients say they want business agility. Yet, we don't share a common definition of business agility. Actions matter when it comes to business agility. Since managers create and refine the culture, they can create an environment that supports business agility. An Environment that Supports Business Agility.
I see many teams and team members who say, “Agile stinks. ” When I ask people what's happening, they say: We're doing an agile death march because someone else already told us what we have to do and the date it's due. And don't get me started on how coaches tend to do life coaching instead of support for agility.)
What do teams need to know about the product now to focus their work? If I was the product leader, I would write which feature sets and which problems they solve in each of these various minimum boxes. Product leaders need the flexibility to replan. Teams use backlogs for the day-to-day tactical decisions.
They want a single product roadmap to serve all these purposes: Focus the team's work for this specific product for the short term. Show customers where the company thinks the product is headed. The more specific overview of when salespeople might expect new features or new products.). What management thinks they want.
Strategy and Product Feedback Loops. Instead of teams being responsible for delivering product, the managers are responsible for explaining when the managers want to decide. What about product decisions? The product value team might need to see product deliverables at least once a week. Or finish a project.)
I have a new book: Project Lifecycles: How to Reduce Risks, Release Successful Products, and Increase Agility. I wrote it because I'm concerned about what I see in too many supposedly agile teams: Crazy-long backlogs and roadmaps. See Manage Unplanned Feedback Loops to Reduce Risks and Create Successful Products.)
I started this series by discussing why managers didn't perceive the value of agile coaches and Scrum Masters in Part 1, resulting in layoffs.) Then, in Part 2 , I asked those unemployed agilists to review their functional skills, the skills people need to do a product development job well. Especially, Agile is Not a Silver Bullet.
You can do this even if each of you is an expert on various areas or different products when you use flow efficiency. See Who's Playing Agile Schedule Games? ). No More Agile Death Marches. They're able to release more finished features because they're not postponing the work they owe the product.
Let me address a little about business agility and innovation. Business agility allows us to create a culture where we plan to change. Too many people think business agility is about the ability to do more of the same, faster. ” Or mine, “Explore and support effective ways of managing product development.”
I said that when we focus on individual achievements and deliverables, we ignore the agile system of work. Worse, when we reward individual achievements we prevent an agile culture. That's because agile teams learn together as they create the product. Agile Behaviors for Learning and Working Together.
In Effective Agility Requires Cultural Changes: Part 1 , I said that real agile approaches require cultural change to focus on flow efficiency , where we watch the flow of the work , not the people doing tasks. Can you create an agile culture for your team even if you can't change how the organization works? 1,2 and so on.
He thought agile approaches would work to “meet” and “enforce” deadlines. I asked Brad these questions: Do you have product or feature teams that are cross-functional and can release alone? ( Component teams create interdependencies and take much more time to finish work.). Why do you have deadlines?
I was on the Agile Uprising podcast this past Sunday, discussing my most recent book. Some of what we discussed: That managers want agility but do not care about any agile methods or frameworks. While we might think “agile” is another project organization method—or lifecycle—it's not. See (and hear!):
“Data scientists, fast computers, and advanced software are replacing traditional decision-making processes and disrupting tried-and trusted traditional consulting methodologies, with Big Data being one of the main forces of disruption” ( Tras, 2015 ). So, how does big data create value for consulting firms?
We organize all of the trending information in your field so you don't have to. Join 55,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content