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
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.
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.
Introduces, in simple text and photographs, the characteristics of some of the animals and plants that can be found in the forest. Includes a chipmunk, box turtle, fern, bull moose, moth, ermine, and white birch.
Wild West to Agile: The evolution and revolution of software development, drawn from personal experience, from the Apollo moon mission to digital transformations. In 2023, "technology is your business--no matter what your business." But how did we get here and how could a historical perspective prepare us for the future? Jim Highsmith tackles the evolution and revolution of software development, embellishes them with personal experiences, from the Apollo moon mission to modern digital transformations, and introduces the adventurous pioneers--from structured era developer Ken Orr to Agile methodologist Kent Beck--who strived to make the world a better place, by building better software. Jim's six-decade career has encompassed the Wild West (1966-1979), to Structured Methods and Monumental Methodologies (1980s), to the Roots of Agile (1990s), to the present Agile Era (2001-present). In each era, he explores the evolution of software development methods, methodologies, and mindsets. Whether you are from the 1970-1980's generation looking for an "I was there too" moment, a newer generation interested in the evolution of software development, the Agile generation interested in how Agile methodologies were born and evolved, or have a general interest in information technology, Wild West to Agile has something for you. "Jim Highsmith is the Forrest Gump of software development. What made the 1994 movie so entertaining was how frequently Forrest found himself in the right spot as history was being made. Unlike Forrest, though, Jim's actions influenced that history." --Mike Cohn, cofounder of the Agile Alliance, and the Scrum Alliance; author of Succeeding with Agile "If you want to understand the shape of software development today, this is the book for you. If you want to understand how to navigate a turbulent career with grace & style, this is also the book for you. If you enjoy memoirs, ditto. Enjoy his story." --Kent Beck, Chief Scientist, Mechanical Orchard; author, Extreme Programming Explained "This entire journey--beginning with the Wild West era of software development through the Agile Era to today's Digital Transformation era--is entirely empowered by people. Thank you, Jim, for sharing these beautiful stories and honoring the people that were a part of this amazing journey." --Heidi J. Musser, Vice President and CIO, USAA, retired "I've always felt that understanding history is important, because it's hard to understand where we are unless you understand the path that we took to get here. Jim's memoir is an entertaining and astute odyssey through this history." --Martin Fowler, Chief Scientist, Thoughtworks
Organizations report that as much as 50% of investments in IS and IT solutions are judged to be outright failures or deemed highly unsatisfactory. Information Systems Innovation and Diffusion: Issues and Directions reports on innovation and diffusion research and presents theory-based guidelines that will increase the business value of IS/IT investments.
The Software Engineering Institute's Capability Maturity Model( Integration (CMMI) provides best practices that span a product's life cycle, from conception through delivery and maintenance. Employing real-life examples and practical advice, authors Garcia and Turner tap their extensive experience working with diverse organizations to help readers survey the CMMI territory.
