Remove Engineer Remove Hiring Remove SCRUM Remove Wiki
article thumbnail

Lessons Learned: Combining agile development with customer development

Startup Lessons Learned

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.

Agile 111
article thumbnail

Startup Tools

steveblank.com

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.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Lessons Learned: The lean startup

Startup Lessons Learned

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.

Lean 168
article thumbnail

The four kinds of work, and how to get them done: part three

Startup Lessons Learned

For starters, theres whole volumes that need to be written about how to actually find and hire the people your startup needs. But most startups succeed in hiring, one way or another, and are still left with the problems of organizing the people that rapid growth brings in. At IMVU, we found 60 days was just about right.

article thumbnail

Lessons Learned: A new version of the Joel Test (draft)

Startup Lessons Learned

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.

article thumbnail

You don't need as many tools as you think

Startup Lessons Learned

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.

article thumbnail

Lessons Learned: The product manager's lament

Startup Lessons Learned

The VP Engineering spends all of his time trying to make sure the programmers understand and implement the spec. Eventually, I hope to get them on a full agile diet, with TDD, scrums, sprints, pair programming, and more. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Bring your questions.