The Principles of Product Development Flow

Startup Lessons Learned

Lessons Learned by Eric Ries Monday, July 13, 2009 The Principles of Product Development Flow If youve ever wondered why agile or lean development techniques work, The Principles of Product Development Flow: Second Generation Lean Product Development by Donald G.

[Interview] Michael K. Levine, Author Of “People Over Process: Leadership for Agility”

YoungUpstarts

Though agile is all about process and that’s where much of our attention has gone, it’s time we shifted out focus on people and interactions. In his new book “ People Over Process: Leadership for Agility “, technology expert Michael K.

Agile 130

Lessons Learned: Product development leverage

Startup Lessons Learned

Lessons Learned by Eric Ries Sunday, April 26, 2009 Product development leverage Leverage has once again become a dirty word in the world of finance, and rightly so. But I want to talk about a different kind of leverage, the kind that you can get in product development. Its a force that allows startups to build products at parity with much larger companies - cheaper and much faster. In the end, I believe they co-created our product with us.

Agile Marketing: How to Implement Scrum for Digital Marketing

ConversionXL

Agile marketing may not be a phrase you hear often, but it’s becoming increasingly popular and important. An Introduction to Scrum and Agile Development. Scrum is a framework for developing and sustaining complex products.” The Product Owner.

SCRUM 129

Thoughts on scientific product development

Startup Lessons Learned

Lessons Learned by Eric Ries Monday, September 22, 2008 Thoughts on scientific product development I enjoyed reading a post today from Laserlike (Mike Speiser), on Scientific product development. By embracing a scientific approach to product development, not only will your business have a much higher probability of success, but it will also be a more fun and creative place to work. By starting a new product off with as few features as possible (1?),

Lessons Learned: Combining agile development with customer development

Startup Lessons Learned

Lessons Learned by Eric Ries Monday, March 16, 2009 Combining agile development with customer development Today I read an excellent blog post that I just had to share. Jim Murphy is a long-time agile practitioner in startups. In most agile development systems, there is a notion of the "product backlog" a prioritized list of what software is most valuable to be developed next. But startups sometimes have trouble applying agile successfully.

Agile 89

Lessons Learned: Stevey's Blog Rants: Good Agile, Bad Agile

Startup Lessons Learned

Lessons Learned by Eric Ries Thursday, November 6, 2008 Steveys Blog Rants: Good Agile, Bad Agile I thought Id share an interesting post from someone with a decidedly anti-agile point of view. Steveys Blog Rants: Good Agile, Bad Agile : "Google is an exceptionally disciplined company, from a software-engineering perspective. They take things like unit testing, design documents and code reviews more seriously than any other company Ive even heard about.

Agile 68

Kent Beck keynote, "To Agility, and Beyond"

Startup Lessons Learned

Lessons Learned by Eric Ries Sunday, April 4, 2010 Kent Beck keynote, "To Agility, and Beyond" Kent Beck will give the opening keynote at the Startup Lessons Learned conference on April 23. Kent is a significant figure in the field of software development.

Agile 111

The Customer Development Manifesto: Reasons for the Revolution.

Steve Blank

After 20 years of working in startups, I decided to take a step back and look at the product development model I had been following and see why it usually failed to provide useful guidance in activities outside the building – sales, marketing and business development. Every startup has some methodology for product development, launch and life-cycle management. Yet at the end of the day even with all these processes 9 out of 10 of new products are failures.

Empower Operational Employees to Innovate

Gregg Fraley, Author of Jack's Notebook

Companies are investing in innovation training, mostly learning frameworks like Lean, Agile, or Design Thinking. Nearly all that training is for dedicated innovation teams , or employees who are focused on new product development.

The Lean Startup at Agile Vancouver April 21st

Startup Lessons Learned

Lessons Learned by Eric Ries Wednesday, March 25, 2009 The Lean Startup at Agile Vancouver April 21st A surprising number of respondents in the latest Lessons Learned survey hail from one of the flourishing startup hubs in Canada. In keeping with my recent theme of blogging about upcoming events, Im happy to announce that Ill be speaking at Agile Vancouver on April 21. This workshop brings together leading thinkers from Lean Production and Lean software.

Agile 60

Customer Development Manifesto: The Path of Warriors and Winners.

Steve Blank

This post describes a solution – the Customer Development Model. In future posts I’ll describe how Eric Ries and the Lean Startup concept provide the equivalent model for product development activities inside the building and neatly integrates customer and agile development.

Twitter Link Roundup #130 – Small Business, Social Media, Design, Copywriting, Marketing And More

crowdSPRING Blog

These posts and videos are about logo design , web design , startups, entrepreneurship, small business, leadership, social media, marketing, and more! How to Increase Trust for a Landing Page Design – [link]. Better Agile Than Smart – [link].

Refactoring for TDD and interaction design

Startup Lessons Learned

