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
Agile methodology. In contrast to Waterfall, Agile is a flexible iterative approach, which was initially developed for software engineering but has gained popularity in other types of engineering projects. The main characteristics of this approach are responsiveness to changes, continuous collaboration, and frequent value delivery.
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. What do we do?
At the same time, the amount of information in any domain is unprecedentedly huge – courses, books, education websites, blogs, etc. So, we’d like to give you guidance in this flow of resources – we’ve selected 11 project management books that any successful project manager should discover. What else will you find in this book?
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
I had a terrific time with Chris Williams on his Badass Agile podcast. We discussed the Modern Management Made Easy books. The seven principles I covered in the books. How managers need to collaborate to achieve agility. Chris called these “indispensable books.”. We had a terrific discussion. Rule of three.
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.
See Behaviors Create an AgileCulture with Johanna Rothman. We spoke about the Modern Management Made Easy books. We had a delightful discussion on Behaviors Create an AgileCulture with Johanna Rothman. Gregory Miller and I discussed the ideas of behaviors vs mindset on his podcast. And much more.
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.
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.
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. See the Modern Management Made Easy books, too. How servant leaders support people taking responsibility.
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. That's a good thing.) Actions Over Mindset.
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!):
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.
(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.
I'm rewriting/reorganizing the Lead an Innovative Organization book. 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. The post Want Business Agility?
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? Before the Manifesto, we had plenty of books and articles that discussed more lightweight approaches. That's just books. The Context for the Manifesto.
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.
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 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.
If software has eaten the world, then agile has eaten the software world. And there is no shortage of information and advice on how agile should be implemented in your tech organization. For example, a Google search for “agile software development” returns over 14 million results. Related Video.
You hear a lot about “agile innovation” these days. Teams using agile methods get things done faster than teams using traditional processes. Agile has indisputably transformed software development, and many experts believe it is now poised to expand far beyond IT. They keep customers happier.
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 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.
Successful companies, like Apple or Google, deliberately foster a culture of “space” where innovation can flourish. The backspace represents agility—the ability to pivot, revise, and improve. Get your copy of my latest new books available now on my Amazon’s author page.
Now, these same managers want business agility. The more we remove, the more agility or improvement we might see. As the teams used agile approaches, they requested more and more frequent deployments. A lot of the friction we see is anti-agility. What culture do you want? What Might You Consider Removing?
When I think about changing outcomes, I think about culture change. Of the four factors, how can we create a culture that encourages happiness? We might create that culture this way: Create the “good” kind of stress. I like agile approaches because I can separate lots of deliverables into small, coherent pieces.
A couple of weeks ago, I delivered the first version of my Free Your Agile Team talk at Agile New England. I spoke about the problem of a framework-first approach to transforming to an agileculture. I based the talk on Create Your Successful Agile Project , but I didn’t stop there.). (I
Mark Kilby and I have finished the first four chapters of From Chaos to Successful Distributed Agile Teams: Collaborate to Deliver. If you don’t like to read books in progress, wait until we have more chapters done. If you don’t like to read books in progress, wait until we have more chapters done.
” These managers have created a resource efficiency culture, not a flow efficiency culture, as in the image above. In contrast, a flow efficiency culture watches the flow of the work. What does your culture value? Or does the culture value throughput, so people collaborate on the flow of the work?
See Agile FM – Johanna Rothman. We spoke about a number of ideas from the Modern Management Made Easy books: How to recognize and avoid micromanagement. I had a terrific time with Joe Krebs on his podcast. What it might mean to engage people at work. The kinds of workspaces we need. Psychological safety. One-on-ones.
Gil Broza and I are thrilled to announce the updated version of our flagship workshop, the Influential Agile Leader. If you have these kinds of challenges: Your business can’t “stop” to recreate itself as an agile organization. That will help everyone avoid bounce-back to non-agile approaches. Then do join us.
I’ve been thinking more about possible measurements in an agile transformation journey. This post will focus on measurements you might see when the culture changes with an agile transformation. They “measure” the culture. When you transform your measurements, you can transform your system and culture.
.” In my experience, when organizations want to use agile approaches or transform in some way, the managers start with the teams. Agile approaches can help teams improve, and many teams do release value faster. I always estimate how long my books take. I'm still experimenting with my book writing to make it faster.).
In our book Time, Talent and Energy , we note that when employees aren’t as productive as they could be, it’s usually the organization, not its employees, that is to blame. Many corporate cultures require collaboration far beyond what is needed to get the job done. Executives can also work on culture and coaching.
We hear about agile teams, in the form of product or feature teams. I showed Bob this picture from Book 3: Practical Ways to Lead an Innovative Organization , and he said, “Yes! ” If we want business agility, managers need to work in teams—maybe even before we think about product or feature teams.
In the research for my book, Simply Brilliant , I spent time with lots of leaders with big ideas about the future. Indeed, I’m not sure I’ve met a CEO who has made learning more central to the corporate culture than Ridge has, or has found more ways to develop a thirst for learning among his colleagues.
” Many of us now work in constantly connected, always-on, highly demanding work cultures where stress and the risk of burnout are widespread. Since the pace and intensity of contemporary work culture are not likely to change, it’s more important than ever to build resilience skills to effectively navigate your worklife.
Does your team have to keep two sets of “books”? You have an agile roadmap to see where you're headed. Your team hates having to translate the agile planning into more traditional planning. If you're in this pickle, your manager might think your agile team doesn't replan very often. Placate the Manager.
I'm rewriting/reorganizing the Lead an Innovative Organization book. 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. Manage for effectiveness.
As I complete the Modern Management Made Easy books, I realize I need to explain how much tolerance an organization has for experiments. If you're working on a culture change such as an agile transformation, see if you can understand what the organization rewards. That might be your first step to creating a more agileculture.
This program gives employees across all disciplines and levels tools to educate them on the company, its culture, products and services, and how they solve its customer’s needs. Marketers are adopting the business practices of entrepreneurs such as lean startup and agile development.
See the roadmap series starting with Alternatives for Agile and Lean Roadmapping: Part 3, Flow-Based Roadmapping to see how to integration options into your various roadmaps. Options Helped Me Write and Deliver a New Book By design, I have a one-person business. That's where rolling wave planning with options works to help us change.
You now realize that if you want an agileculture, you want the team to collaborate. Agile thinking and culture shows us that no, we don't. I addressed this particular issue in books 2 and 3. Once you discuss the problem with the person, discuss the problem with the team. Explain that you made a mistake.
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