Startup Lessons Learned

APRIL 4, 2010

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. Kent is a significant figure in the field of software development.

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

Startup Lessons Learned

MARCH 16, 2009

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. But startups sometimes have trouble applying agile successfully. Thats pretty clear.

Agile 111

Agile Customer Development Developer San Francisco 111

ctotodevelopers.blogspot.com

JULY 11, 2012

Social, Agile, and Transformation. I cover several topics including agile software development, software startups, web 2.0, Strategic Agile Thinking: Balancing Value, Innovation and Research. 2) The agile "happy place". Agile teams sprint when value is known, implementation is low risk.

Agile 40

Agile Architecture Offshore Software Developers 40

Steve Blank

MAY 6, 2015

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. Waterfall Development was all about execution of the requirements document. Here’s how. Microsoft Windows 3.0).

Lean 120

Lean Agile Business Model Customer Development 120

View from Seed

NOVEMBER 6, 2014

Isaac Cambron is co-founder and CTO of Zensight.co , whose pre-launch product enables sales reps to find and use their best content to close more deals. Below, he answers questions about developing products from scratch, as well as the difficult technology choices and tradeoffs CTOs must make. We did that for a lot of reasons.

Technology 334

Technology Ruby Startup Engineer 334

Steve Blank

AUGUST 31, 2009

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. So what’s wrong the product development model?

Customer Development 243

Customer Development Developer Customer Silicon Valley 243

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. This workshop brings together leading thinkers from Lean Production and Lean software.

Agile 60

Agile Lean San Francisco Continuous Deployment 60

Startup Lessons Learned

APRIL 25, 2011

It may be hard to remember that there was a time when people in the agile software development community thought Lean Startup was incompatible with agile practices. Former Adaptive Path CEO Janice Fraser will present a series of case studies on how to use Lean Startup to design amazing products.

San Francisco 146

San Francisco Silicon Valley Lean Agile 146

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

Startup Lessons Learned

NOVEMBER 12, 2013

On November 14 (that’s this Thursday) at 1p PT, Eric Ries will speak with Kent Beck, a creator of Agile software development, about facilitating the work of engineers and product teams. This Thursday’s webcast will get to the heart of how product groups work—and how they can work better.

Product Development 167

Product Development Software Review Technical Review Developer 167

Startup Lessons Learned

SEPTEMBER 7, 2008

In addition to presenting the IMVU case, we tried for the first time to do an overview of a software engineering methodology that integrates practices from agile software development with Steves method of Customer Development. Can this methodology be used for startups that are not exclusively about software?

Customer Development 131

Customer Development Engineer San Francisco Developer 131

crowdSPRING Blog

MAY 11, 2012

Better Agile Than Smart – [link]. Six Myths of Product Development – [link]. Unlimited Vacation Doesn’t Create Slackers–It Ensures Productivity – [link]. Unlimited Vacation Doesn’t Create Slackers–It Ensures Productivity – [link]. So what exactly is a tech company?

Social Media 92

Social Media Small Business Design Media 92

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 Lean 94

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).

Lean 68

Lean San Francisco Continuous Deployment DC 68

ConversionXL

JUNE 13, 2017

Agile marketing may not be a phrase you hear often, but it’s becoming increasingly popular and important. Traditionally associated with development and product management, agile is a lightweight and, well, agile framework for software development and bringing features and products to market.

SCRUM 112

SCRUM Agile Marketing Development Team Review 112

Up and Running

SEPTEMBER 28, 2015

Kanban: a method used to control production. The word kanban means “signboard” or “billboard” in Japanese, and it’s a concept most commonly applied to “lean” or “just in time” production. Kanban is a scheduling system for “just in time” production. Scrum: a flexible way to manage product development.

SCRUM 60

SCRUM Japan China Agile 60

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.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

FEBRUARY 9, 2009

The Lean Startup: a Disciplined Approach to Imagining, Designing, and Building New Products.: It uses principles of agile software development, open source and web 2.0, Hey Someone else who is extending the agile/lean approach beyond just developing software. I am extending it to all start-ups.

Lean 68

Lean San Francisco Web Advisory Board 68

Startup Lessons Learned

SEPTEMBER 2, 2008

Lessons Learned by Eric Ries Tuesday, September 2, 2008 On deployment My favorite question to ask a software development team is "how do you do a release." Thoughts on scientific product development Lo, my 5 subscribers, who are you? You can tell a lot about a company from their deployment flow. How fast do they iterate?

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

OCTOBER 4, 2008

Although Catalyst folded with the dot-com crash, Ries continued his entrepreneurial career as a Senior Software Engineer at There.com, leading efforts in agile software development and user-generated content. While an undergraduate at Yale Unviersity, he co-founded Catalyst Recruiting. hey eric, love the blog.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

MAY 27, 2009

