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.
ConversionXL
NOVEMBER 10, 2020
For example, the Jira Software team created a microsite dedicated to product-agnostic education about becoming an agile team. For example, Kanban and Scrum are two popular agile project management rituals. The Agile Coach includes a mix of long-form articles, vidoes, and tutorials.
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. 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.
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.
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!) When its receding, we rescope. Do you have a spec?
Startup Lessons Learned
APRIL 9, 2009
Best of all, Nivi from Venture Hacks was recording, so these slides have synchronized audio, too. This is true whether youre selling million-dollar software to huge enterprises or selling fifty-cent virtual clothes to teenagers. So without further ado, let me share the slides with audio. Here are some of my top takeaways.
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. Scrum reports would come in once a month, nobody was actually responsible for anything. My favorite instance of this is scheduling software.
Expert insights. Personalized for you.
111 
Let's personalize your content