Re: [extremeprogramming] The principle behind How Test-Driven Development Works

 Beware that in the hands of rigid thinkers, this kind of thinking can
easily lead to Gant charts, critical chains, critical paths, and other
forms of over-planning.

Keep things dynamic and simple.  TDD with good unit test coverage
facilitates just doing things in whatever order the user story slices and
their priorities lead.

On Tue, Oct 29, 2019 at 4:43 AM Agust?n Villena <[email protected]>
wrote:

> Hi all
>
> I'm a big fan of Joe's article
> https://blog.jbrains.ca/permalink/how-test-driven-development-works-and-more
>
> I wanted to check what was "queue theory" principle behind TDD that Joe's
> referred,
>
> "Given a process B, which follows a process A, sometimes in performing B
> we need to perform some of A again. We can remove the need to rework by
> taking some portion of process B and performing it before process A"
>
> but it seems that this principle comes from another source, Theory of
> Constraints, explained in the famous part of the goal of the boy scout
> expedition where Herbie, the slowest kid, should be out at the front of the
> group to improve overall speed.
>
> https://www.mmsonline.com/columns/where-is-your-herbie
>
> Am I ok?
>
> Saludos from Chile
> Agustin Villena
>
>
>
>
> 
>
>

-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.

View/Reply Online (#160159): https://groups.io/g/extremeprogramming/message/160159
Mute This Topic: https://groups.io/mt/39414677/2417047
Group Owner: [email protected]
Unsubscribe: https://groups.io/g/extremeprogramming/leave/4902963/619838065/xyzzy  [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-