Your email was sent successfully. Check your inbox.

An error occurred while sending the email. Please try again.

Proceed reservation?

Export
Filter
  • MPI Ethno. Forsch.  (2)
  • Regensburg UB
  • 2000-2004  (2)
  • McBreen, Pete  (2)
  • Boston : Addison-Wesley  (2)
  • Berkeley : University of California Press
Datasource
  • MPI Ethno. Forsch.  (2)
  • Regensburg UB
Material
Language
Years
  • 2000-2004  (2)
Year
Publisher
  • 1
    Online Resource
    Online Resource
    Boston : Addison-Wesley | Boston, MA :Safari,
    Language: English
    Pages: xxi, 201 p. ; , 24 cm
    DDC: 005.1
    Keywords: Computer software ; Development ; eXtreme programming ; Electronic books ; local
    Abstract: Extreme Programming (XP) has been the subject of heated debate since its arrival on the programming scene in 1998-understandably so, as it contradicts many traditional software development beliefs. We¿ve heard success stories about sweeping changes made to organizations as a result of XP. We've read books about how this approach can work for our teams. However, are there times when XP isn't appropriate? There are certainly instances when making the leap to XP could potentially jeopardize a whole project. What's missing from all of this rhetoric? Witness Pete McBreen, software craftsman, examine the issue from both sides. In Questioning Extreme Programming , the author helps you examine and answer the following questions: Is the cost of change really low? Does XP allow proper testing? Does XP make sense? Is XP a return to the dark ages? Can we adopt XP practices for other approaches? Do you need process improvement or process change? Why are developers so zealous about adopting XP? Is XP suitable for your projects? What is the next step after Extreme Programming? After reading this thought-provoking book, software developers can make informed decisions about Extreme Programming, and whether it is suitable for their organization. Readers will also be able to determine whether Extreme Programming is inappropriate for a particular project. The author challenges you to look past the hype and start asking the hard questions about how software is built. Discover for yourself. 0201844575B07092002
    Note: Includes bibliographical references (p. 187-190) and index
    Library Location Call Number Volume/Issue/Year Availability
    BibTip Others were also interested in ...
  • 2
    Online Resource
    Online Resource
    Boston : Addison-Wesley | Boston, MA :Safari,
    Language: English
    Pages: xvii, 187 p. ; , 24 cm
    DDC: 005.3
    Keywords: Computer software ; Development ; Electronic books ; local
    Abstract: By recognizing that software development is not a mechanical task, you can create better applications. Today's software development projects are often based on the traditional software engineering model, which was created to develop large-scale defense projects. Projects that use this antiquated industrial model tend to take longer, promise more, and deliver less. As the demand for software has exploded, the software engineering establishment has attempted to adapt to the changing times with short training programs that teach the syntax of coding languages. But writing code is no longer the hard part of development; the hard part is figuring out what to write. This kind of know-how demands a skilled craftsman, not someone who knows only how to pass a certification course. Software Craftsmanship presents an alternative-a craft model that focuses on the people involved in commercial software development. This book illustrates that it is imperative to turn from the technology-for-its-own-sake model to one that is grounded in delivering value to customers. The author, Pete McBreen , presents a method to nurture mastery in the programmer, develop creative collaboration in small developer teams, and enhance communications with the customer. The end result-skilled developers who can create, extend, and enhance robust applications. This book addresses the following topics, among others: Understanding customer requirements Identifying when a project may go off track Selecting software craftsmen for a particular project Designing goals for application development Managing software craftsmen Software Craftsmanship is written for programmers who want to become exceptional at their craft and for the project manager who wants to hire them. 0201733862B07242001
    Note: Includes index
    Library Location Call Number Volume/Issue/Year Availability
    BibTip Others were also interested in ...
Close ⊗
This website uses cookies and the analysis tool Matomo. More information can be found here...