At its heart, Agile is a very simple inspect-and-adapt process. The problem is that simple measures often aren’t comfortable or easy.
In my last post, I talked about that moment when a person, team, or even company is confronted with collected data (the inspect phase) that is challenging to their self image and – instead of adapting – decides to ignore the information, therefore sabotaging their progress.
To understand why and how that can happen, we need to first take into consideration two factors governing our behavior…
Today I replayed the video of a mastermind group that I’m running. It was painful. I saw so many flaws in how I had led the meeting. I saw people confused by the opening statements. I saw where I hadn’t
By Cindy Solomon, from her blog on Startup Product The first Startup Product Academy stand-alone, full day course was Intro to Agile on December 16, 2013 in Oakland, CA. Startup Product Academy is a product of the Startup Product
I volunteered heavily for Railsbridge from about 2009 to 2011, and intermittently since then when I had time between projects. When I “tuned in” again in fall of 2013, I found the organization has been tremendously successful: over 70
The team space contains two tables facing a large (10’ x 5’) projection area. It feels like the split-screen arrangement I’ve seen many developers using, only much, much larger. It’s easy for all six of us to sit on the
A.K.A. “How to get that first scrum master job.” I’ve answered this question twice in the past two weeks, and when it came up again today on a mailing list, I figured I’d cross post here. Basically, it takes both