Lessons Learned by Eric Ries Saturday, August 30, 2008 Refactoring for TDD and interaction design In TDD , we follow a rhythm of “test-code-refactor.&# This basic pattern is useful in all aspects of product development. The same process works in Interaction Design. The temptation is try and build a toolkit of general pieces, which can be assembled into many kinds of final product.

Embracing Digital Disruption in the Business World

The Startup Magazine

From marketing to product development, to new software tools and communications, the list is almost endless as to the digital transformations taking place. When designers and editors scroll through Everypixel no time is wasted with trashy images.

Stock 106

How to Structure a Modern, Customer-Driven Product Team

View from Seed

According to David Cancel , CEO of Drift , the optimal number of members in a product team at a young startup is three. The point isn’t “to organize a product team better.” All of the products and services that we create are ultimately connected with the customer.

Lessons Learned: When NOT to listen to your users; when NOT to.

Startup Lessons Learned

Lessons Learned by Eric Ries Monday, October 6, 2008 When NOT to listen to your users; when NOT to rely on split-tests There are three legs to the lean startup concept: agile product development , low-cost (fast to market) platforms , and rapid-iteration customer development. They need to incorporate customer feedback into the product development and business planning process. If were going to build a product, we need to have a sense of who will use it.

The Customer Development Manifesto: Reasons for the Revolution.

Steve Blank

This post describes how the traditional product development model distorts startup sales, marketing and business development. In the next few posts that follow, I’ll describe how thinking of a solution to this model’s failures led to the Customer Development Model – that offers a new way to approach startup sales and marketing activities. Once the product begins to ship, startup sales execs use orders and revenue as its marker of progress in understanding customers.

Good enough never is (or is it?)

Startup Lessons Learned

One of the sayings I hear from talented managers in product development is, “good enough never is.&# And, most importantly, it helps team members develop the courage to stand up for these values in stressful situations. Minimum viable products are not a single hypothesis.

