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
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. It's time for performance reviews.
We often hear that agile is a mindset. That we need to change our thinking to use agility. Our culture defines our environment. Define Mindset, Behaviors, Culture. We need behaviors if we want an agileculture. The culture is a combination of: How people treat each other. Is that correct?
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. Part of what might not work is the culture. (Is Is agility even possible?)
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.)
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.
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. What about those cultural changes? This is not an agile approach. 1,2 and so on.
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
So when does it make sense to customize your agile approach to gain a strategic advantage? They want an agile approach, so they started with Scrum. We don't think we need to be “religious” about our agile approach as long as we get the benefit. Then, they Built their agile approach based on their needs.
They think agile approaches are tactics and agile tools are part of their strategy. That's why they want to Buy an agile approach. Not realizing a standard agile approach is an oxymoron. Teams need to experiment and change their agile approach. Address the cultural changes necessary for agility.
One of my clients wants to use shared services “teams” as they start their agile transformation. Agile approaches break the idea of a “shared service” model of people. I don't know of any way to keep “shared services” and move to agile approaches. ” Don't use an agile approach.
Ron Jeffries, Matt Barcomb, and several other people wrote an interesting thread about prescriptive and non-prescriptive approaches to team-based agile. If you don’t want to read the entire thread, here is a summary: People often need help with their agile approach. That’s why we have the agile values and principles.
See Behaviors Create an AgileCulture with Johanna Rothman. We had a delightful discussion on Behaviors Create an AgileCulture with Johanna Rothman. The post Behaviors Create an AgileCulture with Gregory Miller appeared first on Johanna Rothman, Management Consultant. And much more.
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. Culture requires management involvement.
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.) That's why I then asked people to review their product-oriented domain expertise and agile-focused domain expertise in Part 3. Especially, Agile is Not a Silver Bullet.
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. Opportunities for Agility. The iterative lifecycles offer agility anytime you get feedback from a customer (or a manager).
I had a terrific time with Chris Williams on his Badass Agile podcast. How managers need to collaborate to achieve agility. The post Enlightening Conversation on the Badass Agile Podcast appeared first on Johanna Rothman, Management Consultant. We discussed the Modern Management Made Easy books. We had a terrific discussion.
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. Who Wants the Teams to Use an Agile Approach? Before I had the “agile” word, I discussed iterating over feature sets and delivering small increments. Oh, please.
Instead, I see assumptions that reveal a divide-and-conquer, and possibly a command-and-control culture, not an agileculture. Divide and Conquer is Anti-Agility I see the product owner and dev team as a divide-and-conquer approach to work. Agility requires a collaborative cross-functional team.
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 agileculture. Instead of individual achievements, we can reward the types of agile leadership we want to see in agile teams.
Opportunities for More Agility. Because we release every time we finish a feature set, we have these opportunities for agility: Re-rank the remaining feature sets. If your company can't create an agileculture, consider an incremental lifecycle, especially if you have schedule risks. Part 5 Agile Approaches.
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.
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. Management Actions Create Business Agility.
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!):
Agile strategy leads to 220% increase in revenue. As the organization moved forward with acquisitions as outlined in the strategy, Brimstone worked with the organization on integration, building one culture, and identifying operation synergies and efficiencies. CASE STUDY. Let's talk CONTACT BRIMSTONE.
I had the pleasure of being on the Agile Uprising Podcast: Modern Management Made Easy with Johanna Rothman. How trust, empathy, and creating a safe environment are what allows us to use agile approaches. The post Fun Discussion with the Agile Uprising appeared first on Johanna Rothman, Management Consultant.
(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. Luke and I always have fun discussions.
Anytime I've seen a successful innovation culture, I've seen these principles. 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.
Effective governance can serve as the bedrock of organizational culture, which shapes perceptions, attitudes, and interactions throughout the organisational hierarchy, between departments, and within project teams. Foster an inclusive culture that values different perspectives.
Agilent Technologies, separating from Hewlett Packard, turned to Deloitte to help facilitate the transaction and Deloitte in turn asked Steve Pratt to act as project lead. Soon, Pratt and Joshi talked and Agilent became the first client Deloitte served using a global delivery model (GDM). Agile Enterprise. Digital Marketing.
I've met a number of agile coaches recently. However, many of these coaches work in organizations just starting a cultural transformation. Even though the client asked for agile coaching, that might not be what the client needs. Even though the client asked for agile coaching, that might not be what the client needs.
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 agileculture. That's because agile teams learn together as they create the product. Agile Behaviors for Learning and Working Together.
A Guide to Agile Practices and Their Benefits in Today’s Dynamic Business Environment In to-day’s business landscape, agility has become a key driver for success. Agile methodology, originally conceived for software development, has transcended its IT roots to become a vital approach in various business sectors.
I had great fun with Cherie Silas and Alex Kudinov on their podcast, “Keeping Agile Non-Denominational.” You've seen or heard about this problem: Senior leadership says, “Yes we need agility!” ” The teams say, “Yes, we got the agile goodness here!” The current culture pulls them one way.
Isn't every iterative and incremental approach an agile approach? We often hear agile approaches are a mindset. An agile approach requires a change in culture at the team level, at the portfolio level, and in management. Agile approaches change what we discuss, how we work together, and what we reward.
The original signatories of the Manifesto for Agile Software Development wanted to solve these specific problems: How can we: Bring more adaptability to software development? If you read these books, you could understand project-based agility. However, many people wanted “the recipe” for agility.
We talk a lot about empowered or self-organizing teams in the agile community. When Mark Kilby and I wrote From Chaos to Successful Distributed Agile Teams , we said the easiest way to create a system that worked for the team was for the team to create its own board. Agile Approaches Require Management Cultural Change.
In Part 1 , I wrote about how “Agile” is not a silver bullet and is not right for every team and every product. This post is about how management fits into agile approaches. Too often, managers think “agile” is for others, specifically teams of people. Team-based “agile” is not enough.
At the Influential Agile Leader workshop earlier this year, I led a session about scaling and how you might think about it. I asked if any of the teams succeeded at using an agile approach at the team level. I explained how in Agile and Lean Program Management.). ” Agile Scaling is the Answer to Whose Problems?
I just finished a series for my Pragmatic Manager newsletter about Agile Transformation Secrets: Part 1: Manage for Change. I wrote this series because I find that many people get a little confused about an agile transformation. They think an agile approach will work because they can predict and commit better. Please join us.
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. You can decide if you need an agile approach. See What Lifecycle or Agile Approach Fits Your Context? What can you do?
I discussed the origins of the agile approaches in Part 5. In this post, I'll discuss how you can create an agile approach that fits your context. Why should you create your own agile approach? Because your context is unique to you, your team, project, product, and culture. Remember, an agile approach starts with a team.
I started this series asking where “Agile” was headed. (I I didn't like what I saw at the Agile 2019 conference.) This part is about what “Agile” or “agile” means. I understand that people want what they perceive as the value “Agile” will bring them. Why a Manifesto?
I started asking if you actually need an agile approach in Part 1 and noted the 4 big problems I see. Part 2 was why we need managers in an agile transformation. Part 4 was about how “Agile” is meaningless and “agile” is an adjective that needs to be applied to something. That would be resilient.
I had a great time on the Agile Coffee podcast, 75. We spoke about a variety of issues that managers, teams, and people encounter, such as: Culture and how that plays out at all levels. We discussed several ideas from the Modern Management Made Easy books: How performance reviews make an agileculture difficult, if not impossible.
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