Startup Lessons Learned

SEPTEMBER 15, 2008

I would add -- think of your development and running your business like a PM/Developer uses Agile or Scrum in software development. You need an overarching vision and goal but just try to get to the next level, one iteration or sprint at a time. No more, no less. September 15, 2008 9:19 PM James said.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

Startup Lessons Learned

SEPTEMBER 10, 2008

There are several ways to make progress evident - the Scrum team model is my current favorite. If you have a true cross-functional team, empowered (a la Scrum) to do whatever it takes to succeed its likely they will converge on the result quickly. When its receding, we rescope. Do you have a spec?

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

The Next Web

DECEMBER 4, 2013

These categories came from Yonder conference , a conference held to discuss just such challenges and solutions: hiring and onboarding. In short, these are the top 10 remote team management lessons I have learned: Find a way to meet at the same time. Hire those you trust. After the scrum, if time allows, hang out and catch up.

Management 152

Management SCRUM CTO Hire Distribution 152

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. We had all the tools in place but we didn’t actually practice agile development.

San Francisco 68

San Francisco SCRUM Lean Continuous Deployment 68