The Customer Development Manifesto: The Startup Death Spiral (part.

Steve Blank

This post describes how following the traditional product development can lead to a “startup death spiral.&# In the next posts that follow, I’ll describe how this model’s failures led to the Customer Development Model – offering a new way to approach startup sales and marketing activities. To support sales, Marketing tries to “make up a better story,” and the web site and/or product presentation slides start changing (sometimes weekly or even daily).

Customer Development Manifesto: Market Type (part 4) « Steve Blank

Steve Blank

In future posts I’ll describe how Eric Ries and the Lean Startup concept provided the equivalent model for product development activities inside the building and neatly integrates customer and agile development. The product development model treats all startups like they are in an Existing Market – an established market with known customers. In 1996 Palm was selling a product that allowed users to do something they couldn’t do before.

How to Build Robust User Personas in Under a Month

ConversionXL

Customer personas are often talked about in marketing and product design, but they’re almost never done well. The alternative, an “elastic user,” would be a design target that stretches to the whims of the design team.

Agile 128

Does Scrum Apply To All Types Of Projects?

The Startup Magazine

All of us know in software companies that scrum is the most significant agile methodology for handling software projects. Scrum is a lightweight agile process framework used primarily for managing software development. Articrafts: Product backlog, Sprint backlog.

SCRUM 131

Revisiting the Software Design Manifesto (and what's changed since.

Startup Lessons Learned

Lessons Learned by Eric Ries Saturday, August 8, 2009 Revisiting the Software Design Manifesto (and whats changed since then) My recent article on technical debt and its positive uses generated a fair bit of controversy. One of the topics that raised heated debate was whether I had conflated technical design with product design , because I made the admittedly counter-intuitive claim that sometimes good technical design actually leads to increased technical debt.

Lessons Learned: The engineering manager's lament

Startup Lessons Learned

Lessons Learned by Eric Ries Monday, October 20, 2008 The engineering managers lament I was inspired to write The product managers lament while meeting with a startup struggling to figure out what had gone wrong with their product development process. When a process is not working, theres usually somebody who feels the pain most acutely, and in that company it was the product manager. He has a good team, and theyve shipped a working product to many customers.

Why Companies and Government Do “Innovation Theater” Instead of Actual Innovation

Steve Blank

If they were a commercial company, they figured out product/market fit; or if a government organization, it focused on solution/mission fit. Process Versus Product. And by product, I mean the creation of new hardware, services, software, tools, operations, tradecraft, etc.

Tesla and Adobe: Why Continuous Deployment May Mean Continuous Customer Disappointment

Steve Blank

For the last 75 years products (both durable goods and software) were built via Waterfall development. This process forced companies to release and launch products by model years, and market new and “improved” versions. The Old Days – Waterfall Product Development.

How to Build Robust User Personas in Under a Month

ConversionXL

User personas are often talked about in marketing and product design, but they’re almost never done well. Cooper framed personas as a way of avoiding designing for an “elastic” user, and thus cementing some sort of common properties across segments to aid cohesive design strategy.

Agile 123

Why Build, Measure, Learn – isn’t just throwing things against the wall to see if they work

Steve Blank

I am always surprised when critics complain that the Lean Startup’s Build, Measure, Learn approach is nothing more than “throwing incomplete products out of the building to see if they work.”. Waterfall Development. It often took companies three tries to get products right.

Pivot, don't jump to a new vision

Startup Lessons Learned

Each has its own iterative process: customer development and agile development respectively. The hardest part of entrepreneurship is to develop the judgment to know when its time to change direction and when its time to stay the course. As Steve writes in the Four Steps to the Epiphany , we always seek to find a market for the product as currently specified , not conduct a focus group to tell us what the spec should be. Why don't you call this product pivot.

Why The Government is Isn’t a Bigger Version of a Startup

Steve Blank

Some of the best and brightest wanted to work for defense contractors or corporate research and development labs. Indeed, Silicon Valley was born as a center for weapon systems development and its software and silicon helped end the Cold War.

Lessons Learned: Just-In-Time Scalability

Startup Lessons Learned

We wanted an agile approach that would allow us to build our software architecture as we needed it, without downtime, but also without large amounts of up-front cost. After all, the worst kind of waste in software development is code to support a use case that never materializes. You can also download our presentation, " Just-In-Time Scalability: Agile Methods to Support Massive Growth." Labels: agile , continuous deployment 1 comments: timothyfitz said.

Maybe not so much with the "optimization"

A Smart Bear: Startups and Marketing for Geeks

When we demand overwhelming customer outcry before committing to the slightest product change, we're in danger of losing the value of creating a cool feature that takes too much effort but people just love. Code Historian was my first product.

Lean 248

Lessons Learned: Throwing away working code

Startup Lessons Learned

This builds on a lot of great thinking that has come before, like the agile movements insistence that only the creation of working code counts as progress for a software development team. Customers dont care if you have good metrics, only if you have a good product. We picked those numbers by counting up the numbers of friends, family, and relatives we thought we could cajole into buying our early product. Labels: product development 4comments: Doug said.

Fear of Failure and Lack of Speed In a Large Corporation

Steve Blank

And when we do make bets, they’re small bets on incremental products or acquisitions that simply add to the bottom line.”. More agile competitors are starting to eat into our business. I suggested the best place to start the conversation is with the 21 st century definition of a startup: A startup is a temporary organization designed to search for a repeatable and scalable business model. They’ve found product/market fit (what products customers want to buy).

Widget 257

Why Companies are Not Startups

Steve Blank

These groups are adapting or adopting the practices of startups and accelerators – disruption and innovation rather than direct competition, customer development versus more product features, agility and speed versus lowest cost. By design not by exception.

Smarticus — 10 things you could be doing to your code right now

Startup Lessons Learned

Lessons Learned by Eric Ries Wednesday, September 10, 2008 Smarticus — 10 things you could be doing to your code right now Smarticus — 10 things you could be doing to your code right now A great checklist of techniques and tools for making your development more agile, written from a Rail perspective. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

Lessons Learned: Test-Driven Development as andon cord

Startup Lessons Learned

Lessons Learned by Eric Ries Monday, September 1, 2008 Test-Driven Development as andon cord You cannot control what you cannot see, and the hardest part of managing software projects is that the final product is so intangible. In almost all Agile Development systems, thousands of automated tests are run against every change to the software. This is equivalent of the andon cord in a Toyota production plant.

How To Hire Scrum For Your Startup

YoungUpstarts

So, what you do now is that you basically approach a development company, you put up your requirements to them and then after discussions the company promises you to deliver the app one year later. This solution is a philosophy, and this philosophy is AGILE.

SCRUM 141

Is the Lean Startup Dead?

Steve Blank

Reading the NY Times article “ Jeffrey Katzenberg Raises $1 Billion for Short-Form Video Venture, ” I realized it was time for a new startup heuristic: the amount of customer discovery and product-market fit you need to find is inversely proportional to the amount and availability of risk capital. First Movers” didn’t understand customer problems or the product features that solved those problems (what we now call product-market fit).

Lean 260

Speed up or slow down? (for Harvard Business Review)

Startup Lessons Learned

for Harvard Business Review) Over at Harvard Business Review, Ive been building up a series designed to introduce the Lean Startup methodology to a business-focused audience. This is the first post that moves into making specific process recommendations for product development.

Why Your Startup Needs to Track and Manage User Feedback

The Startup Magazine

Among these obstacles exists the idea of product viability and adaptability. While the success of a product is heavily dependent upon value, it’s not uncommon for many to fail in their very early stages—this is especially true with little funding, research, and long-term planning.

Building Great Founding Teams

Steve Blank

Its goal is to take the original idea and search for a repeatable and scalable business model - first by finding product/market fit, then by testing all the parts of the business model (pricing, channel, acquisition/activation, partners, costs, etc.).