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. Now that the key features and benefits of resource capacity planning tools are clear, let’s explore some tips on how to choose the right tool.
Increasing volatility, uncertainty, growing complexity, and ambiguous information (VUCA) has created a business environment in which agile collaboration is more critical than ever. How to make your company more nimble and responsive. Marina Nasr / EyeEm/Getty Images. This story is not unique. Insight Center. Competing in the Future.
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. They plan diligently and produce excellent products and experiences for clients time and time again.
Support and training providing tools, templates, and training to project teams to enhance their productivity and adherence to standards. Improved Resource Allocation Efficient resource allocation is crucial for optimizing productivity and avoiding burnout. Agile, Waterfall, or Hybrid).
As I've been speaking about the Modern Management Made Easy books, people ask these questions: We're pretty good with our agile approach. How do we reward someone based on individual work when we want teams to work together? These people tell me their career ladder doesn't work to enhance agility. What do we do?
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? How to make your company more nimble and responsive. What can I do?”
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. They can offer a subscription-based revenue model if they figure out how to release something useful almost every week.
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. .”
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.
How to Optimize Team Potential: A 7-Step Guide for Managers High performing team managers optimize potential by unlocking their teams collective capability. In a working group, there is no collective work product beyond individual accomplishments. Because they can divide and conquer their tasks.
More of my clients say they want business agility. Yet, we don't share a common definition of business agility. Instead, let's consider how to see management's adaptable and resilient actions. Actions matter when it comes to business agility. Mindset is how we think about our work. That's a good thing.)
What do teams need to know about the product now to focus their work? These problems might be about how to reduce risk, what the users need first, or an experiment the team needs to learn.). ” That's why many people like time-based roadmaps. I'm not a fan of time-based roadmaps, but here's how they work to focus the team.
By providing real-time insights and streamlining complex workflows, project portfolio management tools empower organizations to handle diverse initiatives with precision and agility. It prevents overloading or underutilizing team members, increasing productivity and employee satisfaction.
I don't know how to offer the level of predictability they want for large and unchanging work. 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. Define Each Product Strategy.
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.
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. I had to explain to my managers how the project would work. My managers were smart but didn't understand how to spiral time.
The managers don't believe the teams need product owners, so the teams don't have POs. 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? They're having trouble with Scrum.
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.”
Then we feel more anxious,” says Susan David, a founder of the Institute of Coaching at McLean Hospital and author of Emotional Agility. On a team, these feelings, and the resulting hit to productivity, can be contagious. Sleep, exercise, and good nutrition are proven stress killers and productivity enhancers.
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.
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.
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?
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 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.)
By Ayman Sayed, President and Chief Product Officer, CA Technologies. But, what about the application of AI and ML to agile development, testing and even portfolio management? We’re all striving to deliver better products faster to meet customer needs in the marketplace and stay ahead of the competition.
By providing real-time insights and streamlining complex workflows, project portfolio management tools empower organizations to handle diverse initiatives with precision and agility. It prevents overloading or underutilizing team members, increasing productivity and employee satisfaction.
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.
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.)
(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.
” 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. I'm not alone.
Strategy and Product Feedback Loops Many of my middle-management and senior leadership clients want certainty about future work. Does that sound like an agile team to you? However, managers don't create features as agile teams do. Agile teams don't assume they make a final product the first time out.
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?
We had (and still have) too many products to keep the same teams on them for a long time. For programs, the team stayed together and moved to a different feature set/internal product until the program finished. We could move to a new product and/or a new team. My job was to smooth the way for people to deliver products.
You can do this even if each of you is an expert on various areas or different products when you use flow efficiency. Here's how Clare's team worked: Every person started their own story. See Who's Playing Agile Schedule Games? ). No More Agile Death Marches. Agile approaches are all about collaboration.
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!):
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.”
See Create Your Successful Agile Project for more details.) Also, see the Pairing, Swarming, Mobbing post so you can see how people might work together, keeping the team's WIP low. My suggestion for team-based WIP is the floor of the number of people on the team/2. If your data is unreliable, fix that problem first.
And even if you can find an agile coaching or Scrum Master job, the pay is so terrible, you don’t want to take it. That’s because these managers think agile coaching and Scrum Mastering is a staff job, not a line job. At what level do you understand the products you’ve worked on? Those are functional skills.
From figuring out how to cut costs and trying to stand out from your competitors, all while also trying to keep your staff paid and happy, there’s a lot to think about. This is because they are better equipped to handle tasks, solve problems, and deliver high-quality work–all of which impact organizational productivity.
However, agile teams have one specific “tool” to create better predictability: right-sizing their stories. When I say that, teams roll their eyes at me—until they learn to make product minimums and split stories. But right-sizing works even better when we need to forecast product development.
The corollary, of course, is “we don’t know how to do that.” That’s our product, and that’s our passion. It launched a product, gathered feedback, and kept iterating as it scaled and added users. Your data isn’t even in the picture. We are simply not interested in any of it.”
When Mark Kilby and I wrote From Chaos to Successful Distributed Agile Teams , we differentiated between these types of teams: Collocated, as all the people are within 8-16 m of each other. In Developing Products in Half the Time , Smith and Reinertsen used the Allen Curve (in the above image) to decide whether a team was collocated or not.
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