Startup Lessons Learned

SEPTEMBER 2, 2008

After all, the worst kind of waste in software development is code to support a use case that never materializes. Chris and I had the opportunity to present on our approach this past spring at the MySQL Conference. Chris and I had the opportunity to present on our approach this past spring at the MySQL Conference.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

FEBRUARY 10, 2009

Lessons Learned by Eric Ries Tuesday, February 10, 2009 Continuous deployment and continuous learning At long last, some of the actual implementers of the advanced systems we built at IMVU for rapid deployment and rapid response are starting to write about it. At IMVU it’s a core part of our culture to ship.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

Startup Lessons Learned

FEBRUARY 9, 2009

Expo San Francisco 2009 The current macroeconomic climate presents unparalleled opportunities for those that can thrive with constrained resources. It uses principles of agile software development, open source and web 2.0, The trade-off, though, is a more structured presentation format. Expo (and a call for he.

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." You can tell a lot about a company from their deployment flow. After an hour with a team talking dirty about deployment, youll know. 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. Case Study: Continuous deployment makes releases n. Thanks and thanks again.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

MARCH 25, 2009

Agile Vancouver : Lean Development for Lean Times On Tuesday April 21st, we are hosting an afternoon event on the application of Lean Principles to software development. This workshop brings together leading thinkers from Lean Production and Lean software. Case Study: Continuous deployment makes releases n.

Agile 60

Agile Lean San Francisco Continuous Deployment 60

Startup Lessons Learned

MARCH 16, 2009

What causes projects like this to fail in traditional software development is that the solution is unknown. Eric Ries Lean Startup Schematic View Of Agile Development And Customer Development View more presentations from Eric Ries. Labels: customer development , product development 8comments: Sarah Milstein said.

Agile 111

Agile Customer Development Developer San Francisco 111

Startup Lessons Learned

MAY 27, 2009

Heres their description of the event: The current macroeconomic climate presents unparalleled opportunities for those that can thrive with constrained resources. It uses principles of agile software development, open source and web 2.0, It uses principles of agile software development, open source and web 2.0,

Lean 60

Lean Austin San Francisco Continuous Deployment 60

Startup Lessons Learned

OCTOBER 16, 2013

We work in prototypically four-week iterations, with quality engineers and software developers working in close collaboration. This finally bit us after a four month stint of development blew through its testing schedule by a factor of four: two scheduled weeks turned into two months before the product reached stability.

Lean 167

Lean Startup Software Engineering Agile 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. I had a background in lean manufacturing (book knowledge, anyway) and lean software development (hands on) before encountering Lean Startups.

Lean 140

Lean San Francisco Continuous Deployment Startup 140

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. Case Study: Continuous deployment makes releases n. I used to think that investments in metrics were a form of waste.

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

Startup Lessons Learned

JULY 2, 2009

Furthermore, I think most of what you are suggesting is applicable in companies/ industries that are not software development. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

SEPTEMBER 27, 2010

Lean manufacturing , agile software development , and Theory of Constraints are all examples of this idea in action. Lean manufacturing , agile software development , and Theory of Constraints are all examples of this idea in action. Case Study: Continuous deployment makes releases n.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

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. Im not much of a statistician, so I am indebted to @hypatiadotca who shared this excellent and brief presentation by Terri Oda. Demographic diversity is an indicator.

San Francisco 167

San Francisco Lean Sweden Continuous Deployment 167

Startup Lessons Learned

AUGUST 1, 2009

We might be a ways away from the reality of a Chief Engineer or Product Director role commonly in software development, but ultimately it's going to be a matter of getting the culture right so that people stick around long enough to develop not only the tactical skills, but also the honed instincts and senses.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

DECEMBER 7, 2008

Our CTO is the CEO himself, but he lacks the understanding of the new software development processes and the new technologies. In school I was being pounded day and night with anything that has to do with agile software development. Case Study: Continuous deployment makes releases n.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

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. Case Study: Continuous deployment makes releases n.

San Francisco 74

San Francisco SCRUM Lean Continuous Deployment 74

Startup Lessons Learned

JANUARY 28, 2009

Its an essential discipline of good software development, especially in startups. In the same way that product managers must be ruthless about product prioritization, developers should be ruthless about choosing which bits of code are really worth polishing right now. Case Study: Continuous deployment makes releases n.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79