Startup Lessons Learned

NOVEMBER 18, 2008

Its even more critical in lean startups when they need to manage growth. At IMVU , we called this person a Producer (revealing our games background); in Scrum , they are called the Product Owner. Once an agreement is reached, the Chief Engineer continually watches to make sure that the functions are following through.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

SVPG

MARCH 10, 2016

For many years, as teams move to Agile methods (they usually start with Scrum), many companies decide to contract with or hire an Agile Coach. They understand the engineering and release side of things, but not the discovery side of things. Discovery Coaches are not unlike Lean Startup Coaches.

Agile 60

Agile SCRUM Lean Engineer 60

Startup Lessons Learned

APRIL 9, 2009

Thats the essence of so many of the lean startup techniques Ive evangelized: customer development , the Ideas/Code/Data feedback loop , and the adaptation of agile development to the startup experience. No engineering team. The lean startup focuses on situations where we have both an unknown problem and an unknown solution.

San Francisco 132

San Francisco Continuous Deployment Lean Agile 132

SVPG

JUNE 5, 2015

” These might be user stories or they might be more like some form of a functional spec but it’s purpose is to communicate with the designers and engineers what needs to be built. Finally the requirements and design specs make it to engineers. This is usually where Agile finally enters the picture.

Product 60

Product Agile Engineer SCRUM 60

Startup Lessons Learned

MAY 25, 2020

And I think how you think about that, whether you're a restaurant owner that didn't invest in curbside pickup, what can you do to, I'll call it, hack it or in an agile mindset, how do you think about bringing a way to be able to do curbside and do that well, and not just rely on the delivery folks to be able to support you? Let's go."

Technical Review 148

Technical Review Balance Sheet Texas Austin 148

Startup Lessons Learned

DECEMBER 6, 2008

The advantages of cross-functional teams are well documented, and for a thorough treatment I recommend the theory in the second half of Agile Software Development with Scrum. Scrum recommends 30 days; I have worked in one or two-week cycles up to about three months. The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 74

San Francisco SCRUM Lean Continuous Deployment 74

Startup Lessons Learned

SEPTEMBER 22, 2008

Heres something I can relate to: We used assembla for subversion, scrums, milestones, wikis, and for general organizational purposes. We had all the tools in place but we didn’t actually practice agile development. Scrum reports would come in once a month, nobody was actually responsible for anything.

San Francisco 68

San Francisco SCRUM Lean Continuous Deployment 68

steveblank.com

JULY 8, 2011

Github - Free public repositories, collaborator management, issue tracking, wikis, downloads, code review, graphs Pivotal Tracker – Agile project management tool that enables real time collaboration. WebSequenceDiagrams - sketch sequence diagrams.

Software Review 110

Software Review Startup Silicon Valley Analytics 110

www.vccafe.com

MARCH 11, 2013

Lean Methodology Sources. Steve Blank on Lean Customer Development. Part 3- Lean Cust. Firebase : Are all your developers front-end engineers? Google Custom Search Engine. Google App Engine. Steve Blank’s Lean Startup Resources. Lean Startup Circle â?? Search Engine Optimization Tools.

Software Review 53

Software Review Technical Review Startup 53