Belated response ;-)

Taskcard is clearly overkill for an experienced team doing full-on XP in a single room. I believe that's only a fraction of the people using some elements of XP, and an even smaller fraction of those who could benefit from a centralized task repository.

Fair enough.

I guess my problem (and it may just be "my" problem :-) is you calling Taskcard "XP-style" since, to me, it isn't very.

Taskcard has things like start/end dates for tasks, etc. Non-XP things for cards. The list of things you'd like to do are even less-XPish, and more like a project management system in the MS Project mold.

I believe that more agile methods, and XP in particular are excellent software development techniques. As a contractor/consultant I often am faced with the task of introducing these methods into an organisation. On occasion I have problems because people have "tried XP" and it has failed. However, on closer examination they have only tried something that bears a superficial resemblance to one aspect of XP.

I can just see a point in the future when somebody says "we tried the XP planning game and it didn't work" when what they really mean is "we tried Taskcard and it didn't work".

Not that this would necessarily be a fault in Taskcard of course. Just a fault in the way it was used. However, because you say it's "XP-style" the failure will be laid at the door of XP.

If you're trying to manage 5 volunteers on an OSS project, each in different time zones and each with only a few hours to spare each week, I think Taskcard could be really valuable. There's some feature work to do, but much interface design: when it's ready, it'll look simpler and do more.

Cool. Look forward to it :-)

In reply to Re^3: CPAN: install programs and namespaces by adrianh
in thread CPAN: install programs and namespaces by legLess

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.