2010 Agile Design 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.
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.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
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.") April 6, 2010 8:23 AM Colie Brice said. No more, no less.
Startup Lessons Learned
OCTOBER 5, 2008
These specs are handed to a designer, who builds layouts and mockups of all the salient points. Then the designs are handed to a team of programmers with various specialties. The programmers keep asking for more say in the designs and direction that they work on. First, he writes it nice and clear.
Startup Lessons Learned
SEPTEMBER 10, 2008
I know plenty of people who prefer more advanced source control system, but my belief is that many agile practices diminish the importance of advanced features like branching. Its not that the idea behind them is wrong, but I think agile team-building practices make scheduling per se much less important. Youd better.
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
To begin with, see if you can get designers, programmers, and QA on the same team together. 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. At IMVU, we found 60 days was just about right. Expo SF (May.
Expert insights. Personalized for you.
111 
Let's personalize your content