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
Here’s an overview of the main principles of this approach: Muda: aims to streamline project workflow by eliminating waste, e.g., overproduction, excess inventory, idle time, and product defects; Value Stream Mapping (VSM): visualizes the full process of value delivery (e.g., Agile methodology.
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. Other Features Product overview Time tracking Workload management Task management Collaboration Templates 9.
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?
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?
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 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.
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.
Agile has become the most popular methodology in recent years and has proven its efficiency for millions of companies already so nobody has any doubts about it today. Being agile means being flexible enough to adequately and timely react to any alterations of your project environment and any external changes that may happen at any time.
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?
I’ve been pair-writing a book with Mark Kilby , From Chaos to Successful Distributed Agile Teams: Collaborate to Deliver. We’ve been working on this book for a year. We reflected a little on our success to date: We both want the best possible book. It’s much better because of our collaboration.
(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.
Many nonfiction writers start books with outlines. Or, some writers (raises hand) are prone to put everything she ever learned about this topic into one book. Either of those problems make it difficult to finish a book before the writer dies. Either of those problems make it difficult to finish a book before the writer dies.
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.)
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 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 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.
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.
I'm rewriting/reorganizing the Lead an Innovative Organization book. 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. Manage for effectiveness.
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.
The book provides six principles that the author’s believe can make organisations more agile, competitive, and responsive by helping employees become more autonomous, cooperative and empowered. The car manufacturer tried to do this by moving its production engineers to the warranty department.
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.
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.
Some of my clients have struggled with their project governance as they move to agile approaches. This kind of measurement is antithetical to agile principles. We can see it in an agile approach, because the more time we spend estimating up front, the longer it takes us to deliver that first increment of value.
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 have some feedback on the book that I need to integrate. I want to address the next 3 chapters, because they're the platform for the next part of the book. In addition, I also have a new task: get one book ready for another distributor. In addition, I also have a new task: get one book ready for another distributor. (If
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.
I had a great time on the Agile Coffee podcast, 75. How we might ascribe value to seeing customer situations vs sitting in the office working on the product. We discussed several ideas from the Modern Management Made Easy books: How performance reviews make an agile culture difficult, if not impossible.
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.
A total of about 1500 words on the book plus one image. The book distributor work is complete. All this collaboration and learning together means the team shares its product development. If you're a product leader, you need a product value team. If your managers scale these ideas, they can also become more agile.
“Productivity isn’t everything, but in the long run it is almost everything,” wrote Paul Krugman more than 20 years ago. Productivity in most developed economies has been anemic. During much of this time, it has been shareholders, not workers, who have reaped the benefits of higher productivity.
I still want to write more in the book. I don't have just one product for my business. And I'm not a team working on just one feature set or a product. Those purchase orders are much larger sums of money than an online workshop or revenue from a book. At some point today, I plan to upload the videos to teachable.
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.
After I spoke with Chad and Jeff on the previous podcast, Deep Dive into Successful Independent Consulting with the Agile Wire , we spoke all about the idea of building products, starting with consulting-based products. See Building the Right Product with Johanna Rothman. In the meantime, enjoy our discussion.
Now, these same managers want business agility. The more we remove, the more agility or improvement we might see. As the organization changes (both products and tooling), people might not make those mistakes again. About a decade ago, an organization suffered three consecutive bad deployments to production.
Whether it’s clearing room in a product or service line, pausing to reassess strategies, or giving ourselves time to think creatively, progress is born from intentional gaps. The backspace represents agility—the ability to pivot, revise, and improve. Business Lesson : Mistakes are inevitable.
Instead of incurring the time and cost when you bring everyone together, consider the Product Value Team. (In In past writing and presentations, I’ve called this the Product Owner Value Team. I am trying to change my term to the Product Value Team.). The product value team is a different kind of a team.
” These people claim there is no need for either role in an effective team, especially an agile team because the team can manage its own deliverables. While some agile teams can manage their own deliverables, that's not the only role for a project or program manager. Clarify the Product and Team Objectives. The outcomes).
I suggested ways to think about more agile budgeting in part 1. I evaluate the plan—my products, services, and clients—on a regular basis. Publish that book? I can change that mix because I can produce some of my products in under a month. Also, see From Chaos to Successful Distributed Agile Teams.
This guy, from a famous agile consultancy, not only used my article. Not only did he use the image from the article that referenced the book, he didn't acknowledge my work at all. I said, “If you credit my work—both the article and the book—you can keep using these slides.” Maybe I could learn something.
global chip shortage), and the need for reducing production costs add to the above-mentioned difficulties. . In addition, to stay competitive on the market, business owners will struggle to deliver their products faster and produce more (e.g. The need to shorten the time for product development. Dealing with uncertainty.
Many new-to-agile teams use some form of iteration-based agile approach. Back in Time You Spend in Agile Meetings (near the bottom of the post), I enumerated all the possible meetings. I’ve seen several benefits of using a Demo column before the Done column: Too many teams have part-time product owners.
.” 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.).
We hear about agile teams, in the form of product or feature teams. Then he said, “I miss the team-based problem solving I did with colleagues back when I was on a product team. ” We’re accustomed to product or feature times. The managers also learned that some teams had overloaded product people.
The true cost to business can be far greater, thanks to low productivity across organizations, high turnover, and the loss of the most capable talent. 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.
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