Buch, Englisch, 286 Seiten, Previously published in hardcover, Format (B × H): 155 mm x 235 mm, Gewicht: 4686 g
Systems Thinking and Organizational Legacy
Buch, Englisch, 286 Seiten, Previously published in hardcover, Format (B × H): 155 mm x 235 mm, Gewicht: 4686 g
ISBN: 978-3-319-85313-0
Verlag: Springer International Publishing
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 enterpriseagility. 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.
Zielgruppe
Professional/practitioner
Autoren/Hrsg.
Fachgebiete
- Mathematik | Informatik EDV | Informatik Angewandte Informatik Wirtschaftsinformatik
- Wirtschaftswissenschaften Betriebswirtschaft Management Unternehmensorganisation & Entwicklungsstrategien
- Mathematik | Informatik EDV | Informatik Programmierung | Softwareentwicklung Software Engineering Agile Softwareentwicklung
- Wirtschaftswissenschaften Betriebswirtschaft Wirtschaftsinformatik, SAP, IT-Management
Weitere Infos & Material
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.