Startup Lessons Learned

AUGUST 8, 2009

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. We owe a lot to this seminal document. The same might be said of good software. But what about Commodity?

Software Review 87

Software Review Design Software San Francisco 87

Startup Lessons Learned

MAY 31, 2010

And a special thanks is due to all of our presenters, panelists, and mentors. Kent Beck is deservedly famous for his many contributions in the software industry. Unfortunately, the video of our sllconf conversation is not online (due to technical problems), but we have a physical tape backup which we are endeavoring to get online soon.

San Francisco 133

San Francisco Lean Technical Review Software Review 133

Startup Lessons Learned

JUNE 17, 2010

But according to the theory, this should have been covered by the various specs and documentation we were rigorous about producing. I was the junior guy on a project team; I was called in to do some technical due diligence for reasons that were obscure to me, because the team already had much more senior engineers assigned to it.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Up and Running

MAY 23, 2016

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. If you use software like LivePlan, you can create this initial “lean plan” in under an hour and then spend your time where it really matters—on validating your idea.

Software Review 74

Software Review Software Delaware Forecast 74

Startup Lessons Learned

FEBRUARY 22, 2009

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. only two kids took it up!

Programming 143

Programming San Francisco Lean Continuous Deployment 143

SoCal CTO

FEBRUARY 13, 2013

Once you build it, they will now ask you about the key metrics that they need proven in order to see if you really are a good investment. The real reason to build an MVP is to do early tests of key Startup Metrics for the business. " Once you have the metrics defined, it focuses your effort. Review the code being built.

Technical Cofounder 338

Technical Cofounder Technical Review CTO Hire Fractional CTO 338

ConversionXL

NOVEMBER 10, 2020

Metrics for this depth are rare and only long-term. We might have medium-term goals like “adopting agile methodologies” or “getting everyone on the same page with a project kick-off” as the outcomes for the reader. The metrics for this level are more concrete and objective.

Agile 139

Agile Social Media Audience Software Review 139

ConversionXL

AUGUST 4, 2020

You do CX a disservice if you focus only on metrics like NPS. Access to a team with skills that include scientific experimentation, UX, copywriting , consumer psychology , statistics , data analysis, coding, research methodologies, change management, and design. Fresh-eyes review. Can you share our company policy documents?

SQL 117

SQL Software Review Agile Metrics 117

Startup Lessons Learned

NOVEMBER 13, 2008

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.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Up and Running

DECEMBER 6, 2012

Here at Palo Alto Software in 2007 and 2008, we embraced these planning concepts and moved towards a more agile planning process. Instead of detailed documents, we focused on tracking our performance to our plan and managing to regularly updated schedules and milestones. Step 1: The Pitch. Step 3: Develop a Financial Model.

Lean 147

Lean Silicon Valley Forecast Technical Review 147

The Next Web

SEPTEMBER 8, 2013

At the end of last year, a document was published that described how Spotify works using a decentralized approach of tribes and squads. I also want to explain that it is possible to have a truly agile work environment based on small, autonomous teams. They develop a prototype that can be reviewed and most importantly, play tested.

Software Review 146

Software Review Agile Analytics SCRUM 146

crowdSPRING Blog

DECEMBER 13, 2018

You may already have your vision, mission, and values documented, but don’t worry if you don’t. Some companies chose to thoroughly document these and put them on an office wall or their website. You’re going to need some brand health metrics to track. 3) Develop personas for your target customers. Social media.

Marketing 162

Marketing Charlotte Naming Design 162

Startup Lessons Learned

MARCH 27, 2009

I believe it is a full, company-wide turn through the OODA loop (for a software business, see especially Ideas-Code-Learn ). In fact, every single lean transformation documented in books like Lean Thinking took place in the midst of serious external threats. What counts as an iteration? Were talking PayPal -sized variations.

San Francisco 117

San Francisco Lean Continuous Deployment DC 117

blog.expensify.com

APRIL 24, 2012

The right sort of person is so passionate about coding, they can’t be stopped from doing it. But every day spent in that kitchen is a day NOT spent in a real kitchen, learning how to cook real food, and write real code. I currently work in information security, and I help teach developers how to write better, more secure code.

Java 107

Java PHP Software Review Coder 107

Startup Lessons Learned

JANUARY 12, 2009

Since then, PHP (as part of the LAMP stack ) has really been the dominant development platform, at least in the free software and startup worlds. When we started IMVU in 2004, we could rely on a staggering amount of open source software that jumpstarted our initial product offering. Every change required a server restart.

PHP 166

PHP Software Review Ruby San Francisco 166

steveblank.com

JULY 8, 2011

signup, upgrade, trial pricing Zuora – online subscription management FeeFighters – find the cheapest credit card processors HealPay – Collections made easy Customer Support Tender – support, knowledgebase tool for your site GetSatisfaction - conversations between companies / customers.

Software Review 110

Software Review Startup Silicon Valley Analytics 110

www.vccafe.com

MARCH 11, 2013

VC Cafe highlights everything you need to know from hosting your code in hackathons to open source legal docs. For modifications, please edit the original document here. s the new way to code, and quite easy to learn. You can write back end code in javascript, one language conquers all! Code Igniter. Seed Startups.

Software Review 53

Software Review Technical Review Startup 53

Startup Lessons Learned

SEPTEMBER 11, 2009

In fact, I am convinced that if you could find some of IMVU’s earliest adopters, they would say something like this: “sure, those guys at IMVU HQ were helpful in writing code and stuff, but in the end they were just the hired help. peer review is NOT working. It was really the community who built that product.&#

Community 158

Community Management Lean Software Review 158