Comments on: Extreme Programming workflow simulation

By: bin amer

bin amer — Mon, 12 Apr 2010 22:38:05 +0000

I have downloaded the pipe2 but how i can run this model? i tried to save it as xml file then open it but it did not work..
So, how can i run this model?

By: How is SCRUM related to a Web Application Tester?

How is SCRUM related to a Web Application Tester? — Fri, 15 May 2009 08:44:37 +0000

[...] Extreme Programming workflow simulation [...]

By: Corey Ladas

Corey Ladas — Tue, 10 Mar 2009 16:39:19 +0000

The accept build transition is there to model the case where the customer decides that she has enough and wants to disengage. Nothing requires her to ever take that transition. That case is important when a team is part of a larger group with internal dependencies or multiple customers. I changed the labels to clarify the intent.

By: Dew Drop - March 10, 2009 | Alvin Ashcraft's Morning Dew

Dew Drop - March 10, 2009 | Alvin Ashcraft's Morning Dew — Tue, 10 Mar 2009 12:11:18 +0000

[...] Extreme Programming workflow simulation (Corey Ladas) [...]

By: Keith Braithwaite

Keith Braithwaite — Tue, 10 Mar 2009 07:31:48 +0000

The limit on stories in flight is called “velocity” and is built in to XP. It’s interesting to have another reason to talk about why that’s important. Thanks.

I’m not convinced by the Customer has problems write a story arc. The customer generally has many more stories in mind than the team can deliver, and new stories are written in parallel with earlier stories being built. I just don’t see XP teams going around a “write stores until no more problems” loop with nothing else going on. Is this a widespread misunderstanding of what goes on in the contemporary planning game? In fact, they just pull as many as they’ve demonstrated they can do off the priority queue.

I also don’t buy that having pending or integrated stories inhibits accepting a build. To my mind iterative development means exactly the opposite: the customer is able (and eager) to accept a build knowing that work remains on some stories (given that other constraints are met).

PIPE2 looks like fun. Post QCon I might have a go at modelling an agile workflow in it myself.