000013246 000__ 02712cam\a2200541\i\4500
000013246 001__ 13246
000013246 003__ SzGeWIPO
000013246 005__ 20210318092556.0
000013246 008__ 031003s2000\\\\mau\\\\\rb\\\u001\0\eng\d
000013246 020__ $$a0201710919
000013246 020__ $$z9780201710915$$qpaperback
000013246 035__ $$a(wipo)(CD )03-0376
000013246 035__ $$a(OCoLC)1158215222
000013246 040__ $$aSzGeWIPO$$beng$$erda$$cSzGeWIPO$$dCaBNVSL
000013246 050_4 $$aQA76.76.D47$$bB4335 2001
000013246 08204 $$a005.3$$221
000013246 08204 $$a005.1201$$222
000013246 084__ $$aD 73 BEC.P
000013246 090__ $$c13911$$d13911
000013246 1001_ $$aBeck, Kent,$$eauthor.
000013246 24510 $$aPlanning extreme programming /$$cKent Beck, Martin Fowler ; illustrated by Jennifer Kohnke ; [foreword by Tom DeMarco].
000013246 264_1 $$aBoston :$$bAddison-Wesley,$$c2000.
000013246 300__ $$axvii, 139 pages ;$$c[28] cm.
000013246 336__ $$atext$$btxt$$2rdacontent
000013246 337__ $$aunmediated$$bn$$2rdamedia
000013246 338__ $$avolume$$bnc$$2rdacarrier
000013246 4901_ $$aThe Xp Series
000013246 500__ $$aAngekündigt als: Beck, Kent: Steering & planning with extreme programming.
000013246 500__ $$aIndhold: Why plan? Fear. Dring software. Balancing power. Overviews. Too much to do. Four variables. Yesterday's weather. Scoping a project. Release planning. Writing stories. Estimation. Ordering te stories. Relaease planning events. The first plan. Release planning variations. Iteration plannning. Iteration planning meeting. Tracking an interation. Stand-up meetings. Visible graphs. Dealing with bugs. Changes to the team. Tools. Business contracts. Red flags. Your own process.
000013246 5201_ $$a"Within this context of flexibility and rapid-fire changes, planning is critical; without it, software projects can quickly fall apart. Written by acknowledged XP authorities Kent Beck and Martin Fowler, Planning Extreme Programming presents the approaches, methods, discipline, and advice you need to plan and track a successful Extreme Programming project. The key XP philosophy: Planning is not a one-time event, but a constant process of reevaluation and course-correction throughout the life cycle of the project."
000013246 650_0 $$aeXtreme programming.
000013246 650_0 $$aAgile software development.
000013246 650_0 $$aComputer software$$xDevelopment.
000013246 650_0 $$aComputer software.
000013246 650_0 $$aProject management.
000013246 650_0 $$aSoftware engineering$$xPlanning.
000013246 650_4 $$aPROJECT MANAGEMENT
000013246 650_4 $$aCOMPUTER PROGRAMS
000013246 650_4 $$aCOMPUTER PROGRAMMING
000013246 7001_ $$aFowler, Martin,$$d1963-
000013246 7001_ $$aBeck, Kent.
000013246 7001_ $$aDeMarco, Tom.
000013246 7001_ $$aKohnke, Jennifer M.
000013246 830_0 $$aXp Series.
000013246 903_0 $$aThe XP Series$$v1
000013246 942__ $$cMON
000013246 952__ $$w2006-11-03$$p2003-0376$$r51.00$$u14722$$bMAIN$$10$$kD 73 BEC.P$$v2003-10-03$$zIT Section$$70
000013246 980__ $$aBIB
000013246 999__ $$c13911$$d13911