Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • You write that the book "contrasted a plan-driven project team that was employing PSP/TSP and an agile team using Extreme Programming". I'm pretty sure we use a lot of planning for our implementation of XP. I'm a little puzzled to assume that XP'ers don't plan. My experience is different. My two cents.
    – Manfred
    Commented Oct 25, 2011 at 8:30
  • @John Plan-driven methodologies are centered on applying traditional engineering techniques and moving systematically from requirements through, ultimately, a delivery product, while performing verification and validation at step. They are characterized by strong documentation and traceability through the life of the system. There are detailed plans, workflows, and work products (that are things other than working software).
    – Thomas Owens
    Commented Oct 25, 2011 at 9:58