Transformify

MARCH 14, 2020

Even though Korea and Finland have been on the top of the list of the most educated nations, the school systems in these countries vary a lot and it is almost impossible to compare them with each other. The same is valid for people who have graduated from a variety of universities and schools.

Hiring 98

Hiring Bulgaria Italy Spain 98

Startup Lessons Learned

AUGUST 3, 2009

My experience is in Enterprise Software - where we are forced to chunk features into formal releases. Revisiting the Software Design Manifesto (and what. Robert August 25, 2009 5:25 AM Bernard said. Great Post - could not agree more. Take a look and let me know what you think.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

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. Take a look and let me know what you think.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

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

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

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

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. I think you can safely ignore the rantings about "bad agile" and the bad people who promote it.

Agile 76

Agile San Francisco Software Review Continuous Deployment 76

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

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

Both Sides of the Table

SEPTEMBER 27, 2012

From startup Rovio in Finland. Ability To Attract a Pool of Engineers – We know that SF is Mecca for software engineers. It came from an amazing small startup in McKinney, Texas (30 miles North of Dallas) called NewToy , which they acquired. Think the next big startup can’t come from Dallas, TX? Think again. Angry Birds?

Community 378

Community San Diego Silicon Valley Los Angeles 378

Startup Lessons Learned

FEBRUARY 10, 2009

That leads to a seemingly-obvious question: what is progress in software development? Did it ever occur to any of you how many man hours are wasted on writing software that gets thrown out because you didnt simply ask the user if they would even like that feature? Heck, thats what it says right there in the agile manifesto.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

Startup Professionals Musings

APRIL 10, 2011

I was once asked by a top executive of a major software company why we were not selling more products in Finland. I informed him that we needed to translate the software into Finnish at a cost of $50,000. Here are a few examples from my personal experience: You need to translate/localize your products. Local laws prevail.

Saudi Arabia 225

Saudi Arabia Brazil Finland Silicon Valley 225

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

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

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

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

Steve Blank

SEPTEMBER 15, 2011

They also set up ethnic-centric networks like TIE (The Indus Entrepreneur) and the Chinese Software Professionals Association where they shared information about how the valley worked as well as job and investment opportunities. Looking for a chance to run their own show, many of them left and founded startups. What Are You Waiting For?

Silicon Valley 335

Silicon Valley Finland IP Cofounder 335

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

crowdSPRING Blog

JULY 7, 2010

Legal Contracts for Software Developers Who Hate Contracts (w/free contract template to use today) – [link]. Today Finland officially becomes first nation to make broadband a legal right – [link]. Inspiration: Asian Style Tattoos – [link]. 65 Unique And Innovative Website Footer Designs For Inspiration – [link].

Social Media 96

Social Media Small Business Design Media 96

crowdSPRING Blog

JULY 7, 2010

Legal Contracts for Software Developers Who Hate Contracts (w/free contract template to use today) – [link]. Today Finland officially becomes first nation to make broadband a legal right – [link]. Inspiration: Asian Style Tattoos – [link]. 65 Unique And Innovative Website Footer Designs For Inspiration – [link].

Social Media 96

Social Media Small Business Design Media 96

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. There are three stages: We start with ideas about what our product could be.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

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.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

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.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

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. Do you know the difference between Durant and Sloan ? If not, youd better watch video of his talk ASAP. And then you can buy a t-shirt. And then you can buy a t-shirt.

San Francisco 133

San Francisco Lean Technical Review Software Review 133

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

DECEMBER 8, 2008

In many traditional software organizations, branches can be extremely long-lived, and integrations can take weeks or months. Heres how Fowler describes it: I vividly remember one of my first sightings of a large software project. I would like the users of my software to test and give their feedback to me. Rate me on some scale.

Software Review 136

Software Review San Francisco Lean Continuous Deployment 136

YoungUpstarts

AUGUST 3, 2018

Lamia (Finland). Silk Software Corp. MindArc Pty Ltd (Australia). Madia BV (Netherlands). Webgriffe SRL (Italy). Divante Sp. HiberusTecnologia (Spain). One Creations (UK). Blue Acorn, LLC (USA). eWave (Australia). netz98 GmbH (Germany). Netherlands). Selection Tips. .

Netherlands 100

Netherlands Belarus Poland Indonesia 100

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? Continuous Deployment is a process by which software is released several times throughout the day – in minutes versus days, weeks, or months.

Continuous Deployment 151

Continuous Deployment San Francisco Lean Wiki 151

Startup Lessons Learned

JULY 5, 2010

Four Steps primarily centers its stories and case studies on B2B hardware and software startups. Four Steps primarily centers its stories and case studies on B2B hardware and software startups. This new volume also tackles examples from the Internet and wireless startups of today, both B2B and B2C.

Customer Development 166

Customer Development Developer San Francisco Customer 166

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. Please register to attend this event as space will be limited.

Agile 60

Agile Lean San Francisco Continuous Deployment 60

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

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

AUGUST 26, 2009

More recently it's skewed to software & web. Revisiting the Software Design Manifesto (and what. I remember thinking then how much better it was than Chicago, where I'd spent the previous 8 years. Technically you argue it goes back 30 years when StorageTek was founded. There used to be a ton of storage startups here.

San Francisco 113

San Francisco Silicon Valley Startup Continuous Deployment 113

Startup Lessons Learned

SEPTEMBER 30, 2008

It became harder and harder to separate how the software is built from how the software is structured. If not, whos going to insist we switch to free and open source software? But along the way, something strange happened. How can it work if some folks are pre-building and others use five whys to drive decisions?

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

ConversionXL

AUGUST 23, 2017

Finland-based Leadfeeder is a top (Google) analytics tool that shows the companies that visit your website. Let’s get inspired by these companies’ successful customer journey map examples. While some weren’t able to share the entire process due to privacy issues, they did share a specific section in the process… 1. Leadfeeder.

Customer 130

Customer Channel Design Retention 130

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

OCTOBER 5, 2008

So the product manager winds up actually having to use the software, by hand, updating the spec and helping create a new test plan. The fourth spec exists only in these emails, which are changing the design in an ad-hoc fashion. By the time QA gets the feature, their test plan is badly out of date. Take a look and let me know what you think.

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

MAY 27, 2009

It uses principles of agile software development, open source and web 2.0, Ship new software at a dizzying pace: multiple times a day while improving quality and lowering costs. and lean manufacturing to guide the creation of technology businesses that create disruptive innovation. Take a look and let me know what you think.

Lean 60

Lean Austin San Francisco Continuous Deployment 60