Startup Lessons Learned
MARCH 16, 2009
XP and Scrum don’t have much to say - they punt. If you look at the origins of most agile systems, including Scrum and XP , they come out of experiences in big companies. Both Scrum and XP had a role which you could happily call by the modern title "Product Manager". Embedded in that assumption is why startups fail.
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.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
SEPTEMBER 15, 2008
See Customer Development Engineering for my first stab at articulating the theory involved) Ferocious customer-centric rapid iteration, as exemplified by the Customer Development process. I would add -- think of your development and running your business like a PM/Developer uses Agile or Scrum in software development. No more, no less.
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. Lean Startup Wiki - including a complete list of local meetups and meetup organizers.
Startup Lessons Learned
SEPTEMBER 10, 2008
At IMVU , our engineering team accumulated thousands upon thousands of tests, and we had a build cluster (using BuildBot ) that ran them. There are several ways to make progress evident - the Scrum team model is my current favorite. At IMVU, our rule was that a new engineer needed to push code to production on their first day.
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. Bring your questions.
Startup Lessons Learned
APRIL 9, 2009
No engineering team. But where it makes sense, that team may also include engineers building new experiments or prototypes to try with customers. And instead of design, engineering, QA, and operations we have a solution team implementing a startup-centric version of agile development. You need a problem team and a solution team."
Expert insights. Personalized for you.
111 
Let's personalize your content