Agile Product Development: How to Design Innovative Products That Create Customer Value
Language: English
Pages: 204
ISBN: 1484210689
Format: PDF / Kindle (mobi) / ePub
Discover what it takes to develop products that blow your users away—and take market share from your competitors. This book will explain how the principles behind agile product development help designers, developers, architects, and product managers create awesome products; and how to look beyond a shiny user interface to build a great product. Most importantly, this book will give you a shared framework for your product development team to collaborate effectively.
Product development involves several key activities—including ideation, discovery, design, development, and delivery—and yet too many companies and innovators focus on just a few of them much to the detriment of the product’s success in the marketplace. As a result we still continue to see high failure rates in new product development, be it inside organizations or startups. Unfortunately, or rather fortunately, these failures are largely avoidable.
In the last fifteen years, advances in agile software development, lean product development, human-centered design, design thinking, lean startups and product delivery have helped improve individual aspects of product development. However, not enough guidance has been available to integrate them in the context of the product development life cycle.
Until now. Product developer extraordinaire Tathagat Varma in Agile Product Development integrates individual knowledge areas into a field manual for product developers. Organized in the way an idea germinates, sprouts, and grows, the book synthesizes the body of knowledge in a pragmatic way that is more natural to the entire product creation process rather than from individual practices that constitute it.
In today’s hyper-innovative world, being first to the market, or delivering feature-loaded products, or even offering the latest technology doesn’t guarantee success anymore. Sure, those elements are all needed in the right measures, but they are not sufficient by themselves. And getting it right couldn’t be more important: Building products that deliver awesome user experiences is the top challenge facing businesses today, especially in a post-Apple world where user experience and design has been elevated to a cult status.
What you’ll learn
- How to stimulate creativity and prioritization of ideas in product design
- How to get early feedback on initial product idea iterations
- How to design and develop products using sound engineering practices
- How to apply principles of agility into software delivery
Who this book is for
Entrepreneurs, designers, developers, product managers, software architects.
Table of Contents
Chapter 1: Preamble
Chapter 2: Discover
Chapter 3: Deliberate
Chapter 4: Describe
Chapter 5: Design
Chapter 6: Develop
Chapter 7: Deliver
at least a hundred citations. These were more than six times as likely to come from a team of scientists. This is an interesting observation—backed by solid research and data—.that flies in the face of the “lone genius myth” There is enough data to suggest that we are facing more and more complex problems than what a single human mind can individually comprehend, and perhaps cross-functional problems need multiple specialists to collaborate more than ever before. A key aspect of a
product boxes might be full of features and details, but these features and details might make the product seem cumbersome. The idea is to capture the most compelling set of product features that drive the right message across, and help a potential customer understand the product better, and expedite the buying process, ideally in your favor. 2 www.gnpd.com/sinatra/gnpd/frontpage/?__cc=1. “Why Most Product Launches Fail,” Joan Schneider and Julie Hall, https://hbr.
sentence”: Design is to design a design to produce a design. 109 110 Chapter 5 | Design He identified design as the overall concept that entails using “design” as a verb. He also describes it as the process behind the overall concept. In addition, he indicates that “design” refers to some idea or concept being developed. Finally, Heskett suggests that “design” is the final, tangible outcome. He recognizes that design takes place at multiple levels. We can say the same about design in the
he ended up writing the 1975 software project management classic The Mythical Man-Month. In the book, Brooks identifies several issues leading to a software project’s going awry: • Techniques of estimating are poorly developed. • Estimating techniques fallaciously confuse effort with progress. • Because we are uncertain of estimates, we are not able to forecast accurately. • Schedule progress is poorly monitored. • Manpower is added to a late project. Unfortunately, there was no real
something wrong in the way you have implemented it. It should be the silent hum of the engine running somewhere in the background that ensures your teams can peacefully do why you hired them for in the first place—design innovative products that create customer value! Welcome to the journey… 181 I Index A process methodologies, 19 responding to change, 26 signing, 17 source of uncertainty, 22 upper-management consultants, 18 wicked problems, 23 working software, 26 a priori, 3 finite state