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. Amazon PostRank

Lean 168

Lean San Francisco Startup Continuous Deployment 168

Startup Lessons Learned

DECEMBER 14, 2017

And the effort was reflected by the 140 speakers and mentors who took the stage and ran workshops over the course of the seven-day conference. The result is a combination of design thinking, Lean Startup, and Agile Scrum, and Ignacio’s innovation team includes 25 coaches who train employees in PACE best practices. They’re qualified.

Lean 245

Lean Startup CTO Hire Cofounder 245

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? Amazon PostRank

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

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. Amazon PostRank

San Francisco 68

San Francisco SCRUM Lean Continuous Deployment 68