Startup Lessons Learned

NOVEMBER 29, 2008

The technical interview is at the heart of these challenges when building a product development team, and so I thought it deserved an entire post on its own. The six key attributes spell ABCDEF: Agility. When talking about their past experience, candidates with agility will know why they did what they did in a given situation.

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

OCTOBER 5, 2008

Eventually, I hope to get them on a full agile diet, with TDD, scrums, sprints, pair programming, and more. But first I think we need to save the product manager from that special form of torture only a waterfall product development team can create. Labels: product development 8comments: Vincent van Wylick said.

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

FEBRUARY 20, 2009

Similar results apply in product management, design, testing, and even operations. When operating with continuous deployment, its almost impossible to have integration conflicts. Luckily, I now have the benefit of a forthcoming book, The Principles of Product Development Flow. Small batches reduce overhead.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

JULY 29, 2009

I hope to show why lean and agile techniques actually reduce the negative impacts of technical debt and increase our ability to take advantage of its positive effects. Startups especially can benefit by using technical debt to experiment, invest in process, and increase their product development leverage.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

OCTOBER 20, 2008

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. Even worse, agile wasnt really helping me ship higher quality software.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

NOVEMBER 13, 2008

Hes a new employee, and he was not properly trained in TDD So far, this isnt much different from the kind of analysis any competent operations team would conduct for a site outage. For my first time, it was scalability problems and our operations team. Now, everyone is learning together - about your product, process, and team.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

NOVEMBER 8, 2008

