Book Image

Lean Product Management

By : Mangalam Nandakumar
Book Image

Lean Product Management

By: Mangalam Nandakumar

Overview of this book

Lean Product Management is about finding the smartest way to build an Impact Driven Product that can deliver value to customers and meet business outcomes when operating under internal and external constraints. Author, Mangalam Nandakumar, is a product management expert, with over 17 years of experience in the field. Businesses today are competing to innovate. Cost is no longer the constraint, execution is. It is essential for any business to harness whatever competitive advantage they can, and it is absolutely vital to deliver the best customer experience possible. The opportunities for creating impact are there, but product managers have to improvise on their strategy every day in order to capitalize on them. This is the Agile battleground, where you need to stay Lean and be able to respond to abstract feedback from an ever shifting market. This is where Lean Product Management will help you thrive. Lean Product Management is an essential guide for product managers, and to anyone embarking on a new product development. Mangalam Nandakumar will help you to align your product strategy with business outcomes and customer impact. She introduces the concept of investing in Key Business Outcomes as part of the product strategy in order to provide an objective metric about which product idea and strategy to pursue. You will learn how to create impactful end-to-end product experiences by engaging stakeholders and reacting to external feedback.
Table of Contents (19 chapters)
Lean Product Management
Contributors
Preface
Another Book You May Enjoy
Index

Why can estimates not be accurate?


Estimating software development effort is not just a well-established routine anymore. I'm afraid that it is evolving into a branch of science! For decades now, software teams have tried to come up with various methods to predict timelines.

About 15 years ago, I used Function Points as a way to assess the size of an application, based on how much input / output data the application had to handle. This was at a stage where a system view of a software was more prevalent and the applications were mostly about data flow. There was little user input. User experience was never discussed. This meant that software developers could be given requirement specifications, with details of what field to input and what to validate for each input. Here, implementation specifics were closely tied to the requirements specifications. A change in implementation specifics or the addition of a new field to capture, would impact the size of the application in terms of Function...