Hope it helps! It is… after all… another “list” of sorts… ha!
By: peter
By: Jordan
The most recent post on my blog covers why these people are so important…
Jordan
By: Jordan
Now with url
By: Nick Jenkins
Glad to hear that Lean could be considered the future of agile. It should be up for debate, like all good things, and the best of both will survive to become something new.
But I also think there’s more of Lean in agile than most people realise.
TDD & BDD for example are what Lean would call jidoka or autonomation. I think there is more Lean influence in modern agile than people realise.
And “having eyes for waste” is a concept so beautiful that once you understand it, it will influence everything you do – from agile devlopment to planning your next holiday to running your business.
By: peter
Nick, thanks a ton for your thoughtful comments. Love your “eyes for waste” comment. Totally true!
I see Agile… in a sense falling under a “lean umbrella” of sorts… could cause some debate here… but it’s kind of true!
By: Jordan
Eliminating waste is great, but that requires architects and knowledgable engineers, which is against the more proletariat leaning Agile right?
And isn’t TDD against the Toyota canon of “Build quality in, don’t test quality in?”
Lean and Agile aren’t interchangable, relevant to each other, or even relevant to software development in general.
But they are both trendy…
Jordan
By: peter
TDD means “Test… Doh… Derp…”
By: YvesHanoulle
Jordan
>And isn’t TDD against the Toyota canon of “Build quality in, don’t >test quality in?”
I think that TDD is actually the Toyota version of unit testing
As with TDD you will start with testing and asking you what you expect from the code. > build quality in.
Unit testing without TDD, could be seen as testing quality in.
By: Jordan
Sorry, not seeing it. Do you have anything to support the conjecture that TDD is the Toyota version of unit testing?
There is nothing in TDD that talks at all about building quality in.
TDD only talks about that the code must pass the unit tests. You throw code at it until the tests are green. That is testing quality in. That is not building quality in.
You can compare Ron Jeffries approach to building a sudoku problem solver to Peter Norvigs (google it). Norvig built quality in. Jeffries tested quality in. Jeffries was never able to actually get a working solver using TDD; Norvig was.
Jordan
By: New PM Articles for the Week of May 7 – 13 | The Practicing IT Project Manager
[...] Peter Saddington recaps the history of Agile – the movers, the shakers, the influencers, and the drivers that got us here. [...]
By: The 8 C’s of Agile Coaching » Agile Scout
[...] don’t compromise (Agile foundational truth) [...]
By: Jordan
The most recent post on my blog covers why these people are so important… 🙂
Jordan
By: Jordan
Now with url 🙂
By: Nick Jenkins
Glad to hear that Lean could be considered the future of agile. It should be up for debate, like all good things, and the best of both will survive to become something new.
But I also think there’s more of Lean in agile than most people realise.
TDD & BDD for example are what Lean would call jidoka or autonomation. I think there is more Lean influence in modern agile than people realise.
And “having eyes for waste” is a concept so beautiful that once you understand it, it will influence everything you do – from agile devlopment to planning your next holiday to running your business.
By: peter
Nick, thanks a ton for your thoughtful comments. Love your “eyes for waste” comment. Totally true!
I see Agile… in a sense falling under a “lean umbrella” of sorts… could cause some debate here… but it’s kind of true!
By: Jordan
Eliminating waste is great, but that requires architects and knowledgable engineers, which is against the more proletariat leaning Agile right?
And isn’t TDD against the Toyota canon of “Build quality in, don’t test quality in?”
Lean and Agile aren’t interchangable, relevant to each other, or even relevant to software development in general.
But they are both trendy…
Jordan
By: peter
TDD means “Test… Doh… Derp…” 😉
By: YvesHanoulle
Jordan
>And isn’t TDD against the Toyota canon of “Build quality in, don’t >test quality in?”
I think that TDD is actually the Toyota version of unit testing
As with TDD you will start with testing and asking you what you expect from the code. > build quality in.
Unit testing without TDD, could be seen as testing quality in.
By: Jordan
Sorry, not seeing it. Do you have anything to support the conjecture that TDD is the Toyota version of unit testing?
There is nothing in TDD that talks at all about building quality in.
TDD only talks about that the code must pass the unit tests. You throw code at it until the tests are green. That is testing quality in. That is not building quality in.
You can compare Ron Jeffries approach to building a sudoku problem solver to Peter Norvigs (google it). Norvig built quality in. Jeffries tested quality in. Jeffries was never able to actually get a working solver using TDD; Norvig was.
Jordan
By: New PM Articles for the Week of May 7 – 13 | The Practicing IT Project Manager
[…] Peter Saddington recaps the history of Agile – the movers, the shakers, the influencers, and the drivers that got us here. […]