It uses principles of agile software development, open source and web 2.0, Sorry about this being out of context but I wonder if youve read "What Customers Want: Using Outcome-Driven Innovation to Create Breakthrough Products and Services". Labels: events 3comments: Alexandre Gomes said. Expo SF (May.

Lean 60

Lean Austin San Francisco Continuous Deployment 60

Startup Lessons Learned

JUNE 15, 2009

This condition makes it much easier for teams to innovate, experiment, and achieve sustained productivity. One large source of waste in development is “double-checking.&# One is used by engineers to refer to the process of getting code fully integrated into production. Continuous deployment also acts as a speed regulator.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

femgineer.com

JULY 18, 2010

If you’re a founder who is still trying to grasp the product roadmap and create a company vision its probably not a good time to hire an engineer. We engineers know that need to be agile in a startup and be able to scrap code and rebuild, but want we don’t want is to have a founder who manic or aimless.

Engineer 41

Engineer Software Review Startup Technical Review 41

Startup Lessons Learned

OCTOBER 16, 2013

One good example is the way in which we''ve adjusted the length of different phases of our agile sprints. We don''t follow a set agile methodology, but rather follow a more home-grown, minimal version of various approaches. It wasn’t always this way. So what was going on? But that doesn’t mean that we don’t take these ideas seriously.

Lean 167

Lean Startup Software Engineering Agile 167

Startup Lessons Learned

SEPTEMBER 27, 2010

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. This is precisely the dilemma that the doctrine of minimum viable product is designed to solve.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

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. There is a dark side to naming.

Lean 140

Lean San Francisco Continuous Deployment Startup 140

Startup Lessons Learned

FEBRUARY 10, 2009

This also literally can’t catch every problem, because your test sandboxes or test clusters will never be exactly like the production system. But I will tell you not to have too little or too much, because those definitely ruin the food or product. Heck, thats what it says right there in the agile manifesto. But it worked.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

Steve Blank

NOVEMBER 2, 2009

For those of you who have been following the discussion, a Lean Startup is Eric Ries ’s description of the intersection of Customer Development , Agile Development and if available, open platforms and open source. Where is the budget for purchasing the type of product you’re selling? Something else? Who’s the customer?

Lean 259

Lean Silicon Valley Startup RSS 259

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. Customers dont care if you have good metrics, only if you have a good product. I think it was $350 the next, and so on.

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

A Smart Bear: Startups and Marketing for Geeks

JULY 19, 2010

During a lull in her practice she got a serendipitous opportunity to shift gears completely and ended up leading software product development teams. But now she has the vision and ability to design her own software, capitalizing on modern trends (e.g. At best, they could copy. Our advantage was speed.

Software Review 325

Software Review Technical Review Development Team Review Bolivia 325

Startup Lessons Learned

AUGUST 1, 2009

He doesnt put out crappy, buggy products and then ask for feedback. My normal answer is that I dont really think thats how Apple products are built. Thats what so many techniques that I advocate are all about: customer validation , minimum viable product , vision pivots , and even throwing away working code. It just wasnt great.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

DECEMBER 7, 2008

In a few cases, they are clearly smart people in a bad situation, and Ive written about their pain in The product managers lament and The engineering managers lament. The "just fix it" mentality is counter-productive here. At the end of the day, the product development team of a startup (large or small) is a service organization.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

JULY 2, 2009

Five Why’s rarely works for general abstract problems like “our product is buggy&# or “our team moves too slow.&# The net effect of all this was to make new engineers incredibly productive right away – in most cases, we’d have them deliver code to production on their very first day.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

bhargreaves.com

MARCH 7, 2010

Many capable founders aren’t developers, and I frequently meet with entrepreneurs that have taken a very different path. Most disturbingly, I’ve occasionally found myself agreeing with an entrepreneur’s decision to hire a development shop to build their product. Sometimes, it just makes sense.

Hiring 40

Hiring Technical Review Agile Software Review 40

Startup Lessons Learned

DECEMBER 6, 2008

Lessons Learned by Eric Ries Saturday, December 6, 2008 The four kinds of work, and how to get them done: part three Those startups that manage to build a product people want have to deal with the consequences of that success. Lets start with the most important thing you can do to help product teams succeed: make them cross-functional.

San Francisco 74

San Francisco SCRUM Lean Continuous Deployment 74

Startup Lessons Learned

FEBRUARY 22, 2010

Even if men have an innate advantage at software development, the gap would have to be massive in order to explain why startup after startup has an all-male team. The work product is a more realistic test, although it requires much more work on the part of the candidate. Demographic diversity is an indicator.

San Francisco 167

San Francisco Lean Sweden Continuous Deployment 167

A Smart Bear: Startups and Marketing for Geeks

FEBRUARY 7, 2011

With all these new tasks, there’s no way you can also manage the projects and client relationships and internal product development, so you’ll need a project manager or a sales person or an office manager or some kind of help, and all of those come out of your profits. Build a product. Lack of focus kills.

America 330

America Employee Hiring HTML 330