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
The main characteristics of the Lean method for project management involve reducing waste, increasing efficiency, and improving project performance. Agile methodology. Although engineering projects are structured and ordered, they sometimes require flexibility, which can be achieved by integrating some elements of Agile methodology.
Reporting and analytics A robust capacity planning tool should generate reports and dashboards with insights into resource availability and capacity, allocation, and utilization, which will help managers track resource performance and assess the efficiency of project work. Why do you need capacity planning software?
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. That disconnect occurs when managers, HR, everyone focuses on resource efficiency, not flow efficiency.
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?
The German sociologist Max Weber famously praised bureaucracy’s rationality and efficiencies. 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. Learn and experience how agile works. What can I do?”
I'm rewriting/reorganizing the Lead an Innovative Organization book. Flow efficiency at all levels. Let me address a little about business agility and innovation. Business agility allows us to create a culture where we plan to change. Deciding what not to do is often more effective than trying to be efficient.
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.
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. The most popular and widely used Agile methodology is Scrum. Read further to learn the details. The Role of Sprints in Project Management .
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.
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.
Resource Efficiency. ” “Each resource has at least two projects so they stay productive and efficient.” ” These managers have created a resource efficiency culture, not a flow efficiency culture, as in the image above. .” Resource efficiency means we watch each person's effort.
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. And there is no shortage of information and advice on how agile should be implemented in your tech organization. Related Video.
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 agile culture. That's because agile teams learn together as they create the product. Agile Behaviors for Learning and Working Together.
Years ago, Roy Osherove interviewed me about project management, agile thinking, hiring, and management. See Johanna Rothman Interview – Agile, a Decade Later. We focused much more on agile issues in this interview. Some links to some of my thinking on: “Scaling” agile. Flow efficiency.
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 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!” ” And the middle managers?
And given the plethora of “agile” coaches, too many managers have relinquished their coaching roles to these (supposed) agilists. What if it's most efficient to do the work for a person or a team? Reducing management delays and increasing management throughput allows everyone to be efficient and effective.
So, automakers have to change their approaches to product development to make it shorter but no less efficient. . Nevertheless, automotive companies need to deliver their projects as successfully and efficiently as possible. Utilize available resources with maximum efficiency. Adopt Agile frameworks for product development.
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? You deserve an agile approach that helps you achieve the business outcomes you need. What do you need? Start with the Team.
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 agile culture. I based the talk on Create Your Successful Agile Project , but I didn’t stop there.). (I Yes, there are 8 parts!).
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. It's time to start removing some of those policies and procedures.
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.
.” 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.).
I had a great time recording with two of the guys from the Agile Uprising Podcast. See Create Your Successful Agile Project with Johanna Rothman. We discussed the book. I had an opportunity to rant and rave about many things: agile project managers (no, the term is not an oxymoron). I had a great time with Jay and James.
You don't want to reinforce resource efficiency, even though you rewarded the person for that all along. Instead, you want to reinforce flow efficiency. Discuss why you want flow efficiency and overall lower cycle time. You now realize that if you want an agile culture, you want the team to collaborate.
In research for our book, Time, Talent and Energy, my co-author Michael Mankins and I found that such investments do indeed pay off: The top-quartile companies in our study unlocked 40% more productive power in their workforce through better practices in time, talent and energy management.
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. Here is a super summary of the six principles (some are more illuminating than others): Understand what other people do.
Successful project delivery is usually a result of efficient management of both workflow and resources. What do you need to know to manage project resources with maximum efficiency? What do you need to know to manage project resources with maximum efficiency? The results of efficient resource management are as follows: .
I'm rewriting/reorganizing the Lead an Innovative Organization book. Flow efficiency at all levels. Let me address a little about business agility and innovation. Business agility allows us to create a culture where we plan to change. Deciding what not to do is often more effective than trying to be efficient.
I like agile approaches because I can separate lots of deliverables into small, coherent pieces. When I want to deliver books, I need a team to create a final delivery. See the Flow Efficiency series.). In fact, agile approaches make this kind of culture possible. Focus on job satisfaction. Increase self-esteem.
Flow Efficiency In How Centralization Decisions Create Friction, Increase Cycle Time, and Cost Money, Part 1, I discussed how removing support staff for departments and managers created longer cycle times. Now, it's time for Economies of Scale and how that ties into resource efficiency thinking. See the Wikipedia article.
Up until now, HR wanted to reward an individual's contribution, thinking in terms of resource efficiency. Even if you're not part of an agile team, highly collaborative teams have trouble identifying who contributed what. Yes, it’s about the ideas in the Modern Management books, but you’ll recognize many of the ideas.
A total of about 1500 words on the book plus one image. The book distributor work is complete. However, if people collaborate with pairing, swarming, or mobbing, they work in flow efficiency. If you want to “scale” your agility, ask yourself these questions: How can we collaborate at all levels?
If you're trying to use an agile approach, what do you care about in terms of finishing: That the team finish the work, regardless of the personal or team cost? Agile teams always know who did what. I updated this in the book.) In agile organizations, peers offer this feedback, not (just) the managers.
To take advantage of this opportunity place focus on building agility, aligning the organization, operating as a team of teams, and developing your people. Build Agility. While it is easy to say these pivots were a result of agility, it is important to differentiate between “brilliant improvisation” and a repeatable capability.
This is one of the reasons Mark and I wrote From Chaos to Successful Distributed Agile Teams. Your team might not need an agile approach. Mark and I listed these tools for the team's workspace in the book: The code repository. Now, as I write this series, the coronavirus is winging its way around the globe. The test repository.
See Building a Team With Feedback and Create Your Successful Agile Project ). Hiring based on low salary vs resource efficiency and flow efficiency. Open book management, especially with regard to salaries. I wrote about some of this in Agile HR, Part 5: Performance Management, the Career Ladder.
It’s wide-ranging from thinking about agile approaches as a way to improve organizational flow and what that means for us as humans. We had a wide-ranging discussion, about my fiction writing, my books, how agile approaches affect the organization and how people can think differently when the teams and managers use agile approaches.
I took an opportunity to write a new book this year, Free Your Inner Nonfiction Writer. That book satisfied one of my business goals: to write more useful books. That book was on my options list, but I had not planned to write that book this year. I'm now able to finish the consulting book.
Here's an example from the project portfolio book. See the image about problem determinism in What Lifecycle or Agile Approach Fits Your Context? However, they worked inside a system that valued resource efficiency. Yes, the essence of agility.) The costs of the work often have little relation to the value of that work.
How could we organize if we want flow efficiency? Even before I knew about agile approaches, I spent a bunch of time creating unit tests and system tests so I could know that as I fixed/added/replaced code, I hadn’t introduced any problems. If you’re wondering, this is how I write books. Thinking about Refactoring.
I have a paper book from 1989.). The idea of resource efficiency instead of flow efficiency pervades management, too. The more transparency the managers have with each other and their bosses, the more likely the senior leadership team will start to realize that managers need to collaborate, to work in flow efficiency.
If you use these delegation ideas, you will find you have time to have one-on-ones every week or two, depending on how agile your team is. Most of the problem is that organizations reward resource efficiency, not flow efficiency —even for managers. You will also have time to think. Facilitate Other People's Learning.
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