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
I wanted to share with you the framework I use when doing this. I then do various interviews with executives all the way to Product Management team members and surrounding functions. Below is a brief overview of the framework that I use and a few signs of where you should start if you want to run this exercise yourself.
What do you do when your team is working their socks off and yet they are getting little credit for the work being done, mainly because the team isn’t able to set concrete expectations with the stakeholder? This obviously reflected as a failure to deliver on part of the engineering team. THE CHALLENGE. THE CAUSE.
Before the advent of agileframeworks like Scrum , a product person—the product manager—would typically carry out the market research, compile a market requirements specification, create a business case, put together product roadmap, write a requirements specification, and then hand it off to a project manager.
.” But do not allow people to dominate and tell you what to do, and don’t agree to a weak compromise. In Scrum—the framework that gave birth to the product owner—the role is responsible for maximising the value a product creates for the users and for the business. That’s usually challenging enough.
In this talk from #MTP Engage Manchester consultant Itamar Gilad takes us through his GIST (goals, ideas, steps, tasks) framework. Negative – where launches are so bad they get rolled back. This in turn feeds project plans and feature roadmaps, and the micro-planning of an agile product team. Three Types of Launch.
We had no clue about what “Lean” or “Agile” or even “Startup” essentially meant, but we spent most of our time out in the streets talking to our customers. Similar stories have inspired new product and business developmentframeworks , thousands of articles, and numerous books. Let’s go Agile! So where is the problem?
At JCDecaux, I led the development of an information kiosk for airport passengers. Passengers are also able to view hotel information and use the devices to speak to the sales team of the hotel. In addition, choosing the wrong product management framework added to the failure of the launch.
Listen to the audio version of this article: [link] 1 Complement Scrum with a Product Discovery and Strategy Process Scrum is a simple framework that helps teamsdevelop successful products. Continue the discovery and strategy work while the product is being developed. But don’t stop there.
But you can think of the product owner as an agile product manager, as I explain in the article “ Product Manager vs. Product Owner ”. In the agile scaling framework LeSS, the role is referred to as “ Area Product Owner “ A component owner owns an architecture building block like a user-interface layer or a payment service.
. “Successfully managing complex sales requires a different level of visibility into your deals” To get visibility into large deals, I developed a visual framework – which I call the Agile Arrow – that applies popular project management principles to the work that we do as salespeople.
The Secret Product Management Framework. Finally writing down the Secret Product Management Framework was a revelation for me. One test of a new framework is how well it explains “previous observations.” In this article, I tie the older posts to the framework. How To Talk To Your Executives About Agile.
The ideas of Agile are great. Three mindsets of product development. Design Thinking is how we explore and solve problems; Lean is our framework for testing our beliefs and learning our way to the right outcomes; and Agile is how we adapt to changing conditions with software. Agile is related to Lean. Jeff Bezos.
TL; DR: How to Make Agile Work in Fast-Growing Startups For years, I worked in several Berlin-based, fast-growing startups in my capacity as Scrum Master, agile coach, and Product Owner. These are my lessons learned on making ‘agile’?—?including including Scrum as a framework?—?work work in a fast-growing startup.
The Secret Product Management Framework. Finally writing down the Secret Product Management Framework was a revelation for me. One test of a new framework is how well it explains “previous observations.” In this article, I tie the older posts to the framework. How To Talk To Your Executives About Agile.
The Secret Product Management Framework. Finally writing down the Secret Product Management Framework was a revelation for me. One test of a new framework is how well it explains “previous observations.” In this article, I tie the older posts to the framework. How To Talk To Your Executives About Agile.
So, it was natural that we should want to develop a talent growth plan for our people. Each month we send out an NPS survey to assess whether the company is being a great place to work, but a few months ago I also sent Google’s manager feedback survey to my team of 10 product managers. Team execution and development.
Ruthless prioritization translates to product teams spending time building the right thing at the right time. This discipline is the bread & butter for a winning product team, but building an effective product process takes a lot of trial and error. A decision making framework that I use is. The goal of a feedback loop is.
It can be hard to reach the required level of buy-in without using design-by-committee , brokering a weak compromise, and agreeing on the smallest common denominator—which is hardly the foundation of a successful product. This approach makes it easier to reach unanimity and consent without making weak compromises.
Has the spirit of being agile been lost behind a mountain of rules? Agile vs. Being AgileAgile became popular shortly after ‘The Agile Software Development Manifesto ’ was published in 2001. Companies who focused on being agile saw great success, and others wanted to follow suit.
Before the advent of agileframeworks like Scrum , a product person—the product manager—would typically carry out the market research, compile a market requirements specification, create a business case, put together product roadmap, write a requirements specification, and then hand it off to a project manager.
At the beginning of any software development project, managers think of which methodology is between waterfall and agile. It’s essential to follow clearly defined processes or software development life cycle (SDLC) to ensure software development quality. Waterfall and agile: A smart method or bad solution?
I was asked to give a ten-minute overview of my continuous discovery framework and then participated in a fireside chat where the host, Cecilie Smedstad , asked me to go deeper in a few areas. Discovery is a team sport. I did classic web development before there were frameworks back in the ’90s. Week over week.
The Scrum Guide released in November 2020 states that “the product goal describes a future state of the product … [It] is the long-term objective for the Scrum team.” The product owner is accountable for “developing and explicitly communicating the product goal.” The entire Scrum team is “focused on one … product goal” at a time.
Many medium to large organizations are adopting agile practices, such as the use of Scrum. Most of these organizations are also using some form of stage-gate for the development of new products. companies using stage-gate, the idea of replacing it with agile is often not warmly embraced. For the more than 80 percent of U.S.
Some product teams are moving away from written PRDs to visual artifacts like mockups and prototypes. It’s a change in approach that’s driven by demands for more agility and greater velocity from the time a problem is identified to the time that a product is released. . They become more effective when used together.
And leaders have an outsized impact on team performance. She shared some insights on human behavior, and how we as leaders can use our influence to build a culture of psychological safety, enhancing collaboration and problem solving in our teams. On the tactical front, we talked about the good and bad sides of data.
Prescriptive Agileframeworks make it hard for designers to add valuable contributions to the team. I designed every detail in Photoshop before handing the mockups to the developers. Desperate to find an alternative to our ineffective process, I stumbled upon Agile and it blew my mind. But it wasn’t all that bad.
Agile Died While You Were Perfecting Your Standup. Nate Walkingshaw argues that it’s time to take the things we have learned from Agile and move on to new ways of working together to build products. Why Isn’t Agile Working? It is common for big organisations to adopt Agile, but see no benefits. Burn down the burndown.
Too many times people confuse agile and scrum. Agile is a concept with principles that helps us develop software better, validate it as soon as we can, and bring value to our customers faster. Scrum is a valid and very popular framework for agiledevelopment. Agile is just a means to an end.
On the other hand, the Scrum Master theses also cover, for example, the relationship with the Product Owner, they deal with agile metrics, and how to kick-off an agile transition, thus moving beyond the original framework of the Scrum Guide. Product discovery using the Design Thinking, Lean Startup, or Lean UX frameworks help.
On June 26, 2017, English football team Crystal Palace enthusiastically announced the appointment of the great Dutch defender Frank de Boer as its new manager. He announced he would take a middling team and turn them into a whirring, possession-based team emulating the lofty ideals of Total Football. The Parable.
If you manage a digital product that end users employ, such as a web or mobile app, then you usually do not require in-depth technical skills, such as, being able to program in Java, write SQL code, or know which machine learning framework there are and if, say, TensorFlow is the right choice for your product.
Agile Died While You Were Doing Your Standup. The inimitable Nate Walkingshaw argues that despite the successes Agile has brought us, it’s time to take the things we have learned from Agile and move on. Understanding how Design Thinking, Lean and Agile Work Together. Dual-Track Agile: Why Messy Leads to Innovation.
.” But do not allow people to dominate and tell you what to do, and don’t agree to a weak compromise. In Scrum—the framework that gave birth to the product owner—the role is responsible for maximising the value a product creates for the users and for the business. That’s usually challenging enough.
1] Figure 1: An Empowerment Model for Product People and Teams Level one represents the authority to decide how features are detailed and guide their implementation. Level three, finally, allows product people and teams to develop the product strategy including the value proposition and business goals.
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.
It is one of the most commonly used, abused, and misused metrics in Agile software development. Teams, their managers, and even their stakeholders often focus on “improving velocity” without considering the entire value delivery system. Successful Programs for Metrics in Agile. Bad turnover. Measure for a Purpose.
Value stream mapping is a common practice in the Agile space because it allows leaders and stakeholders to see where the flow of value delivery is slowing down and exposes opportunities to create better alignment across teams. Then it becomes a tool to help diagnose a problem (which is usually when Agile coaches are called in). .
It is one of the most commonly used, abused, and misused metrics in Agile software development. Teams, their managers, and even their stakeholders often focus on “improving velocity” without considering the entire value delivery system. Successful Programs for Metrics in Agile. Bad turnover. Measure for a Purpose.
When I first attended Scrummaster training, I went in wide-eyed and excited to learn all of the secrets behind this amazing “new” agile project-management strategy called Scrum. But my employer had just paid for me to go through the training, and I was expected to help improve their development processes.
The rollercoaster ride that is product development is inherently chaotic and ever-changing. Sure, there are semi-quantitative ways of estimating uncertainty for each assumption (for example, the RICE framework for prioritization), but as with many things in product development, these are guess-based models that help us to compare options.
I’ve asked friends who do the job at social events and got the same answer, and frequently asked members of my own teams, who struggled to find the time to do it. To compensate, I’ve seen UX researchers & designers pick up the mantle a lot more, and the design teams have really leaned into this space. What can be cut first?
While software developmentteams have been moving toward agile methods for years, many product managers are only now becoming aware of it. An agile approach applies collaborative and continuous improvement concepts to software development. There is no single, definitive “agile method.”
8 AI trends that will define product development By Greg Sterndale Posted in Digital Transformation , Product Published on: February 12, 2025 Last update: February 10, 2025 From modular architecture to agentic AI How product development will evolve in 2025 & beyond In product development, change is the only constant.
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