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
He emphasizes that these activities vary based on context (large vs. small organizations, B2B vs. B2C, Agile vs. Waterfall). The discussion reveals how product management has evolved since 1931 and highlights the importance of clear role definition to prevent job frustration.
Featuring an engaging discussion with Inis Hormann (Marketing Director Germany, Cepheid) and Steve Kury (Leadership Development Consultant, SHK Leadership Consulting), the session provided actionable insights for PMs at every level. The Future of PM Leadership As we approach 2025, product management roles are transforming.
How product managers can navigate leadership challenges Today we are talking about four leadership motions that enable increased organizational effectiveness and productivity and alleviate organizational friction, waste, and indecision. Sharing the four leadership motions with us is Janice Fraser. Measure outcomes.
Holding regular Agile retrospectives can be very useful in this regard and allow a safer communication to happen within the team. This can be done for example by involving the developers and product owners in the user research, the wireframes assessment and the usability testing sessions. Resource management. Stakeholder engagement.
Speaker: Peter Taylor, Speaker/Author, The Lazy Project Manager
Business agile is an approach that gives the right business flexibility and fast decision-making in a volatile environment, providing a great capacity for innovation, adaptation and change. Businesses everywhere are trying to “get business agile”—but it’s not easy to adapt to becoming this adaptive.
When you have one team learning Agile, another learning Lean, and yet another learning Design Thinking, how are you supposed to get to alignment? Everyone speaks a different language, works at a different pace, aims for different goals, and leadership is in the middle trying to understand how best to help. What is Agile Really About?
The sales team and leadership promised the clients to deliver the product without having any discussion with the engineering team. The Aviation Authority and leadership were appalled by our product. Even though we called ourselves an agile team, we delivered our product using a waterfall method. No one liked the product.
Despite the successes Agile has brought us, it’s time to take the things we have learned from Agile and move on. Like the technology we use to build the products we love ages and gets left behind, Agile has died while we were perfecting our standup. We are in a post-Agile world and the terrain has changed.
David Bland is the CEO and Founder of Precoil, an author, and a long-time practitioner of agile and lean startup. He joined us on the podcast to talk about how to create focus around what matters to your users by using different testing methodologies – a topic he and Alex Osterwalder cover in their book, Testing Business Ideas.
The ideas of Agile are great. 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. Comparing and contrasting Lean and Agile.
Jeffrey Fredrick and Douglas Squirrel know this well, and their new book Agile Conversations , focuses on the five critical conversations you’ll have and how to perfect them. She has worked on a diverse range of products – leading the product teams through discovery, prototyping, testing and delivery. Quote of the Episode.
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.
Challenging situations are great opportunities to grow as a human being and by doing so, you increase your leadership power. Check out my product management test that helps you assess your product management knowledge and indicates gaps and weaknesses, so you can make a focused effort to strengthen your expertise. Trust me.”.
We talk a lot about empowered or self-organizing teams in the agile community. When Mark Kilby and I wrote From Chaos to Successful Distributed Agile Teams , we said the easiest way to create a system that worked for the team was for the team to create its own board. Agile Approaches Require Management Cultural Change.
As Product Manager for a scrappy startup, I led agile sprints, collaborated with leadership and engineers, created user stories, and managed Jira. After re-prioritizing the backlog, I created a new process where at the end of each sprint, the team would present a demo, and we would test and close the JIRA tickets together.
This individual leads the product team, not by being the boss but by exercising emergent leadership. The skills typically include architecture, programming, testing, and if the product is end-user facing, UX design capabilities. Additionally, it is based on my leadership work, especially my book How to Lead in Product Management. [2]
Scrum is a popular agile framework. Forming such a team connects the person in charge of the product—the product owner—with the people who design, architect, program, test, and document the solution—the developers. I believe that the first definition is more helpful, especially in an agile context.
What You’ll Learn: Fail Fast, Learn Fast: The value of testing quickly. He reflects on how getting feedback early can prevent costly mistakes and save precious time and resources, especially for startups with limited runway. If youve ever wondered how to avoid wasted effort, this episode will provide the answers.
Experimentation is not about testing guesses and hoping a “magic number” will move. Instead, start building educated hypotheses about problems your users have, how you might solve those problems, and create your tests out of those hypotheses. The key to this empowerment is aligning the team around customer-centric product development.
That’s another level of difficulty and in her new book, The Team That Managed Itself: A Story Of Leadership, Christina Wodtke does just that. That’s another level of difficulty and in her new book, The Team That Managed Itself: A Story Of Leadership, Christina Wodtke does just that. Drawing [.]. Using feedback effectively.
At ProductTank London, Lean & Agile Enterprise Coach Debbie Wren shares insights into successfully scaling autonomous teams. Agile Isn’t Something you do, it’s Something you are. Rather than a process which you follow, agility is the beliefs, values and principles with which your team or organisation operates.
This involves: Screening ideas against predefined criteria Combining multiple ideas to create stronger concepts Selecting the most viable ideas for prototyping and testing By carefully evaluating ideas, you ensure that only the most promising concepts move forward in the product development process.
Now, these same managers want business agility. The more we remove, the more agility or improvement we might see. Over those 10 years, the technical teams created more robust testing and deployment scripts. As the teams used agile approaches, they requested more and more frequent deployments.
Tim is Product Director at Iridion, a trainer and coach, a co-organiser of ProductTank Hamburg, a frequent speaker, and the author of Lateral Leadership. Links mentioned in this episode: The Agile Peer Canvas. Lateral Leadership – Buy the book now! Links mentioned in this episode: * The Agile Peer Canvas.
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.
Did you know you can maximize your chances of achieving desired business outcomes by combining DevOps with an Agile transformation? When you hear “Business Outcomes,” “DevOps,” and/or Agile transformation” – what comes to mind? Agile Transformation. Agile transformations and DevOps initiatives are complementary.
Embracing new technologies like machine learning, micro services, big data, and Internet of Things (IoT) is part of that change, as is the introduction of agile practices including cross-functional and self-organising teams, DevOps, Scrum, and Kanban. Strategy and leadership skills are nice-to-have but not mandatory.
When we compare today’s agile product management in practice with what we have seen some 10 years ago, not much has changed: Agility is still mainly limited to UX labs and A/B testing, and misses the potential value that could be found between the initial idea and a working product. The post Lost in the Agile Jungle?
Investors told startups to act like smaller versions of large companies—coming up with a business plan on paper without talking to customers or testing prototypes. Customer Development, Agile Engineering, and the Business Model Canvas became the Lean Startup. Role of Leadership: The VP of Sales most often kills innovation.
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
The recent Harvard Business Review (HBR) article “ The Agile C-Suite ” 1 and Forbes article “Agile Isn’t New: What’s New Is The C-Suite Embracing It” have prompted some good discussion around the Agile Velocity virtual water cooler. . However, the case being made in this article is that “Agile is primarily for innovation”.
I worked with the product leadership to plan out a product strategy. From that success, I was then officially asked to move into the product role by the product leadership, and I have not looked back since then. Anyone can learn agile product development , basics of software design and development lifecycle, etc.
Often the senior leadership team thinks they talk about strategy a lot, but the employees under them don’t understand the strategy. When I see that type of thing happening, I tell the senior leadership team to ask their CEO, “What’s your strategy?” In general, I’m a believer in agile more so than in Agile.
As a product leader, you are the product manager for a leadership team, and the tricks you learned in product teams remain valuable, they just need a little tweak. Working with agility requires a continual cycle of collaboration, delivery, reflection, and improvement. Value Proposition. This was daunting at first. Product Lifecycle.
If you’ve got a background in waterfall processes, it can seem as if agile techniques are just about making it up as you go along. She has worked on a diverse range of products – leading the product teams through discovery, prototyping, testing and delivery.
With our expert guests, Garrett Lang (PlateRate, Founder and President) and Amil Shah (RBC Capital Markets, Senior Product Manager) , we discussed strategies for balancing leadership pressures, navigating feature requests, and crafting a personal brand that opens doors to new opportunities.
Shipbuilding in 1628 was not unlike the way many agile software development teams operate. Shortly before the official launch party, one nervous engineer decided it might be worth doing a few integration and acceptance tests on the ship. Of course such things are common on any failure to launch a product as well. So what did go wrong?
Historically, we’ve asked product teams to deliver a fixed roadmap typically defined by leadership. It’s easy to focus on the new skills we need— interviewing , prototyping , testing assumptions , and so forth—but today I want to talk about the mindsets we need to become a successful outcome-driven product team.
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 agileleadership we want to see in agile teams.
In the way back time, before Agile, before OKRs and other fads, product managers wrote MRDs, or Market Requirement Documents. The leadership team asked for a formal Market Requirements Document to help their decision process. That is the question. A recent project, a complete re-do of one of our flagship products was needed.
Before the pandemic, many organisations had already chosen to go agile. The pandemic has however stress tested our agility (or ‘wagility’) with deep embedded, organisational processes and roles being challenged.
A few years ago, I was asked to help a healthcare company with their agile transition and its impact on product management. One of the challenges the agile transition team was concerned about was the choice of the right product backlog tool, which at first seemed odd to me. Third, they can be tested.
Our teams were already experienced in Agile development and were working in two week sprints, with a regression test and proposed release at the end of each sprint, but the business stakeholders were still concerned about the speed of delivery. Starting Point.
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.
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