By Isabel Evans

Profitable software program relies not just on technical excellence yet on how participants of the software program group interact. Written in effortless to appreciate language by means of a number one specialist within the box, this ground-breaking quantity offers an outline of the group tradition required to increase caliber software program. Reflecting different perspectives at the nature of software program caliber, the ebook is helping teams in a software program crew to speak extra successfully and to beat the clash created by means of their assorted perceptions of caliber. You research the jobs and actions of staff contributors (including consumers) in the course of the lifetime of a software program product, from prior to the software program improvement begins and through the software program improvement lifecycle, to after the software program has been deployed and is in use.

Show description

Read or Download Achieving Software Quality Through Teamwork PDF

Similar software development books

Oh Crap I Need an App: The Adventures of a Non-Geek Entrepreneur Trying to Get an Application to Make Her Web-Based Business Idea a Reality

Methods to outline your app, rent a seller, and discover a aid community extra quick and for much less cash. Casey Burke Bunn claims to be a normal woman who begun a company at 25 and desires to percentage counsel so that you don’t repeat a few of her very dear errors. you could disagree with the “ordinary” a part of that declare.

What Every Engineer Should Know about Software Engineering

Do you… Use a working laptop or computer to accomplish research or simulations on your day-by-day paintings? Write brief scripts or checklist macros to accomplish repetitive projects? have to combine off-the-shelf software program into your structures or require a number of functions to interact? end up spending an excessive amount of time operating the kinks from your code?

Software-Architektur: Grundlagen - Konzepte - Praxis

Als Architekt arbeiten Sie in einem sehr vielf? ltigen und dynamischen Umfeld. Neue Technologien dr? ngen auf den Markt, neue Werkzeuge versprechen Effizienz- und Produktivit? tssteigerungen und neue traits, wie serviceorientierte Architekturen (SOA) und modellgetriebene Verfahren sollen Ihnen helfen, mit der inh?

JUnit in Action, 2nd edition

Whilst JUnit was once first brought a decade in the past by means of Kent Beck and Erich Gamma, the Agile stream used to be in its infancy, "Test pushed improvement" was once unknown, and unit trying out was once simply beginning to movement into the common developer's vocabulary. at the present time, such a lot builders recognize some great benefits of unit checking out and depend upon the more and more refined instruments now to be had.

Extra resources for Achieving Software Quality Through Teamwork

Sample text

1 Group Attitude Results How IT Infrastructure Staff Software Maintainers Developers Testers Users Developers We’re OK. Don’t listen. Poor quality. Will not document. No business awareness or interpersonal skills. Resist change. A law unto themselves. Resent criticism. Computers are difficult to use and unreliable. IT infrastructure staff Always complaining. We’re OK. Should filter requests. Better customer orientation. Understand. Understand. Software maintainers Unpleasant job, low status. Long delays We’re OK.

We have already mentioned a paper that sets software standards within Six Sigma [9]. In addition, the Software and Systems Quality Framework (SSQF), [18] mentions the EFQM Excellence Model and Baldrige model, Six Sigma, CMM, and ISO 9000 as possible frameworks within which software standards might be adopted, but concentrates on ISO 9000 as the example framework. A useful paper concentrating on testing-related standards can be found on the Testing Standards Web site [19], although it does not mention the EFQM Excellence Model and Baldrige model.

Don’t understand. A luxury. Only if customers demand it. We’re OK. Understand. Testers Unnecessary —we do that! Understand Unnecessary —we do that! Little skill needed. Understand. We’re OK. Users Don’t know what they want. Complain to us about software. Ask for trivial changes. Will not pay for quality but expect it. Will not pay for quality but expect it. Understand. Source: [1]. IT Managers Quality Practitioners View Want delivery We’re OK. too soon to get quality. We don’t want to know about technology.

Download PDF sample

Rated 4.77 of 5 – based on 33 votes