Remove Continuous Deployment Remove Metrics Remove SCRUM Remove Software
article thumbnail

Lessons Learned: Combining agile development with customer development

Startup Lessons Learned

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.

Agile 111
article thumbnail

Lessons Learned: The lean startup

Startup Lessons Learned

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. Case Study: Continuous deployment makes releases n. No more, no less.

Lean 168
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: A new version of the Joel Test (draft)

Startup Lessons Learned

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. For more on continuous deployment, see Just-in-time Scalability.

article thumbnail

Lessons Learned: The product manager's lament

Startup Lessons Learned

So the product manager winds up actually having to use the software, by hand, updating the spec and helping create a new test plan. Eventually, I hope to get them on a full agile diet, with TDD, scrums, sprints, pair programming, and more. Case Study: Continuous deployment makes releases n.

article thumbnail

Embrace technical debt

Startup Lessons Learned

To do that, we add specific speed regulators, like integrating source control with our continuous integration server or the more elaborate dance required for continuous deployment. Let's consider cases: Can you have a piece of software with good product design and bad technical design? One last thought.

article thumbnail

Lessons Learned: Built to learn

Startup Lessons Learned

dalelarson : "Metrics are people, too." leanstartup ericnsantos : #w2e #leanstartup Metrics should be Actionable, Accessible and Auditable. Metrics are a key questions startups face. Metrics are people too" is a reminder I constantly needed when I was a manager. ericries s talk on Lean Startups absolutely fantastic.

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. My favorite instance of this is scheduling software. Case Study: Continuous deployment makes releases n.