|
|
|
|
| LEADER |
02945nam a22005055i 4500 |
| 001 |
978-3-540-70832-2 |
| 003 |
DE-He213 |
| 005 |
20151204170454.0 |
| 007 |
cr nn 008mamaa |
| 008 |
100301s2010 gw | s |||| 0|eng d |
| 020 |
|
|
|a 9783540708322
|9 978-3-540-70832-2
|
| 024 |
7 |
|
|a 10.1007/978-3-540-70832-2
|2 doi
|
| 040 |
|
|
|d GrThAP
|
| 050 |
|
4 |
|a QA76.758
|
| 072 |
|
7 |
|a UMZ
|2 bicssc
|
| 072 |
|
7 |
|a COM051230
|2 bisacsh
|
| 082 |
0 |
4 |
|a 005.1
|2 23
|
| 100 |
1 |
|
|a Stober, Thomas.
|e author.
|
| 245 |
1 |
0 |
|a Agile Software Development
|h [electronic resource] :
|b Best Practices for Large Software Development Projects /
|c by Thomas Stober, Uwe Hansmann.
|
| 264 |
|
1 |
|a Berlin, Heidelberg :
|b Springer Berlin Heidelberg,
|c 2010.
|
| 300 |
|
|
|a XXIII, 179 p.
|b online resource.
|
| 336 |
|
|
|a text
|b txt
|2 rdacontent
|
| 337 |
|
|
|a computer
|b c
|2 rdamedia
|
| 338 |
|
|
|a online resource
|b cr
|2 rdacarrier
|
| 347 |
|
|
|a text file
|b PDF
|2 rda
|
| 505 |
0 |
|
|a The Flaw in the Plan -- Traditional Software Development -- Overview of Agile Software Development -- Tooling -- Considerations on Teaming and Leadership -- Considerations on Planning and Architecture -- Considerations on Project Execution -- Mix and Match -- Summary and Wrap-Up.
|
| 520 |
|
|
|a Software Development is moving towards a more agile and more flexible approach. It turns out that the traditional "waterfall" model is not supportive in an environment where technical, financial and strategic constraints are changing almost every day. But what is agility? What are today’s major approaches? And especially: What is the impact of agile development principles on the development teams, on project management and on software architects? How can large enterprises become more agile and improve their business processes, which have been existing since many, many years? What are the limitations of Agility? And what is the right balance between reliable structures and flexibility? This book will give answers to these questions. A strong emphasis will be on real life project examples, which describe how development teams have moved from a waterfall model towards an Agile Software Development approach.
|
| 650 |
|
0 |
|a Computer science.
|
| 650 |
|
0 |
|a Input-output equipment (Computers).
|
| 650 |
|
0 |
|a Computer communication systems.
|
| 650 |
|
0 |
|a Software engineering.
|
| 650 |
|
0 |
|a Complexity, Computational.
|
| 650 |
1 |
4 |
|a Computer Science.
|
| 650 |
2 |
4 |
|a Software Engineering.
|
| 650 |
2 |
4 |
|a Computer Communication Networks.
|
| 650 |
2 |
4 |
|a Input/Output and Data Communications.
|
| 650 |
2 |
4 |
|a Information Systems Applications (incl. Internet).
|
| 650 |
2 |
4 |
|a Complexity.
|
| 700 |
1 |
|
|a Hansmann, Uwe.
|e author.
|
| 710 |
2 |
|
|a SpringerLink (Online service)
|
| 773 |
0 |
|
|t Springer eBooks
|
| 776 |
0 |
8 |
|i Printed edition:
|z 9783540708308
|
| 856 |
4 |
0 |
|u http://dx.doi.org/10.1007/978-3-540-70832-2
|z Full Text via HEAL-Link
|
| 912 |
|
|
|a ZDB-2-SCS
|
| 950 |
|
|
|a Computer Science (Springer-11645)
|
