Startup Lessons Learned

MARCH 25, 2009

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. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Expo SF (May.

Agile 60

Agile Lean San Francisco Continuous Deployment 60

Startup Lessons Learned

JULY 5, 2010

I believe it is the best introduction to Customer Development you can buy. As all of you know, Steve Blank is the progenitor of Customer Development and author of The Four Steps to the Epiphany. I have personally sold many copies of his book, and continue to recommend it as one of the most important books a startup founder can read.

Customer Development 166

Customer Development Developer San Francisco Customer 166

Software By Rob

APRIL 7, 2010

We developed the plan and a task list, and estimated the effort at around 160 hours including development time needed to make DotNetInvoice a multi-tenant application. We developed the plan and a task list, and estimated the effort at around 160 hours including development time needed to make DotNetInvoice a multi-tenant application.

Agile 42

Agile Software Review Wiki Hosting 42

Steve Blank

MARCH 8, 2011

It was designed to bring together many of the new approaches to building a successful startup – customer development, agile development, business model generation and pivots. Even if they did, what if the assumption – that we had developed a better approach to teaching entrepreneurship – was simply mistaken?

Lean 298

Lean Business Model Customer Development Guinea 298

Startup Lessons Learned

SEPTEMBER 1, 2008

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. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Expo SF (May.

San Francisco 68

San Francisco Developer Continuous Deployment DC 68

YoungUpstarts

DECEMBER 5, 2012

By taking action every day, you develop the habits and discipline to make your vision a reality. We’re wired for agility. We’ve learned to bend technology to fit our needs and increase our agility for handling more complex situations at increasingly higher and faster levels. Women know how to collaborate.

Technical Review 268

Technical Review Agile Harvest Wiki 268

Startup Lessons Learned

APRIL 26, 2009

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 key lean startup concept.

Product Development 88

Product Development Developer San Francisco Product 88

Startup Lessons Learned

SEPTEMBER 15, 2008

But by taking advantage of open source, agile software, and iterative development, lean startups can operate with much less waste. I am heavily indebted to earlier theorists, and highly recommend the books Lean Thinking and Lean Software Development. Labels: customer development , lean startup 8comments: Amy said.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

The Startup Magazine

SEPTEMBER 28, 2020

Agile Scrum daily meetings have become a commonplace solution for development teams to hit and exceed targets. To this extent, Wiki comes bundled with MS Teams by default and allows team members to create and contribute to a dedicated workspace for notes. ScrumGenius.

Wiki 99

Wiki SCRUM Agile Analytics 99

Startup Lessons Learned

JANUARY 12, 2010

The Lean Startup Wiki (hosted by long-time lean startup pbWorks) contains a number of resources, including links to case studies , meetups, tools , and people who have volunteered to help. Its a wiki, feel free to consume and enhance it. Its a wiki, feel free to consume and enhance it. Expo SF (May. Want to learn more about me?

Lean 146

Lean San Francisco Wiki Startup 146

Startup Lessons Learned

SEPTEMBER 2, 2008

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. Expo SF (May.

San Francisco 94

San Francisco Continuous Deployment Agile DC 94

Startup Lessons Learned

SEPTEMBER 22, 2008

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. The goal of iterative development is to give us guard rails so we dont veer off to either extreme. you can be incredibly scientific.

Product Development 68

Product Development Developer San Francisco Product 68

Startup Lessons Learned

AUGUST 3, 2009

You refer to an anonymous Valley-based MMORPG that consumed years and tens of millions in development, but got little commercial traction. Refreshing to finally see lean and agile thinking emerge in product/business-floors and not only in technology. There was only one such company. August 13, 2009 3:43 AM Robert said. Thanks Eric.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Startup Lessons Learned

NOVEMBER 4, 2008

Boyd emphasized the importance of agility in combat: "the key to victory is to be able to create situations wherein one can make appropriate decisions more quickly than ones opponent." Agile software development. Agile allows companies to build higher quality software faster. Customer development. Excellent ideas!

Lean 102

Lean San Francisco Agile Continuous Deployment 102

steveblank.com

JULY 8, 2011

interactions, widgets, effects Django – high-level Python framework Cappuccino – open source framework for app development Kodingen – cloud development environment, code editor, hosting service, collaboration platform. WebSequenceDiagrams - sketch sequence diagrams.

Software Review 110

Software Review Startup Silicon Valley Analytics 110

Startup Lessons Learned

JUNE 2, 2010

As start-ups scale, this agility will be lost unless the founders maintain a consistent investment in that discipline. As start-ups scale, this agility will be lost unless the founders maintain a consistent investment in that discipline. The Entrepreneur’s Guide to Customer Development ▼ June (3) What is a startup?

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

Startup Lessons Learned

JANUARY 30, 2009

Without conscious process design, product development teams turn lines of code written into momentum in a certain direction. This is why agility is such a prized quality in product development. I myself didnt understand it until I had the opportunity to view that failure through the lens of the customer development theory.

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

Startup Lessons Learned

DECEMBER 16, 2009

For those whove heard it, it contains a length discourse on the subject of agile software development and extreme programming, including its weaknesses when applied to startups. As Im pontificating about agile, I see the name Kent Beck in my peripheral vision. Now, this webcast was packed, hundreds of people were logged in.

Lean 140

Lean San Francisco Continuous Deployment Startup 140

Startup Lessons Learned

OCTOBER 5, 2008

Lessons Learned by Eric Ries Sunday, October 5, 2008 The product managers lament Life is not easy when youre working in an old-fashioned waterfall development process, no matter what role you play. I met one recently that is working on a really innovative product, and the stories I heard from their development team made me want to cringe.

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

SEPTEMBER 10, 2008

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.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Steve Blank

DECEMBER 7, 2010

There are few courses which teach aspiring entrepreneurs the skills (business models, customer and agile development, design thinking, etc.) Therefore we developed a class to teach students how to think about all the parts of building a business, not just the product. Start your blog/wiki/journal. to optimize this search.

Wiki 311

Wiki Lean Management Business Model 311

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. Managing weekly releases got a lot harder once I started doing customer development.

Continuous Deployment 151

Continuous Deployment San Francisco Lean Wiki 151

Startup Lessons Learned

JUNE 22, 2009

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. IMVU had a roughly two-month-long development cycle. Heres what it looked like.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

Both Sides of the Table

NOVEMBER 1, 2009

He published our first wiki where the whole list of potential features were outlined. 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. He’s a smart guy.

Customer 280

Customer Technical Review Software Review Mexico 280

Startup Lessons Learned

NOVEMBER 7, 2008

Oops - there went several precious weeks of development effort down the drain. And if you dont know who your customer is, perhaps some customer development is in order? Labels: customer development , search engine marketing 13comments: Jim Lindstrom said. What is customer development? What a great post. Expo SF (May.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

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

FEBRUARY 10, 2009

Nobody gets here overnight, but every step along the way has made us better developers. They’ll increase code quality, prevent defects and educate your developers. You cant make these global efficiency improvements until you get clear about the goal of your development process. On commit automatically run all tests.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

Startup Lessons Learned

MARCH 25, 2010

This is the first post that moves into making specific process recommendations for product development. Labels: product development Speed up or slow down? This is the first post that moves into making specific process recommendations for product development. No departments The Five Whys for Startups (for Harvard Business R.

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

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. And this was a huge product, which took years to develop.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

JULY 30, 2009

I thought Id share a little bit of that, too: I’ve been interested in different approaches to software development going back to 1987 when – in my first company Feld Technologies – my partner Dave Jilk and I started talking about “semi-custom software development&# (way ahead of its time). Expo SF (May.

Lean 68

Lean San Francisco Continuous Deployment DC 68

Startup Lessons Learned

FEBRUARY 28, 2009

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. None of it would have happened if we had plenty of cash, or were content to count our progress by traffic or product development milestones.

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

Startup Lessons Learned

FEBRUARY 20, 2009

The batch size is the unit at which work-products move between stages in a development process. Take the example of a design team prepping mock-ups for their development team. And over time, the development team may be able to start anticipating your needs. For software, the easiest batch to see is code. I dont think so.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

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

SEPTEMBER 2, 2008

Its inspired by the classic OODA Loop and is really just a simplified version of that concept, applied specifically to creating a software product development team. Labels: agile , listening to customers 3comments: hauteroute said. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

AUGUST 2, 2008

The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? 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.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

Startup Lessons Learned

SEPTEMBER 22, 2008

The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? 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.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

Startup Lessons Learned

SEPTEMBER 10, 2008

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 software product development team. Joel said it: "Top notch development teams dont torture their programmers."

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144