Quality Software Management: Congruent action

Quality Software Management: Congruent action

Author: Gerald M. Weinberg

Publisher: Dorset House Publishing Company, Incorporated

Published: 1991

Total Pages: 336

ISBN-13:

DOWNLOAD EBOOK

Partial ContentsI Managing Yourself- Why Congruence Is Essential to Managing- Choosing Management- Styles of Coping- Transforming Incongruence into Congruence- Moving Toward CongruenceII Managing Others- Analyzing the Manager's Job- Recognizing Preference Differences- Temperament Differences- Recognizing Differences As Assets- Patterns of Incongruence- The Technology of Human BehaviorIII Achieving Congruent Management- Curing the Addiction to Incongruence- Ending the Placating Addiction- Ending the Blaming Addiction- Engaging the Other- Reframing the Context- Informative FeedbackIV Managing the Team Context- Why Teams?- Growing Teams- Managing in a Team Environment- Starting and Ending TeamsV EpilogueAppendicesA: Diagram of EffectsB: Satir Interaction ModelC: Software Engineering Cultural PatternsD: Control ModelsE: Three Observer PositionsNotesListing of Laws, Rules, and PrinciplesAuthor IndexSubject Index


Quality Software Management, Volume 1: Systems Thinking, Paperback Edition

Quality Software Management, Volume 1: Systems Thinking, Paperback Edition

Author: Gerald M. Weinberg

Publisher: Dorset House Publishing Company, Incorporated

Published: 2011-02-01

Total Pages: 318

ISBN-13: 9780932633729

DOWNLOAD EBOOK

High-quality software demands high-quality management. That's the subject of Quality Software Management, a four-volume series that has grown out of acclaimed author Gerald M. Weinberg's forty-year love affair with computers. In Volume 1, Systems Thinking, the author tackles the first requirement for developing quality software: learning to think correctly—about problems, solutions, and quality itself. He also sets out guidelines that stimulate the kind of thinking needed. "Act early, act small" is key to staying in control of the software process. Managers need to serve as both planners and catalysts within the organization: to continually plan what to do, observe what happens, and then act decisively to bring the actual closer to the planned. Numerous examples illustrate "control points," areas that can be managed to prevent a crisis or to keep one from getting worse. Topics include: * understanding quality * pressure and breakdowns * software cultures * patterns of quality * patterns of management * feedback effects * the size/complexity dynamic in software engineering * detecting failures and reacting to them * fault resolution dynamics * the role of customers. Useful diagrams, references, exercises, and a bibliography augment the text.


Software Project Management

Software Project Management

Author: Lawrence J. Peters

Publisher: CRC Press

Published: 2024-06-14

Total Pages: 245

ISBN-13: 104003523X

DOWNLOAD EBOOK

The management of a software project has been shown to be the number one factor in determining a software development project’s success. It has been found that most software projects fail because of poor management. Not surprisingly, most software development managers have not been trained in project management. Software Project Management: Methods and Techniques aims to remedy this situation in two ways: familiarizing software developers with the elements of the project management discipline and providing fact-based resources on practicing software project management. Much like the checklist pilots go through prior to a flight, this book provides a pre-project checklist which enables the software engineering team to review and evaluate an extensive set of technical and sociopolitical risks which will help the software project manager and the team determine the project team’s chances of success. This same list and the individual question responses can be used later as part of the project’s closeout process helping team members to improve their individual and collective abilities to assess risk. Intended for both students and software project managers, the book is organized along the lines of the five major functions of a software project manager: planning; scheduling and costing; controlling; staffing; and motivating. The basics of each of these functions are presented in a single chapter. These are followed by a series of narrow topic presentations in the form of appendices that are intended to help solve specific problems that may occur during the conduct of a software project. As in the main portion of the text, the appendices include references that provide an avenue into further detail on the topic. Designed to promote project success, this approach has been taken because software projects are each unique undertakings such that providing a "one size fits all" approach will fail most of the time.


Quality Software Management: Systems thinking

Quality Software Management: Systems thinking

Author: Gerald M. Weinberg

Publisher: Dorset House Publishing Company, Incorporated

Published: 1992

Total Pages: 344

ISBN-13:

DOWNLOAD EBOOK

