This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
Guest post by Lisa Regan, writer for The Lean Startup Conference. We’ve made some cool additions to our pre-conference webcast lineup , including two conversations with founding figures for methods that underlie Lean Startup. At a conference I overheard a couple of programmers make a snarky comment about Test-Driven Development.
No wait, I forgot, actually the question is: What happens when employee #2 makes off with your code and roadmap and marketing data and customer list, moves to Bolivia, and starts selling your stuff world-wide at one-tenth the price? You don't have an "edge" just because you're passionate, hard-working, or "lean.". Like what??
I am convinced one of Joel Spolskys lasting contributions to the field of managing software teams will turn out to be the Joel Test , a checklist of 12 essential practices that you could use to rate the effectiveness of a softwareproductdevelopment team. Do you fix bugs before writing code? Completely necessary.
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 productdevelopment process. The current code is spaghetti, but the new code will be elegant.
A new bit of code contained an infinite loop! why did that code get written? 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. Most engineers would ship code to production on their first day.
This source is a major focus these days, due to government initiatives to incent research and development on alternative energy and other technologies. Software apps that once required a 10-person team can now be done with the LeanDevelopment methodology by two people in a couple of months.
It became harder and harder to separate how the software is built from how the software is structured. If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? If not, whos going to insist we switch to free and open source software? I dont think so.
The problem is that professional investors (angels and venture capital) want a proven business model before they invest, ready to scale, rather than early projections and productdevelopment. Software apps that once required a 10-person team can now be done with the LeanDevelopment methodology by two people in a couple of months.
Integration risk is the term I use to describe the costs of having code sitting on some, but not all, developers machines. It happens whenever youre writing code on your own machine, or you have a team working on a branch. It also happens whenever you have code that is checked-in, but not yet deployed anywhere.
This post was written by Sarah Milstein, co-host of The Lean Startup Conference. We’re looking for speakers for the 2013 Lean Startup Conference. If you’re a Lean Startup veteran, feel free to skim the beginning, as this is mostly stuff you already know. Last week, we announced that our short application form was live.
Each specialist takes up his part of the spec (UI, middleware, backend) and cranks out code. This system naturally lends itself to a pipeline approach, which the product manager organizes. So the product manager winds up actually having to use the software, by hand, updating the spec and helping create a new test plan.
The problem is that professional investors (angels and venture capital) want a proven business model before they invest, ready to scale, rather than early projections and productdevelopment. Software apps that once required a 10-person team can now be done with the LeanDevelopment methodology by two people in a couple of months.
Lessons Learned by Eric Ries Friday, February 20, 2009 Work in small batches Software should be designed, written, and deployed in small batches. I owe it originally to lean manufacturing books like Lean Thinking and Toyota Production System. For software, the easiest batch to see is code.
Of all the tactics I have advocated as part of the lean startup , none has provoked as many extreme reactions as continuous deployment , a process that allows companies to release software in minutes instead of days, weeks, or months. When a developer wants to check-in code, this is a very scary moment.
It wasn’t always perfect, but it was way more right than wrong, It informed our productdevelopment to a great degree and kept us working on more or less the right stuff. Pragmatic and Lean. Basically if you didn’t code or sell, you were semi-worthless. Back then he advocated for. What a gift! Lessons Learned.
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. But there is more to technical debt than just the interest payments that come due. Unfortunately, customers hated that initial product.
I know that this all seems obvious now with the movements started by Steven Blank ( Four Steps of Epiphany ) with the whole Customer Development processes / Lean Startup movements also popularized by people like Eric Ries. They had decided to take a Digg style approach to productdevelopment. Back then it seemed foreign.
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 productdevelopment.
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 productdevelopment. The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May.
This article previously appeared in the Harvard Business Review. HR processes, legal processes, financial processes, acquisition and contracting processes, security processes, productdevelopment and management processes, and types of organizational forms etc. Process Versus Product.
Lessons Learned by Eric Ries Monday, August 3, 2009 Minimum Viable Product: a guide One of the most important lean startup techniques is called the minimum viable product. I was delighted to be asked to give a brief talk about the MVP at the inaugural meetup of the lean startup circle here in San Francisco. Thanks Eric.
Our code pushes take another six minutes. Since these two steps are pipelined that means at peak we’re pushing a new revision of the code to the website every nine minutes. On average we deploy new code fifty times a day. Codereviews and pairing Great practices. Throwing out a lot of code.
Long before there was the Lean Startup, Business Model Canvas or Customer Development there was a guy in Santa Barbara California who had already figured it out. Frank Robinson of SyncDev has been helping companies figure out their minimum viable product and pivots since 1984, long before I even knew what it meant.
Kent is a significant figure in the field of softwaredevelopment. To his credit are Extreme Programming , jUnit, patterns, TDD , the list goes on. Kent is a significant figure in the field of softwaredevelopment. To his credit are Extreme Programming , jUnit, patterns, TDD , the list goes on. Expo SF (May.
Lessons Learned by Eric Ries Monday, September 15, 2008 The one line split-test, or how to A/B all the time Split-testing is a core lean startup discipline, and its one of those rare topics that comes up just as often in a technical context as in a business-oriented one when Im talking to startups. October 4, 2008 10:33 AM Amitt Mahajan said.
Lessons Learned by Eric Ries Thursday, July 2, 2009 How to conduct a Five Whys root cause analysis In the lean startup workshops , we’ve spent a lot of time discussing the technique of Five Whys. My intention is to describe a full working process, similar to what I’ve seen at IMVU and other lean startups.
Lessons Learned by Eric Ries Wednesday, February 11, 2009 The free software hiring advantage This is one of those startup tips Im a little reluctant to share, because its been such a powerful source of competitive advantage in the companies Ive worked with. Especially for a startup, not taking maximum advantage of free software is crazy.
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. Expo SF (May.
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. We're "lean" but we're not stirring hearts. Code Historian was my first product. We're effective but not playful.
When I want to know about some concurrency issues between services in his cluster, he doesnt blink an eye when I suggest we get the source code and take a look. Hes just as comfortable writing code as racking servers, debugging windows drivers, or devising new interview questions. He throws off volumes of code, and it works.
One of the sayings I hear from talented managers in productdevelopment is, “good enough never is.&# And, most importantly, it helps team members develop the courage to stand up for these values in stressful situations. Over time, such teams either explode due to irreconcilable differences or dramatically slow down.
I was the junior guy on a project team; I was called in to do some technical duediligence for reasons that were obscure to me, because the team already had much more senior engineers assigned to it. And like feedback on a simple microphone sound system, this would occasionally boil over into screeching.
Getting features and fixes into hands of users was the greatest priority - a test environment would just get in the way and slow down the validation coming from having code running in production. When a new engineer started at IMVU, I had a simple rule: they had to ship code to production on their first day.
The United States is now a debtor nation to China and that the bill is about to come due. Equity-Only CTO and Equity-Only Developers - SoCal CTO , November 1, 2010 I had a recent email dialog with the founder of a company looking for a CTO for their startup. These are probably the two sites where I've posted the most reviews.
Your natural tendency when an investor says yes will be to relax and go back to writing code. The Lean Startup Intensive is tomorrow at Web 2.0. Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev.
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. The same might be said of good software. Here we have the beginnings of a theory of design for software.
Take a failed product launch. At IMVU , these were quite common (after all, were shipping code 50 times a day). They are collected and reviewed after an appropriate interval (e.g. With due respect to the author’s obvious smarts, these ideas are too logical to be new. This policy doesnt leave much room for excuses.
To explain the difference, let’s take me as an example: I’m a software entrepreneur, and, in recent years, a member of an angel investment group. I get involved in detail when the group is looking at startups in software, web, mobile apps, or financial forecasting. It’s reviewed and revised frequently.
See Paul Grahams Why Nerds are Unpopular to learn more) Take a look at this article on a programming Q&A site: How old are you, and how old were you when you started coding? We also learned that law is code , and that leadership was needed to build thriving communities in a digital age. Can I send you a review copy?
Expo Intensive rocked, the mainstream media has started writing about the Lean Startup, and - most of all - the movement continues to grow and evolve. I went to the conference thinking that I was well grounded in the basics of the Lean Startup approach and that attendance would hone the edges of that understanding.
Due to an interaction effect between your hardware, solar flares, and quantum flux, this virus will crash your computer and erase your hard drive sometime soon. In the past, we invested in brilliant architecture, code reuse, refactoring, modular design, etc. I have detected a secret virus in your CPU. The curse of prevention Beware!
Since the term “cloud computing” was coined in 1996—at least as we have come to understand its meaning—the software as a service industry has exploded. Step 1: Start with a lean plan. I started UpKeep after seeing and using traditional enterprise software. Use your knowledge of an industry to solve a problem. “I
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 codereviews more seriously than any other company Ive even heard about. The Lean Startup Intensive is tomorrow at Web 2.0.
Instead of that naive approach, I wish Id had a book like this one, to help me figure out how to get started with customer development step-by-step. While the customer development framework of Four Steps is universally relevant, The Entrepreneur’s Guide updates its practices for modern startups.
We organize all of the trending information in your field so you don't have to. Join 5,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content