Every person has their own different story of how they found out about Agile and how they came to experiment and ultimately adopt it in their projects.Mine is also different than most, I started as a skeptic. I was one of those that said “it will never work”. But I did come around. Here’s the …
I saw this post and could not resist leaving a comment. Here’s what I wrote as a comment to that post: How can they [Toyota] apply waterfall and be predictive, fast and high-quality? Those are all qualities that waterfall lacks. Predictability is lost because of lack of visibility into quality until it is too late …
The statement in the title is true even for those that are commonly recognized as great, as they say “here today gone tomorrow”. If you really want to be great you should not shout it out loud at every opportunity, you should recognize what your strengths are, play to them and always, always be on …
Through Elisabeth Hendrickson I got to Brett Pettichord’s post about the role of feedback in Agile. Read it if you haven’t yet. Here are the pearls that made me post this: “If you don’t have meaningful feedback then you’re not agile. You’re just in a new form of chaos.” and “Agile practices build a technical …
Here is an excellent piece from the blog Evolving excellence about how a worker at Toyota battled his fear of admitting a mistake and was rewarded by his pears and supervisor for not hiding, but rather disclosing the mistake he had done. Admitting you committed a mistake is a very important part of continuous improvement. …
In a post called “Apple’s Design Process Through a Keyhole”, the blog over at Adaptive Path mentions one technique used at Apple when designing product. The basic idea is that in Apple, designers come up with 10 possible designs for a new feature (and I bet more than 10 for a new product). Then diligently …
