000 | 05134nam a22005175i 4500 | ||
---|---|---|---|
001 | 978-3-319-41478-2 | ||
003 | DE-He213 | ||
005 | 20200420221255.0 | ||
007 | cr nn 008mamaa | ||
008 | 160831s2016 gw | s |||| 0|eng d | ||
020 |
_a9783319414782 _9978-3-319-41478-2 |
||
024 | 7 |
_a10.1007/978-3-319-41478-2 _2doi |
|
050 | 4 | _aQA76.758 | |
072 | 7 |
_aUMZ _2bicssc |
|
072 | 7 |
_aCOM051230 _2bisacsh |
|
082 | 0 | 4 |
_a005.1 _223 |
100 | 1 |
_aBook, Matthias. _eauthor. |
|
245 | 1 | 0 |
_aTamed Agility _h[electronic resource] : _bPragmatic Contracting and Collaboration in Agile Software Projects / _cby Matthias Book, Volker Gruhn, R�udiger Striemer. |
264 | 1 |
_aCham : _bSpringer International Publishing : _bImprint: Springer, _c2016. |
|
300 |
_aXVI, 334 p. 66 illus., 20 illus. in color. _bonline resource. |
||
336 |
_atext _btxt _2rdacontent |
||
337 |
_acomputer _bc _2rdamedia |
||
338 |
_aonline resource _bcr _2rdacarrier |
||
347 |
_atext file _bPDF _2rda |
||
505 | 0 | _aPart I: Introduction -- 1. The Need for Tamed Agility -- Part II: The Interaction Room -- 2. A Room for Ideas -- 3. Interaction Room Basics -- 4. Using an Interaction Room for Digitalization Strategy Development (IR:digital) -- 5 Using an Interaction Room for Software Project Scoping (IR:scope) -- 6. Using an Interaction Room for Mobile Application Development (IR:mobile) -- 7. Using an Interaction Room for Technology Evaluation (IR:tech) -- 8 Using an Interaction Room for Agile Project Monitoring (IR:agile) -- 9. Using Interaction Rooms Under Difficult Conditions -- 10. Summary -- Part III: The adVANTAGE contract model -- 11. Framing Software Projects in Commercial Terms -- 12 Traditional Contract Models in an Agile World -- 13. Agile Contract Models -- 14. Key adVANTAGE Principles -- 15 adVANTAGE Procedures -- 16. adVANTAGE in Practice -- 17 Summary -- Part IV: A Sample Project -- 18 Case Study: The Cura Health Insurance Benefit System -- 19 Initial Project Scoping with the IR:scope -- 20 Project Monitoring with the IR:agile -- 21 Lessons Learned -- Part V: Conclusion -- 22 The Big Picture -- 23 A New Skill Set -- 24 Outlook: Twelve Hypotheses -- Appendix -- 25 Interaction Room Workshop Agendas -- 26 Interaction Room Annotations -- 27 adVANTAGE Contract Template -- Index. . | |
520 | _aThis book describes pragmatic instruments and methods that enable business experts and software engineers to develop a common understanding of complex software systems, to determine key requirements, and to manage projects in a way that fosters trust, encourages innovation and distributes risk fairly between clients and contractors. After an introduction to the fundamentals of agile software development in Part I, Part II describes the Interaction Room, an actual room where digitalization and mobilization strategies are developed, where technology potentials are evaluated, where software projects are planned and managed, and where business and technical stakeholders can communicate face to face, visualize complex relationships intuitively, and highlight value, effort and risk drivers that are keys to the project's success. After addressing these constructive aspects, the book focuses on the commercial aspects of software development: The adVANTAGE contract model described in Part III ensures that the insight-driven innovation process of software development does not just function, but is allowed to flourish in a trusted client-contractor relationship. Even though software contracting and construction may be grounded in two different academic disciplines, they are inseparable in practice, and how they interact is illustrated in the case study of developing a private health insurance benefit system in Part IV. Ultimately though, the success of every software project depends on the skills of the stakeholders. Part V therefore describes the qualification profile that software engineers and domain experts have to satisfy today. This book is aimed at CIOs, project managers and software engineers in industrial software development practice who want to learn how to effectively deal with the inevitable uncertainty of complex projects, who want to achieve higher levels of understanding and cooperation in their relationships with clients and contractors, and who want to run lower-risk software projects despite their inherent uncertainties. | ||
650 | 0 | _aComputer science. | |
650 | 0 | _aManagement information systems. | |
650 | 0 | _aSoftware engineering. | |
650 | 0 | _aComputers. | |
650 | 0 | _aLaw and legislation. | |
650 | 1 | 4 | _aComputer Science. |
650 | 2 | 4 | _aSoftware Engineering. |
650 | 2 | 4 | _aManagement of Computing and Information Systems. |
650 | 2 | 4 | _aSoftware Management. |
650 | 2 | 4 | _aLegal Aspects of Computing. |
700 | 1 |
_aGruhn, Volker. _eauthor. |
|
700 | 1 |
_aStriemer, R�udiger. _eauthor. |
|
710 | 2 | _aSpringerLink (Online service) | |
773 | 0 | _tSpringer eBooks | |
776 | 0 | 8 |
_iPrinted edition: _z9783319414768 |
856 | 4 | 0 | _uhttp://dx.doi.org/10.1007/978-3-319-41478-2 |
912 | _aZDB-2-SCS | ||
942 | _cEBK | ||
999 |
_c52843 _d52843 |