This theory has become so influential that I have called it one of the three pillars of the lean startup - every bit as important as the changes in technology or the advent of agile development. You can learn about customer development, and quite a bit more, in Steves book The Four Steps to the Epiphany. Expo SF (May.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

APRIL 9, 2009

Thats the essence of so many of the lean startup techniques Ive evangelized: customer development , the Ideas/Code/Data feedback loop , and the adaptation of agile development to the startup experience. Creating a company-wide feedback loop that incorporates both customer development and agile development is a challenge.

San Francisco 132

San Francisco Continuous Deployment Lean Agile 132

Startup Lessons Learned

NOVEMBER 17, 2008

Strategy - startups first encounter this when they have the beginnings of a product, and theyve achieved some amount of product/market fit. Stevey's Blog Rants: Good Agile, Bad Agile Learning from Obama: maneuver warfare on the campa. Expo SF (May. Conference streaming, sponsors, discounted tickets.

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

Startup Lessons Learned

NOVEMBER 7, 2008

Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down? Stevey's Blog Rants: Good Agile, Bad Agile Learning from Obama: maneuver warfare on the campa. Expo SF (May.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

APRIL 14, 2009

Their product definition fluctuates wildly – one month, it’s a dessert topping, the next it’s a floor wax. Their product development team is hard at work on a next-generation product platform, which is designed to offer a new suite of products – but this effort is months behind schedule.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Gregg Fraley, Author of Jack's Notebook

MAY 22, 2019

The Benefits of Innovation Training for Operational Employees. Why is it that organizations don’t invest in training operational employees? Companies are investing in innovation training, mostly learning frameworks like Lean, Agile, or Design Thinking. And management of operations is all about control.

Operations 54

Operations Employee Technical Review Agile 54

Startup Lessons Learned

NOVEMBER 17, 2008

Have you met that prickly operations guy who seems to love servers more than people (but would never let them fail on his watch)? Stevey's Blog Rants: Good Agile, Bad Agile Learning from Obama: maneuver warfare on the campa. Thats because most people have a natural affinity for certain kinds of work. Expo SF (May.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79

Startup Lessons Learned

NOVEMBER 18, 2008

I believe its important that product teams be cross-functional, no matter what other job function the product champion does. . Stevey's Blog Rants: Good Agile, Bad Agile Learning from Obama: maneuver warfare on the campa. Its even more critical in lean startups when they need to manage growth. Expo SF (May.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

JULY 9, 2010

In management jobs related to operations – that is, the people tasked with actually making and distributing physical products – this kind of thinking is now considered ludicrous, thanks to a century of progress. Probably not; it’s much easier to blame the particular person who made the mistakes. Expo SF (May.

San Francisco 161

San Francisco Management Founder Lean 161

Startup Lessons Learned

DECEMBER 6, 2008

When youve mastered that, consider adding operations, customer service, marketing, product management, business development - the idea is that when the team needs to get approval or support from another department, they already have an "insider" who can make it happen. Keep the team size small, maybe just two or three people.

San Francisco 74

San Francisco SCRUM Lean Continuous Deployment 74

Startup Lessons Learned

NOVEMBER 22, 2008

Lessons Learned by Eric Ries Saturday, November 22, 2008 Net Promoter Score: an operational tool to measure customer satisfaction Ive mentioned Net Promoter Score (NPS) in a few previous posts, but havent had a chance to describe it in detail yet. Expo SF (May. Conference streaming, sponsors, discounted tickets.

.Net 158

.Net Operations San Francisco Lean 158

Startup Lessons Learned

DECEMBER 28, 2009

Thats a perfectly reasonable reaction, given that most releases of most products are bad news. Even worse, the sad state of product development generally means that the new "features" are as likely to be ones that make the product worse, not better. Its likely that the new release will contain new bugs.

Continuous Deployment 122

Continuous Deployment San Francisco Lean Metrics 122

Startup Lessons Learned

JUNE 8, 2009

So the product development team was busy creating lots of split-tests for lots of hypotheses. That’s causing the Product Owner and team to spend more time with each other reviewing the results of experiments, which is allowing them to learn and iterate much faster. They’ve learned to see this waste. Expo SF (May.

San Francisco 84

San Francisco Lean Continuous Deployment DC 84

Startup Lessons Learned

DECEMBER 8, 2008

Maybe two different developers made changes to the same underlying subsystem, but in incompatible ways. Maybe operations has changed the OS configuration in production in a way that is incompatible with some developers change. The reason its a risk is that, until you integrate, you dont know if the code is going to work.

Software Review 136

Software Review San Francisco Lean Continuous Deployment 136

Startup Lessons Learned

AUGUST 8, 2009

The economics of these process trade-offs are discussed in the Principles of Product Development Flow.) Heres an excerpt: In a previous article, we called Toyota’s product development system the “second Toyota paradox.&# Labels: product development 5comments: new york web development company said.

Software Review 87

Software Review Design Software San Francisco 87

Startup Lessons Learned

JANUARY 19, 2009

For example, lets say you dont have an operations team, and so youre still getting paged late at night when servers crash. Is it time to make your first operations hire? Returning to our example of the beleaguered founder who still has the pager, before hiring an operations guy, try promoting someone from within to take on the job.

Lean 140

Lean Hiring San Francisco Continuous Deployment 140

Startup Lessons Learned

JANUARY 18, 2010

Lessons Learned by Eric Ries Monday, January 18, 2010 Case Study: Continuous deployment makes releases non-events The following is a case study of one entrepreneurs transition from a traditional development cycle to continuous deployment. Many people still find this idea challenging, even for companies that operate solely on the web.

Continuous Deployment 151

Continuous Deployment San Francisco Lean Wiki 151

Startup Lessons Learned

NOVEMBER 5, 2008

Obama understood the two concepts that are essential for building a high-performance, highly adaptable, agile organization: 1) rapid iteration and 2) clear values-based objectives. Mission synchronization If an organization is changing on a daily basis how is it that it doesnt look "erratic" yet feels "agile." Expo SF (May.

Campaign 84

Campaign San Francisco Lean Agile 84

Startup Lessons Learned

JUNE 15, 2009

One large source of waste in development is “double-checking.&# For example, imagine a team operating in a traditional waterfall development system, without continuous deployment, test-driven development, or continuous integration. When a developer wants to check-in code, this is a very scary moment.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

MAY 7, 2009

The idea was that these two people would operate as a unit, with the mentors job performance during this period evaluated by the performance of the new person. Because this was such a big cultural change for most new employees, we didnt leave them to sink or swim on their own. Expo SF (May. Conference streaming, sponsors, discounted tickets.

San Francisco 131

San Francisco Continuous Deployment Software Review Lean 131

Startup Lessons Learned

MARCH 4, 2009

Heres a representative view from an actual Amazon customer review : We all know how to operate our own entertainment center, but what happens when you have to explain it to your babysitter, mother-in-law, or your wife? Combining agile development with customer developm. Before this remote, I had a Sony RM-AV3000. Expo SF (May.

San Francisco 68

San Francisco Lean Continuous Deployment DC 68

Startup Lessons Learned

FEBRUARY 22, 2009

these devices all need human instruction to enable correct and desired operation. Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down? . Expo SF (May.

Programming 143

Programming San Francisco Lean Continuous Deployment 143

Startup Lessons Learned

SEPTEMBER 8, 2009

I'll add two ideas: The modern structure of university patent licensing and technology transfer works really well in the life sciences and other fields with expensive product development processes. September 9, 2009 7:00 AM Anonymoussaid. Ease the process for startups to get access to global talent. Expo SF (May.

DC 90

DC Washington San Francisco SBIR 90

Startup Lessons Learned

FEBRUARY 22, 2010

I’ve seen many times what happens when a single department get’s holed-up in its own space, like the terrifying “ operations cave.&# I’ve seen many times what happens when a single department get’s holed-up in its own space, like the terrifying “ operations cave.&# Expo SF (May.

San Francisco 167

San Francisco Lean Sweden Continuous Deployment 167

Startup Lessons Learned

OCTOBER 21, 2008

Lean startups operate by a different standard. aka "how you get to product/market fit.") Everything else (including a lot of traditional "agile" or "lean" tactics) is waste. Toyota employs something called "set-based product development" where they develop multiple versions of a product at once.

Lean 121

Lean San Francisco Continuous Deployment Startup 121

Startup Lessons Learned

JANUARY 4, 2009

Im talking about the actual data-fetching operation. This information is normally maintained by your operations team. Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down?

San Francisco 151

San Francisco Architecture Startup Database 151

Startup Lessons Learned

MARCH 23, 2009

Pretty soon you’re chasing your own tail a little bit because you’re not operating against a clear, long-term vision of what you’re trying to accomplish. Combining agile development with customer developm. Expo SF (May. Conference streaming, sponsors, discounted tickets.

San Francisco 167

San Francisco Lean Continuous Deployment Audio 167

Startup Lessons Learned

JANUARY 12, 2009

But I think debates about which language, which operating system, even which editor (emacs, vim, Visual Studio) can go on forever. However, it made me remember that Im tired of technology arguments. Dont get me wrong, the right tool should be used for the right problem. Expo SF (May. Conference streaming, sponsors, discounted tickets.

PHP 166

PHP Software Review Ruby San Francisco 166

Startup Lessons Learned

NOVEMBER 5, 2008

Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down? Stevey's Blog Rants: Good Agile, Bad Agile Learning from Obama: maneuver warfare on the campa. Expo SF (May.

Advertising 60

Advertising San Francisco Media Continuous Deployment 60

Startup Lessons Learned

NOVEMBER 19, 2008

FYI the surveymonkey link isnt operational. Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down? November 19, 2008 5:57 PM McElroy Flavelle said. Expo SF (May.

San Francisco 60

San Francisco Lean Continuous Deployment DC 60

Startup Lessons Learned

MARCH 20, 2009

They started building BASIC interpreters, but evolved into the worlds largest operating systems monopoly. Each of these companies were fortunate to have enough time, resources, and patience to endure the multiple iterations it took to find a successful product and market. . Combining agile development with customer developm.

Lean 68

Lean San Francisco Continuous Deployment DC 68