Remove Agile Remove Roadmap Remove Software Review
article thumbnail

519: Product verification, most important of the 19 activities of product management – with Nishant Parikh

Product Innovation Educators

How product managers can adapt core responsibilities across different organizations and contexts Watch on YouTube TLDR Through his research and practical experience at MasterCard, Nishant Parikh identified 19 key activities that define the role of software product managers. Why study the 19 key activities of software product managers?

article thumbnail

10 Tips for Creating an Agile Product Roadmap

Roman Pichler

Whenever you are faced with an agile, dynamic environment—be it that your product is young and is experiencing significant change or that the market is dynamic with new competitors or technologies introducing change, you should work with a goal-oriented product roadmap, sometimes also referred to as theme-based. 4 Keep it Simple.

Roadmap 350
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Book review: “Product Roadmaps Relaunched”

bpma ProductHub

How would you assess your own roadmapping process? A new book, Product Roadmaps Relaunched, could help you re-think and re-launch your approach to Product Roadmapping. The 11-chapters are a master class on product roadmapping, and is supported by 65+ interviews from real practitioners. Register @ www.bostonproducts.org.

Books 394
article thumbnail

How Agile Has Changed Product Management

Roman Pichler

Before the advent of agile frameworks 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.

Agile 261
article thumbnail

Run Less Software

Intercom, Inc.

The same is true in software. In this battle, I’ve found a secret weapon hidden within one of our core engineering strategies, an idea called Run Less Software. As well as being a critical philosophy behind how we build software, it also represents how I feel about the software industry and technology in general.

article thumbnail

Treat Your Product Team Like a Product

The Product Guy

Since there was no active grooming or planning session with the engineers, daily standups played the role of requirement review meetings. Any agile practitioner may recognize these as poor practices and it is surprising how easily a team can succumb when operating in a high pressure, reactive environment. Long standups.

article thumbnail

Dealing with an Underperforming Development Team

Roman Pichler

Before I discuss how you can help an underachieving team, let’s briefly explore what good performance looks like, assuming that an agile, Scrum-based process is used. What’s more, an agile, self-managing team is collectively responsible for their performance. It is hence in your best interest to help the team get back on track.