Bargain Hunting

Posted December 28, 2010 by Joshua Kerievsky in Agile Transition, Lean Startup

High value at low cost. There’s nothing quite like finding a bargain.
Read more

11 comments


What’s Wrong With Clean Code?

Posted October 31, 2010 by Joshua Kerievsky in Lean Startup, Software Design

We recently made a dramatic improvement to our kitchen that got me thinking about software design and the striking difference between cleaning code and remodeling it.
Read more

1 comment


Redefining Done

Posted August 2, 2010 by Joshua Kerievsky in Agile Transition, Lean Startup

“A user story is done when the code is fully integrated, all tests pass and the functionality meets the expectations of the story author(s).” The Agile community calls the above statement a Definition of Done.
Read more

14 comments


Sufficient Design In The Sketch, Craft, Refine Cycle

Posted July 1, 2010 by Joshua Kerievsky in Lean Startup, Software Design

Part 3 of X We've recently been working with a rock-star poster artist on new posters for our in-person workshops.
Read more

No comments


Community, Not Product Owner

Posted November 19, 2009 by Joshua Kerievsky in Agile Transition, Lean Startup

Effective collaboration is far more important to us than having a Product Owner (A.K.A. Single Throat To Choke) select and prioritize work. We seek out differences in opinion rather than expect one person to make key decisions.
Read more

3 comments


Ultra Lean Planning

Posted August 22, 2009 by Joshua Kerievsky in Agile Transition, Lean Startup

Our planning process for developing Agile eLearning has become exceedingly lean over the years. What began with traditional Extreme Programming and Industrial XP planning methods, has shrunk into an ultra-lean process that is thoroughly tuned to our culture and context. Our culture is not typical.
Read more

No comments


Visualizing Proficiency

Posted May 22, 2009 by Joshua Kerievsky in Agile eLearning, Lean Startup, Refactoring, Software Design, Test Driven Development

How do we know if someone is truly learning Refactoring and Test-Driven Development? Before 2005, we determined proficiency by literally looking over people's shoulders as they worked. In 2005, we endeavored to automate the "looking-over-the-shoulder" part. We built code that used reflection to automatically check whether a student's solution met certain design criteria.
Read more

No comments