In the first of three volumes about quality, management, and productivity, Weinberg discusses software development organizations in terms of their culture, and he observes the patterns of their behavior. Organizations can be classified as one of six cultural patterns, ranging from Pattern One (obvio


The Software Project Manager's Handbook

The Software Project Manager's Handbook

Author: Dwayne Phillips

Publisher: John Wiley & Sons

Published: 2004-07-01

Total Pages: 504

ISBN-13: 9780471674207

DOWNLOAD EBOOK

Software project managers and their team members work individually towards a common goal. This book guides both, emphasizing basic principles that work at work. Software at work should be pleasant and productive, not just one or the other. This book emphasizes software project management at work. The author's unique approach concentrates on the concept that success on software projects has more to do with how people think individually and in groups than with programming. He summarizes past successful projects and why others failed. Visibility and communication are more important than SQL and C. The book discusses the technical and people aspects of software and how they relate to one another. The first part of the text discusses four themes: (1) people, process, product, (2) visibility, (3) configuration management, and (4) IEEE Standards. These themes stress thinking, organization, using what others have built, and people. The second part describes the software management principles of process, planning, and risk management. Part three discusses software engineering principles, the technical aspects of software projects. The fourth part examines software practices giving practical meaning to the individual topics covered in the preceding chapters. The final part of this book continues these practical aspects by illustrating a sample project through seven distinctive documents.


Improving Software Development Productivity

Improving Software Development Productivity

Author: Randall W. Jensen

Publisher: Pearson Education

Published: 2015

Total Pages: 368

ISBN-13: 0133562670

DOWNLOAD EBOOK

In Improving Software Development Productivity, legendary software engineering expert Dr. Randall Jensen introduces a proven quantitative approach to achieving high productivity through management support, the ability to communicate, and technology. Jensen demonstrates how to measure organizational capacity and productivity, and use that information to build more accurate estimates and schedules -- and, more broadly, to improve many facets of developer and team performance. Students will learn to quantitatively predict the productivity impact of management decisions related to personnel and management style, development environment, product constraints, technology, development systems, and more.


Software Project Management for Distributed Computing

Software Project Management for Distributed Computing

Author: Zaigham Mahmood

Publisher: Springer

Published: 2017-04-04

Total Pages: 391

ISBN-13: 3319543253

DOWNLOAD EBOOK

This unique volume explores cutting-edge management approaches to developing complex software that is efficient, scalable, sustainable, and suitable for distributed environments. Practical insights are offered by an international selection of pre-eminent authorities, including case studies, best practices, and balanced corporate analyses. Emphasis is placed on the use of the latest software technologies and frameworks for life-cycle methods, including the design, implementation and testing stages of software development. Topics and features: · Reviews approaches for reusability, cost and time estimation, and for functional size measurement of distributed software applications · Discusses the core characteristics of a large-scale defense system, and the design of software project management (SPM) as a service · Introduces the 3PR framework, research on crowdsourcing software development, and an innovative approach to modeling large-scale multi-agent software systems · Examines a system architecture for ambient assisted living, and an approach to cloud migration and management assessment · Describes a software error proneness mechanism, a novel Scrum process for use in the defense domain, and an ontology annotation for SPM in distributed environments · Investigates the benefits of agile project management for higher education institutions, and SPM that combines software and data engineering This important text/reference is essential reading for project managers and software engineers involved in developing software for distributed computing environments. Students and researchers interested in SPM technologies and frameworks will also find the work to be an invaluable resource. Prof. Zaigham Mahmood is a Senior Technology Consultant at Debesis Education UK and an Associate Lecturer (Research) at the University of Derby, UK. He also holds positions as Foreign Professor at NUST and IIU in Islamabad, Pakistan, and Professor Extraordinaire at the North West University Potchefstroom, South Africa.


Creating a Software Engineering Culture

Creating a Software Engineering Culture

Author: Karl E. Wiegers

Publisher: Addison-Wesley

Published: 2013-07-15

Total Pages: 579

ISBN-13: 0133489299

DOWNLOAD EBOOK

This is the digital version of the printed book (Copyright © 1996). Written in a remarkably clear style, Creating a Software Engineering Culture presents a comprehensive approach to improving the quality and effectiveness of the software development process. In twenty chapters spread over six parts, Wiegers promotes the tactical changes required to support process improvement and high-quality software development. Throughout the text, Wiegers identifies scores of culture builders and culture killers, and he offers a wealth of references to resources for the software engineer, including seminars, conferences, publications, videos, and on-line information. With case studies on process improvement and software metrics programs and an entire part on action planning (called “What to Do on Monday”), this practical book guides the reader in applying the concepts to real life. Topics include software culture concepts, team behaviors, the five dimensions of a software project, recognizing achievements, optimizing customer involvement, the project champion model, tools for sharing the vision, requirements traceability matrices, the capability maturity model, action planning, testing, inspections, metrics-based project estimation, the cost of quality, and much more! Principles from Part 1 Never let your boss or your customer talk you into doing a bad job. People need to feel the work they do is appreciated. Ongoing education is every team member’s responsibility. Customer involvement is the most critical factor in software quality. Your greatest challenge is sharing the vision of the final product with the customer. Continual improvement of your software development process is both possible and essential. Written software development procedures can help build a shared culture of best practices. Quality is the top priority; long-term productivity is a natural consequence of high quality. Strive to have a peer, rather than a customer, find a defect. A key to software quality is to iterate many times on all development steps except coding: Do this once. Managing bug reports and change requests is essential to controlling quality and maintenance. If you measure what you do, you can learn to do it better. You can’t change everything at once. Identify those changes that will yield the greatest benefits, and begin to implement them next Monday. Do what makes sense; don’t resort to dogma.