Remove Agile Remove New York Remove SCRUM Remove Technology
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. So far, I have found "lean startup" works better with the entrepreneurs Ive talked to than "agile startup" or even "extreme startup.") Of course, many startups are capital efficient and generally frugal.

Lean 168
article thumbnail

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

Startup Lessons Learned

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. Expo SF (May.

Insiders

Sign Up for our Newsletter

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

article thumbnail

Embrace technical debt

Startup Lessons Learned

I hope to show why lean and agile techniques actually reduce the negative impacts of technical debt and increase our ability to take advantage of its positive effects. Yet other agile principles suggest the opposite, as in YAGNI and DoTheSimplestThingThatCouldPossiblyWork. Reconciling these principles requires a little humility.

article thumbnail

Out of the Crisis #4: Carl Liebert, crisis veteran and radical optimist

Startup Lessons Learned

28:12) The pandemic as a moment to invest in people and technology, have a plan and execute. 44:25) Parallels between the pandemic and previous crises, and Carl's thoughts on some of the new norms that will arise. (45:28) It became brand building and culture building moment for the company. (21:41) Stanley McChrystal's Team of Teams.

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. We had all the tools in place but we didn’t actually practice agile development. Scrum reports would come in once a month, nobody was actually responsible for anything. Expo SF (May.

article thumbnail

How to hire a programmer to make your ideas happen

sivers.org

The idea is that this allows you to get much more clear about what you want to achieve, whats possible with current technology, what other people are doing, how long it might take and how much it is likely to cost. We will even write the invitation to tender for you, based on our discussions. BTW: great keynote at Railsconf!