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
Directional insights and fast feedbackloops reduce risk without slowing progress. Flexible plans grounded in principles help teams stay aligned and resilient. Research belongs inside the flow of work : Teams move smarter and faster when discovery is continuous. They build trust by being transparent and inviting collaboration.
In this episode, Maya breaks down the product philosophy that drives iFundWomen and how values like inclusion, community, and empowerment are embedded into every step of the product journey.
If you’re sprinting with delivery while discovery is stuck in the parking lot, you’re not agile. Most product teams talk about dual-track agile, but few actually do it well. How to Set Up Dual-Track Agile (Not Just Talk About It) “Discovery isn’t something you squeeze in between shipping. Discovery gets sidelined.
Use behavior-based triggers Personalized nudges, milestone tracking, and feedbackloops to keep users engaged. Make switching easier Allow parallel use with existing tools and automate data migration from competitors. Patreon members get exclusive access to deeper strategies for product adoption.
Brought to you by: • Enterpret —Transform customer feedback into product growth • BuildBetter —AI for product teams • Wix Studio —The web creation platform built for agencies — Shaun Clowes is the chief product officer at Confluent and former CPO at Salesforce’s MuleSoft and at Metromile.
Use focus groups to test low-fidelity prototypes and gather qualitative feedback. Customer feedbackloops Gather real-time insights before development. With Usersnaps discovery survey templates and real-time, contextual insights, you can effortlessly collect and analyze user feedback at scale.
A person who lacks experience leading agile development or working in fast-paced, iterative environments. Laid the groundwork for scaling platforms with structured backlogs, user-centric feature planning, and Agile methodology. Who would be a bad fit for this job? How can Prarthana benefit your company?
Tracks progress at both detailed and executive levels Automates reminders, handoffs, and status updates Hosts shared assets and enables feedbackloops Aligns everyone around a unified timeline for launch Weekly cross-functional syncs allow teams to discuss dependencies, unblock issues, and adjust plans as needed.
The rise of intelligent product development powered by AI and now agentic workflowscalls for a new kind of operating model: one that is agile, continuous, insight-driven, and AI-augmented. Through modular, strategic investments, starting with a data readiness assessment and aligned discovery loops.
By responding to customer reviews, you can demonstrate your customer-centric orientation and close the feedbackloop. Product feedback software: Trustpilot. And once the requests are recorded, it keeps users up to date about their status, helping teams close the feedbackloop. Product feedback software: UserVoice.
To help you build smarter (not just faster), we sat down with Matt LeMay – author of Agile for Everybody product discovery evangelist, and creator of the One Page / One Hour method – to learn how to keep discovery grounded in real business impact. Use interviews, surveys, user testing, and more.
The objective is to receive feedback and prioritize it internally against (1) company objectives (2)customer pains/experience (3) Quarterly Product OKRs and ship out solutions. . A feedbackloop is: part of a system in which some portion (or all) of the system’s output is used as input for future operations.
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. Consider the Continuum of FeedbackLoops and Decisions. Let's start with the team.
How product managers can use the Modified Agile for Hardware Development Framework. They think they have the answer for applying Agile principles to hardware projects, and they call it the Modified Agile for Hardware Development (MAHD) Framework. Today we are talking about using a modified version of Scrum for hardware projects.
Strategy and Product FeedbackLoops. These problems and questions are all about delays in the system's feedbackloops. It's time to see these feedbackloops, starting with the team. How Long Are Your Team's FeedbackLoops? Product-Only FeedbackLoop. Roadmap FeedbackLoops.
This part is about shortening feedbackloops. They had one piece of feedback: the checkin broke “unrelated” code. It was time to see their feedbackloops. See Your FeedbackLoops. Every project (or effort) has at least one feedbackloop. How Long Are Your FeedbackLoops?
” (The team feedbackloop is the inside of the onion for how agile the organization can be. See Multiple Short FeedbackLoops Support Innovation.). The post Shorten Team FeedbackLoops with These Three Questions to Increase Throughput appeared first on Johanna Rothman, Management Consultant.
In Costs of an Agile Approach for Hardware Products , I suggested that an iteration-based approach for hardware was too expensive. Agile software teams are cross-functional and interdependent. Many agile software teams have somewhere between four and seven people. FeedbackLoops Drive Collaboration. And, with whom?
I started this series discussing the issue of the various product-based roles in an agile organization. And, batching the product planning in one-quarter chunks doesn't encourage us to reduce the feedbackloop duration. Back when we started using agile approaches, many teams worked directly with their customers.
Strategy and Product FeedbackLoops 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.
Do you need feedbackloops so you can: Cancel the project at any time (to manage schedule and cost risks. Frequent releasing offers us feedback in many ways: Know that we're solving the right problem. Frequent releases help us manage risk with shorter feedbackloops. Why You Might Want an Agile Approach.
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.
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. See Multiple Short FeedbackLoops Support Innovation for more information.).
More of my clients say they want business agility. Yet, we don't share a common definition of business agility. Those actions show that managers change their actions in the face of new information or feedback. Those actions show that managers change their actions in the face of new information or feedback.
He thought agile approaches would work to “meet” and “enforce” deadlines. Even when we use a non-agile approach , schedule variance doesn't make sense. Schedule variance assumes we don't have feedbackloops inside the project, or that we don't learn anything. Why do you have deadlines?
See Create Your Successful Agile Project for how to use cycle time to reduce the time you spend on estimation.). If your team has to change what they do one month or six weeks into a quarter's estimation or commitment, the product feedbackloop is too long. Product FeedbackLoops are Different than Project FeedbackLoops.
TL; DR: Agile Laws and Remote Agile On numerous occasions in the recent past, working with distributed agile teams has amplified existing organizational, technical, and cultural challenges in many organizations. In that respect, the current issues many distributed teams face may also act as accelerants to become more agile.
Your planning feedbackloops can be longer. We need short feedbackloops in the project/program to see where we are and make small adjustments. Even if you do encounter technical problems, agile approaches help manage those problems with short project feedbackloops. We know what we have to do.
Still, effective, quick decision-making is a skill we crave and can increase agility, energy, and momentum within any team. . The second challenge is implementing a feedbackloop. Rapid learning and course correction is a key part of an agile decision-making process. We learn far more by studying the decision itself”.
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.
Many of my clients are trying to use short feedbackloops in agile approaches. The more need for product innovation and change, the shorter the feedbackloops need to be. I wrote about this in Create Your Successful Agile Project.) High Need for Product Innovation and Change.
However, the more often we deliver in short feedbackloops, the more often we can make strategic decisions. The more often we iterate strategically, the more we exhibit business agility. The shorter the feedbackloops, the easier it is to use what we finished to make a new decision about the next bit of work at all levels.
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. Release trains.
I’m working on my roadmapping talk for Agile 2018. I finally had the transforming idea about how to position the talk: Roadmapping and product planning are about feedbackloops. The shorter the feedbackloop, the faster and more often we can learn. How little can you do to get some feedback on the product?
The leaders and change agents we meet are eager to ensure their Agile transformation avoids hitting rocks or running aground. We aim to address those obstacles in this article by offering three Agile transformation OKRs (Objectives and Key Results) for you to consider. The First Agile transformation OKR – “Leader Engagement”.
As teams learn how to work in new ways during an Agile transformation, an organization may consider adopting Agile values in departments outside of IT to support the initiative. In an Agile Uprising Podcast Agile and HR – BFF’s? In an Agile Uprising Podcast Agile and HR – BFF’s?
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.
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 agile culture. Instead of individual achievements, we can reward the types of agile leadership we want to see in agile teams. Ask for help.
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? Especially since teams now had these levers, from the iterative and incremental approaches: Prototype something for fast feedback. Feature-Driven development.
Strategy and Product FeedbackLoops About 20 years ago, I taught a project management workshop to IT people. That's why the duration of the internal feedbackloops is so important. I used the image above in Multiple Short FeedbackLoops Support Innovation. Show them your feedbackloops and your cycle time.
Agile has been shown to shorten time-to-market, increase quality, instill predictability, improve customer satisfaction, and create an overall happier working culture. Agile Transformation involves all levels of the organization and applies Lean-Agile principles to business processes, practices, tools, operations, and culture.
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.
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. A focus on a “standard” agile approach, regardless of how much agility is in that approach.
Establishing agile and product culture is critical to us becoming a modern organisation that continuously improves. Supporting their development, helping them to think and act as agile and product champions. I also defined a vision: Agile product management culture is the norm and is adding measurable value to Parkinson’s UK.
We organize all of the trending information in your field so you don't have to. Join 96,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