Remove Agile Remove Non-Compete Remove Software Review
article thumbnail

Case Study: Lean UX at work

Startup Lessons Learned

Originally a waterfall shop, we transitioned to Agile development about two years ago. Now entering our third year with Agile we’re continually trying to improve the efficiency, productivity and velocity of the various teams. Levels of Agile adoption span the full spectrum across our 6 Scrum teams.

Lean 165
article thumbnail

Responses to Negative Data: Four Senior Leadership Archetypes.

Occam's Razor

For three of the four, I’ve seen individuals successfully navigate the leader-type – never without scars though – and individuals emotionally burn-out due the environment the leader creates. To poke holes in the data/methodology (regardless of the Rationalizer’s analytical competence). They dilute the analysis with non-facts.

Insiders

Sign Up for our Newsletter

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

Trending Sources

article thumbnail

Revisiting the Software Design Manifesto (and what's changed since.

Startup Lessons Learned

Lessons Learned by Eric Ries Saturday, August 8, 2009 Revisiting the Software Design Manifesto (and whats changed since then) My recent article on technical debt and its positive uses generated a fair bit of controversy. The same might be said of good software. Here we have the beginnings of a theory of design for software.

article thumbnail

HOW TO: Hire the Perfect CTO

mashable.com

Leadership Abilities Are A Must It’s natural to want a tech savvy and competent CTO. As a non-technical founder of an IT company, it’s important to know when to dish responsibilities off. Be sure you find someone who is not just competent in understanding technology, but someone who is passionate about technology.

article thumbnail

Product design debt versus Technical debt

andrewchenblog.com

You often end up with lots of half-done experiments lying around, an infrastructure that isn’t built to scale, and a mishmash of code that needs to be refactored. For example, a design approach just turns out to be error-prone or a junior programmer just writes bad code. Of course, we are mostly interested in the second type.

article thumbnail

Lessons Learned: Five Whys

Startup Lessons Learned

His book Toyota Production System: Beyond Large-Scale Production is a fascinating read, even though its decidedly non-practical. A new bit of code contained an infinite loop! why did that code get written? Most engineers would ship code to production on their first day. Best of luck, Your Software." (OK,

article thumbnail

Top 57 Online Startups Meets Technology Meets Product Posts for November 2010

SoCal CTO

The United States is now a debtor nation to China and that the bill is about to come due. Five Reasons You Haven’t Launched - Software By Rob , November 10, 2010 Photo by stevendepolo. These are probably the two sites where I've posted the most reviews. Put likable, competent and passionate people on the front line.