Berkonomics

AUGUST 15, 2013

A good dashboard of relevant real time information is now available for most any business, often created by computer software from data derived from monitoring real time tasks within the business. Earliest warning metrics: What good is information if you can’t act upon it in a timely manner?

Japan 73

Japan Software Review Metrics Technical Review 73

Startup Lessons Learned

NOVEMBER 27, 2013

So if someone says, ‘You need comprehensive documentation for software documentation,’ I think, ‘Well, what if you didn’t have any documentation at all? So I get to see this hothouse of software design. And so I can see many more cycles through the loop of how software evolves, how innovation disperses in a community, and so on."

Lean 165

Lean San Francisco Cofounder Programming 165

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. Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev.

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

Hearpreneur

OCTOBER 29, 2017

Amazing chefs and experts who want to share their cultural and culinary traditions with curious people – even if they can’t hop on a flight and visit Japan this year or Italy next year. 10- Address financial and operating metrics. My service aims to transport kitchens and introduce you to people everywhere.

Entrepreneur 77

Entrepreneur Social Media Liquidity Event Private Equity 77

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. I used to think that investments in metrics were a form of waste. Customers dont care if you have good metrics, only if you have a good product.

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

Startup Lessons Learned

AUGUST 3, 2009

In a lot of cases, this requires a lot of energy invested in talking to customers or metrics and analytics. My experience is in Enterprise Software - where we are forced to chunk features into formal releases. Revisiting the Software Design Manifesto (and what. In fact, MVP is quite annoying, because it imposes extra overhead.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

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. Of course, many startups are capital efficient and generally frugal. No more, no less.

Lean 168

Lean San Francisco Startup 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. Startup Lessons Learned - the Conference (April 23.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

crowdSPRING Blog

JUNE 13, 2013

Excellent Analytics Tip #25: Decrapify Search, Social Compound Metrics | by Avinash Kaushik – [link]. Legal Contracts for Software Developers Who Hate Contracts (w/free contract template to use today) – [link]. New 311mph maglev train in Japan passes initial tests – [link]. Great products sell.

Social Media 95

Social Media Small Business Design Media 95

Hearpreneur

SEPTEMBER 15, 2021

Without these key metrics, employees will be free agents and looking for better work culture. These days, medical practitioners can meet through video communication on software built for this specific purpose. Like Singapore, China, Japan, and Korea, many industrialized countries have lower literacy rates than the United States.

Artificial Inteligence 110

Artificial Inteligence Entrepreneur Technical Review Security 110

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

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

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

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

YoungUpstarts

AUGUST 18, 2015

The company plans to expand into Japan, China, Portugal, and Spain by the end of the year – marking only the beginning of their international expansion strategy. The success of Netflix can be attributed to business intelligence principles and metrics. Netflix focuses on customer experience metrics.

Metadata 100

Metadata Portugal Metrics Spain 100

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 Lessons Learned

DECEMBER 28, 2009

Or, phrased more hopefully, "I see how you can use continuous deployment to run an online consumer service, but how can it be used for B2B software?" That continuous deployment leads to lower quality software than software built in large batches. Monitoring of real-world metrics. Or variations thereof.

Continuous Deployment 122

Continuous Deployment San Francisco Lean Metrics 122

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

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

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

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

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

AUGUST 26, 2009

Inspiring ideas: real-time biz metrics; safe continuous deployment; A/B split testing. More recently it's skewed to software & web. Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

Startup Lessons Learned

APRIL 9, 2009

dalelarson : "Metrics are people, too." leanstartup ericnsantos : #w2e #leanstartup Metrics should be Actionable, Accessible and Auditable. Metrics are a key questions startups face. Metrics are people too" is a reminder I constantly needed when I was a manager. ericries s talk on Lean Startups absolutely fantastic.

San Francisco 132

San Francisco Continuous Deployment Lean Agile 132

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

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

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

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

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

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

NOVEMBER 13, 2008

Because five whys kept turning up a few key metrics that were hard to set static thresholds for, we even had a dynamic prediction algorithm that would make forecasts based on past data, and fire alerts if the metric ever went out of its normal bounds. Best of luck, Your Software." (OK, OK, thats not exactly what it said.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

APRIL 14, 2009

Every board meeting, the metrics of success change. Time-to-complete-a-sale is not a bad metric for validated learning at this stage. So heres the question that I pose to you - our startup helps software companies develop a scalable revenue engine in the form of software-specific hardware devices.

Customer 167

Customer San Francisco Lean Hockey Stick 167

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