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. The same might be said of good software. Here we have the beginnings of a theory of design for software.

Software Review 87

Software Review Design Software San Francisco 87

Steve Blank

FEBRUARY 3, 2016

Carmen was the first CIA executive to envision many of the applications now used by CIA analysts, including online production, collaborative tools, and Intellipedia , the Intelligence Community-wide wiki developed by Don Burke and Sean Dennehy. Upon her retirement from CIA, she received the Distinguished Career Intelligence Medal.

Wiki 120

Wiki Entrepreneur Cofounder Government 120

The Startup Magazine

SEPTEMBER 28, 2020

This app is best described as project management software to help organize and keep projects on track. 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. The app offers great flexibility but shines it how easily it integrates with MS Teams.

Wiki 100

Wiki SCRUM Agile Analytics 100

Both Sides of the Table

AUGUST 23, 2010

Only later did I realize that this was part of Dharmesh Shah’s larger blog and that the software was based on the popular “stack overflow&# software. I felt that the Stack Overflow software made it much more obvious what I was supposed to do when I arrived. It also feels very wiki like. articles and leaves.

Silicon Valley 301

Silicon Valley Pre-Money Valuation Technical Review Software Review 301

Feld Thoughts

JUNE 22, 2012

There seem to be two schools of thought on how to predict the future of information technology: looking at software or looking at hardware. This is what I mean by “forget about trying to predict advancements in software and just look at the hardware trend”. A documentation system such as a wiki is useless without any way to access it.

Artificial Inteligence 182

Artificial Inteligence Technical Review Bandwidth Software Review 182

Austin Startup

SEPTEMBER 18, 2017

They will manage the steps necessary to identify, select, and integrate your software and IT vendors, including third party product dependencies, email, network, wiki, intranet, project management, and telecommunications. They will review and negotiate all related contracts. Security needs to be top of mind for any CTO.

Fractional CTO 54

Fractional CTO CTO Hire CTO Technical Review 54

Startup Lessons Learned

JANUARY 18, 2010

This case presents a further complication: desktop software. Without being able transparently modify the software in situ, is it still possible to deploy on a continuous basis? If youre interested in contributing a case study for publication here, consider getting started by adding it to the Lean Startup Wiki case study section.

Continuous Deployment 151

Continuous Deployment San Francisco Lean Wiki 151

crowdSPRING Blog

JULY 2, 2018

The key here is flexibility: any document you create could have elements of lists, embedded media (including video, audio, and webpages), spreadsheets, wiki-style content, and other data all together in one place. The concept behind both apps is the documents we create aren’t just one type of thing.

Product 69

Product Web Wiki Design 69

ReadWriteStart

JANUARY 29, 2013

What makes Gliffy’s story especially interesting is that Microsoft invited the company to participate – even though Gliffy competes with Microsoft’s own Visio software. ‘We were thinking, is there any other software package that is larger, worldwide? monthly/$49.50 monthly/$99.50 pro tier is also available.

Wiki 60

Wiki Software Software Engineering Algorithm 60

Startup Lessons Learned

APRIL 4, 2010

Kent is a significant figure in the field of software development. Kent is a significant figure in the field of software development. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Our mystery keynote is now revealed and I couldnt be more excited. April 23, 2010 in San Francisco.

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

crowdSPRING Blog

JULY 2, 2018

The key here is flexibility: any document you create could have elements of lists, embedded media (including video, audio, and webpages), spreadsheets, wiki-style content, and other data all together in one place. The concept behind both apps is the documents we create aren’t just one type of thing.

Product 48

Product Web Wiki Design 48

Steve Blank

DECEMBER 7, 2010

Their company can focus in any area– software, hardware, medical device or a service of any kind. Start your blog/wiki/journal. Update your blog/wiki/journal. Update your blog/wiki/journal. Update your blog/wiki/journal. Everyone: Update your blog/wiki/journal. How’s the Class Organized?

Wiki 311

Wiki Lean Management Business Model 311

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 their are independent software companies now focused on this like UserVoice and Get Satisfaction. What changed for us was Tim Barker arrived. He made customer-to-customer dialog possible and visible. cared about the feature set.

Customer 280

Customer Technical Review Software Review Mexico 280

dontbesoanalytical.blogspot.com

MAY 13, 2012

Consider how firms today confront Web 2.0 – the combination of blogs, wikis, and social networking technologies sprouting up. Of course, this draconian measure does not work; employees can blog under another name, or contribute to a wiki pseudonymously. On the Use, and Misuse, of Software Test Metrics. software quality. (1).

CTO 40

CTO Technical Review Technology Software Review 40

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. Lean Startup Wiki - including a complete list of local meetups and meetup organizers.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

Startup Lessons Learned

JUNE 15, 2009

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. All customers will see the new software as soon as it’s deployed.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

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. April 23, 2010 in San Francisco. Bring your questions.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Both Sides of the Table

APRIL 15, 2013

