Loading ...
Sorry, an error occurred while loading the content.
 

Re: [XP] Re: [OT] Duplicate notices from Agile 2007?

Expand Messages
  • Ron Jeffries
    ... While I share the sentiment, I am curious why this was an appropriate venue for the posting. Ron Jeffries www.XProgramming.com Only the hand that erases
    Message 1 of 156 , Apr 2, 2007
      Hello, Joshua. On Monday, April 2, 2007, at 7:24:16 PM, you wrote:

      > Many of us received a few hundred of these acceptance and rejection
      > notices today. The rejection notices contain specific reasons to each
      > submitter for why their submission was rejected. The conference
      > organizers have certainly had a lot of work on their hands -- with so
      > many submissions. Nevertheless, they ought to do a better job of
      > testing the software they use and they would do well to apologize to all
      > of the folks who had their rejection notices on display.

      While I share the sentiment, I am curious why this was an
      appropriate venue for the posting.

      Ron Jeffries
      www.XProgramming.com
      Only the hand that erases can write the true thing. -- Meister Eckhart
    • John Roth
      From: Elizabeth Keogh To: Sent: Wednesday, April 18, 2007 7:11 AM Subject: Re: [XP] Agile
      Message 156 of 156 , Apr 18, 2007
        From: "Elizabeth Keogh" <ekeogh@...>
        To: <extremeprogramming@yahoogroups.com>
        Sent: Wednesday, April 18, 2007 7:11 AM
        Subject: Re: [XP] Agile Explanations?


        > Robert Biddle wrote on 17/04/2007 19:58:01:
        >
        >> And when customer-side people bridle at language like "planning game"
        > and
        >> "process smell", then the conversation may be brief.
        >> Lest I seem speculative, I should perhaps mention that I am not making
        > up
        >> these examples: they come from my discussions with people on the
        > customer side.
        >
        > This was our brief conversation:
        >
        > "What's a planning game?"
        >
        > "It's a meeting in which you get the opportunity to prioritise the stories
        > you want, and steer the direction of the iteration."
        >
        > "Can't we call it Iteration Steering, then?"

        You could, but I wouldn't because there's already a meeting with
        that purpose: iteration planning. It's done at the beginning of each
        iteration.

        If I didn't want to call it the Planning Game, I might suggest
        Project Planning or Release Planning. Both of those terms
        suggest taking a look at the project (or at least the release)
        as a whole. Of course, the customer may very well have another
        name that's part of the organization culture.

        John Roth
        >
        > Cheers,
        > Liz.
        >
        > --
        > Elizabeth Keogh
        > liz@...
        > http://sirenian.livejournal.com
        > http://jbehave.org
        >
        >
        > [Non-text portions of this message have been removed]
        >
        >
      Your message has been successfully submitted and would be delivered to recipients shortly.