Agile Founder Metrics SCRUM 
Startup Lessons Learned
MARCH 16, 2009
Lessons Learned by Eric Ries Monday, March 16, 2009 Combining agile development with customer development Today I read an excellent blog post that I just had to share. Jim Murphy is a long-time agile practitioner in startups. But startups sometimes have trouble applying agile successfully.
YoungUpstarts
MAY 30, 2019
Upon arrival, I incorporated a few elements from my previous stop into this new endeavor, including a battle-tested Agile Scrum process and the corresponding technology. Development teams must build a muscle for reliable estimation and delivery, whether through Scrum velocity metrics or their own approach.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
The Next Web
SEPTEMBER 8, 2013
I also want to explain that it is possible to have a truly agile work environment based on small, autonomous teams. It’s completely up to them if they want to listen or ignore outside advice – even if it’s from one of the founders. Being agile. All KPIs and metrics are available to everyone in the company.
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. So far, I have found "lean startup" works better with the entrepreneurs Ive talked to than "agile startup" or even "extreme startup.") Of course, many startups are capital efficient and generally frugal.
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. Creating a company-wide feedback loop that incorporates both customer development and agile development is a challenge.
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. At IMVU, we found 60 days was just about right. Expo SF (May.
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. Lighthouse – Issue Tracking Tool.
Expert insights. Personalized for you.
111 
Let's personalize your content