04118nam 22005295 450 991025482150332120200701052941.03-319-54087-410.1007/978-3-319-54087-0(CKB)3710000001364136(DE-He213)978-3-319-54087-0(MiAaPQ)EBC4855705(PPN)201474409(EXLCZ)99371000000136413620170505d2017 u| 0engurnn|008mamaatxtrdacontentcrdamediacrrdacarrierThe Journey to Enterprise Agility Systems Thinking and Organizational Legacy /by Daryl Kulak, Hong Li1st ed. 2017.Cham :Springer International Publishing :Imprint: Springer,2017.1 online resource (XIX, 286 p. 35 illus., 32 illus. in color.) 3-319-54086-6 Includes bibliographical references and index.Today’s Problems with Enterprise Business Software -- The Scholars of Systems Thinking -- Worldview and Intentions -- Seven Principles of Systems Thinking for Software Development -- Redefining Professionalism -- Scaling and Sustaining – Avoiding Mechanical Behavior -- Business Value, Estimation and Metrics -- Missing Deadlines Means Missing Market Opportunities -- Flipping the Run/Build Ratio – The Business Case for Software Craftsmanship -- Better Vendor RFPs and Contracts -- Servant Leadership -- How Teams Keep Learning and Improving -- Getting Coaching that Really Helps -- Capitalizing Software Investments -- Integrating Enterprise Methodology and Architecture with Fast-Moving Development Teams -- HR Agility -- Buy versus Build -- Brief Notes on Using Offshore Teams -- Highlighting the Differences Between Software Product Companies and Internal IT -- Conclusion.This is the first book to seriously address the disconnection between nimble Agile teams and other groups in the enterprise, including enterprise architecture, the program management office (PMO), human resources, and even business executives. When an enterprise experiments with practice improvements, software development teams often jump on board with excitement, while other groups are left to wonder how they will fit in. We address how these groups can adapt to Agile teams. More importantly, we show how many Agile teams cause their own problems, damaging scalability and sustainability, by requiring special treatment, and by failing to bridge the gaps between themselves and other groups. We call this phenomenon “Agile illth.” Adopting a set of “best practices” is not enough. All of us, Agile teams and the corporate groups, must change our intentions and worldviews to be more compatible with the success of the enterprise. Join us on the journey to enterprise agility. It is a crooked path, fraught with danger, confusion and complexity. It is the only way to reach the pinnacles we hope to experience in the form of better business value delivered faster for less cost.Management information systemsComputer scienceSoftware engineeringManagement of Computing and Information Systemshttps://scigraph.springernature.com/ontologies/product-market-codes/I24067Software Managementhttps://scigraph.springernature.com/ontologies/product-market-codes/522050Software Engineeringhttps://scigraph.springernature.com/ontologies/product-market-codes/I14029Management information systems.Computer science.Software engineering.Management of Computing and Information Systems.Software Management.Software Engineering.005.74Kulak Darylauthttp://id.loc.gov/vocabulary/relators/aut1063649Li Hongauthttp://id.loc.gov/vocabulary/relators/autBOOK9910254821503321The Journey to Enterprise Agility2533348UNINA