This is my third post in a series on Enterprise Software. In part one I covered the need for early-stage enterprise software companies to build up professional services staff to ensure successful implementation projects. For starters as a young enterprise software company you need to think about the customer segments you serve.

Egypt 297

Egypt Early Stage Mexico Wiki 297

Startup Lessons Learned

FEBRUARY 20, 2009

Lessons Learned by Eric Ries Friday, February 20, 2009 Work in small batches Software should be designed, written, and deployed in small batches. For software, the easiest batch to see is code. When something goes wrong with production software, its almost always because of an unintended side-effect of some piece of code.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

NOVEMBER 6, 2008

Steveys Blog Rants: Good Agile, Bad Agile : "Google is an exceptionally disciplined company, from a software-engineering perspective. But its helpful to take a detailed look inside the highly agile process used by Google to ship software. Lean Startup Wiki - including a complete list of local meetups and meetup organizers.

Agile 76

Agile San Francisco Software Review Continuous Deployment 76

Software By Rob

SEPTEMBER 29, 2009

September 29th, 2009 | Software Development Building your startup? I cover topics that affect software and web startups of all sizes, but mostly relating to startups you can fund yourself. Matt - 3 years as a consultant for software tools (JIRA, svn, Conference, wikis, SCons etc) #5 Balaji_Getfriday on 09.30.09

Software Review 53

Software Review Developer RSS Software Developers 53

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. I know many people who think that software works like magic, but to me it actually was magic. hey eric, love the blog.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

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). Read the rest.

Lean 68

Lean San Francisco Continuous Deployment DC 68

Andrew Payne

MAY 29, 2009

We each have shared calendars, one calendar for each of the kids, and a “guest/vacation/family activity calendar” Private wiki (access controlled). The key here is a good scanner and simple software to scan and file. Plus, it’s a great way to stay in touch with your kids, since it’s a mode they prefer.

Management 40

Management Technical Review Wiki Software Review 40

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

Startup Lessons Learned

FEBRUARY 9, 2009

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. a guide for hackers) You buy virtual goods The free software hiring advantage Continuous deployment and continuous learning The lean startup @ Web 2.0

Lean 68

Lean San Francisco Web Advisory Board 68

bizthoughts.mikelee.org

MARCH 8, 2012

Active software engineers probably get two offers a month or more. I was able to hire phenomenal software engineers and grow a strong team culture. If you’re a non-technical entrepreneur in Silicon Valley that’s out of college now, it can be tough to find a technical cofounder. I was lucky enough to have worked for Yahoo!

Technical Cofounder 40

Technical Cofounder Cofounder Technical Review Software Review 40

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." How long does the software sit un-deployed? Software is generally always getting better or getting worse. You can tell a lot about a company from their deployment flow.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

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. Please leave feedback!) They just dont happen. April 23, 2010 in San Francisco.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

JANUARY 2, 2009

My son is planning a software product that will take the mystery out of wikis and make the technology easier for consumers to use. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Funnel averages over time. You can read the article to find out why. 3comments: Charles Crawford said.

San Francisco 60

San Francisco Tampa Continuous Deployment Lean 60

Startup Lessons Learned

OCTOBER 20, 2008

They just assumed it was the way software companies worked. Unfortunately, threats work a lot better at incentivizing people to CYA than getting them to write quality software. When I first encountered agile software techniques, in the form of extreme programming , I thought I had found the answer. Sound good? It didnt work.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

NOVEMBER 4, 2008

It is becoming easier and cheaper for companies to bring products to market, leveraging free and open source software , cloud computing, open social data (Facebook, OpenSocial ), and open distribution (AdWords, SEO). Agile software development. Agile allows companies to build higher quality software faster. Bring your questions.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

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. Were a software company, so what we do everyday is turn ideas into code. Lean Startup Wiki - including a complete list of local meetups and meetup organizers.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

MARCH 16, 2009

In most agile development systems, there is a notion of the "product backlog" a prioritized list of what software is most valuable to be developed next. The breakthrough idea of agile is that software should be built iteratively, with the pieces that customers value most created first. Hes often felt that there was something missing.

Agile 111

Agile Customer Development Developer San Francisco 111

Startup Lessons Learned

MAY 31, 2010

Kent Beck is deservedly famous for his many contributions in the software industry. Kent Beck is deservedly famous for his many contributions in the software industry. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Do you know the difference between Durant and Sloan ? Bring your questions.

San Francisco 133

San Francisco Lean Technical Review Software Review 133

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. In almost all Agile Development systems, thousands of automated tests are run against every change to the software.

San Francisco 68

San Francisco Developer Continuous Deployment DC 68

TechEmpower

MAY 28, 2020

You can read more about composite scores at the GitHub wiki. This is an exploration of a new use-case for this project that is unrelated to the original goal of improving software performance. You can read more about TPR at the GitHub wiki. TechEmpower Performance Rating (TPR). We look forward to your feedback on this feature.

Framework 624

Framework Azure Wiki Database 624