Stober / Hansmann Agile Software Development

Best Practices for Large Software Development Projects
1. Auflage 2009
ISBN: 978-3-540-70832-2
Verlag: Springer Berlin Heidelberg
Format: PDF
Kopierschutz: 1 - PDF Watermark

E-Book, Englisch, 179 Seiten

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.

Autoren/Hrsg.

Stober, Thomas

Hansmann, Uwe

Inhaltsverzeichnis

1;176104_1_En_FM1_OnlinePDF.pdf;2
2;176104_1_En_1_Chapter_OnlinePDF.pdf;19
2.1;Chapter Chapter 1: The Flaw in the Plan;19
2.1.1;The Delusive Perception of Having Anticipated Everything;19
2.1.2;Accept the Uncertainty and Adapt;23
2.1.3;Involving the Teams;26
2.1.4;In Search of Structure;26
2.1.5;Agile Software Development;30
2.1.6;Further Readings;32
3;176104_1_En_2_Chapter_OnlinePDF.pdf;33
3.1;Chapter Chapter 2: Traditional Software Development;33
3.1.1;History of Project Management;33
3.1.2;Waterfall ApproachWaterfall approach;34
3.1.2.1;Requirements;35
3.1.2.2;Design PhaseDesign phase;36
3.1.2.2.1;Use Cases;36
3.1.2.2.2;UML;39
3.1.2.2.3;Flowcharts;40
3.1.2.3;Implementation;41
3.1.2.4;Testing;41
3.1.2.4.1;Development Test Ratio;42
3.1.2.4.2;Planning and Tracking Test Progress;44
3.1.2.5;Support;45
3.1.2.6;Advantages and Disadvantages;45
3.1.3;Project Management Triangle;46
3.1.4;Modified Waterfall Models;48
3.1.4.1;Milestones and Regular Integration;48
3.1.4.2;Incremental Development;49
3.1.5;Further Readings;50
4;176104_1_En_3_Chapter_OnlinePDF.pdf;52
4.1;Chapter Chapter 3: Overview of Agile Software Development;52
4.1.1;Lean Software Development;54
4.1.2;Project Management 2.0;57
4.1.3;Agile Manifesto;57
4.1.4;Scrum;58
4.1.5;Test Driven Development;64
4.1.6;Extreme Programming;65
4.1.7;Rational Unified Process;69
4.1.7.1;Best Practices;69
4.1.7.2;The Phases;70
4.1.7.3;The Process;71
4.1.7.3.1;Core Workflows;71
4.1.8;Agile Unified Process;73
4.1.9;Agile Model Driven Development;74
4.1.10;Further Readings;75
5;176104_1_En_4_Chapter_OnlinePDF.pdf;77
5.1;Chapter Chapter 4: Tooling;77
5.1.1;Project Management Tools;77
5.1.1.1;Microsoft Solutions Framework for Agile Development;78
5.1.1.2;Jazz and Rational Team Concert (RTC);79
5.1.2;Collaboration Tools;82
5.1.3;Development Infrastructure and Environment;83
5.1.3.1;Source Control and Version Management;84
5.1.3.1.1;Build Infrastructure;84
5.1.3.2;Automated Test Environment;86
5.1.3.3;``Code-Build-Test´´;87
5.1.4;Further Readings;89
6;176104_1_En_5_Chapter_OnlinePDF.pdf;90
6.1;Chapter Chapter 5: Considerations on Teaming and Leadership;90
6.1.1;A ``Lean´´ Hierarchy;90
6.1.2;Setting the Directions: Management by ObjectivesManagement by objectives;93
6.1.3;Defining the Goals;95
6.1.4;About Trust and Thrust: Culture and Climate;97
6.1.5;Cross-functional TeamsCross-functional teams;98
6.1.6;The Wisdom of CrowdsWisdom of crowds;100
6.1.7;It Isn´t that Easy;102
6.1.8;Skills;106
6.1.9;Further Readings;107
7;176104_1_En_6_Chapter_OnlinePDF.pdf;108
7.1;Chapter Chapter 6: Considerations on Planning and Architecture;108
7.1.1;About RequirementsRequirement, Resources, and Dates;108
7.1.2;Agile, a License for Chaos?;108
7.1.3;Balance Flexibility and Structure;110
7.1.3.1;Balance the Level of DetailError! Bookmark not defined;110
7.1.3.2;Balance the Timing of Decisions;112
7.1.3.3;Balance the Need for Commitment;113
7.1.3.4;Balance Between Autonomy and Guidance;114
7.1.3.5;Balance the Amount of Documentation;115
7.1.3.6;Disciplined Agile;116
7.1.4;Reducing Complexity;116
7.1.4.1;Simplify Prioritization and Planning;117
7.1.4.2;Simplify Team Setup and Dependencies;118
7.1.4.3;Simplify Tools and Processes;119
7.1.4.4;Simplify Daily Life;120
7.1.5;Architectural Considerations;121
7.1.5.1;Outside-In Design;121
7.1.5.2;Requirements, Use Cases, Scenarios, and Tasks;122
7.1.5.3;Architectural Attitude;124
7.1.5.4;Making Architecture Flexible;127
7.1.6;Further Readings;129
8;176104_1_En_7_Chapter_OnlinePDF.pdf;130
8.1;Chapter Chapter 7: Considerations on Project Execution;130
8.1.1;The Big Bang;130
8.1.2;Continuous Integration;131
8.1.3;The Rhythm of the Project: Iterations;133
8.1.4;Integration Fest;136
8.1.5;Juggling Content Within an Iteration;137
8.1.6;Planning in an Agile Project;141
8.1.7;Estimating;143
8.1.7.1;Units often used in Agile Projects;145
8.1.7.2;Ways to get to Estimates;148
8.1.8;Metrics for an Agile Project;150
8.1.9;Defects;153
8.1.10;Independent Release Testing and Wrap-up;155
8.1.11;Involving Customers;157
9;176104_1_En_8_Chapter_OnlinePDF.pdf;160
9.1;Chapter Chapter 8: Mix and Match;160
9.1.1;The Tragedy of Being Successful;160
9.1.2;About WebSphere Portal;161
9.1.3;Which Projects are suitable for Agile Software Development?;163
9.1.4;Scaling Agile;164
9.1.5;Moving Towards Agile;165
9.1.6;Tiger Teams in WebSphere Portal;168
9.1.6.1;Budget-based Prioritization;168
9.1.6.2;Cross-Organizational Teaming Structure;170
9.1.6.3;Evolving the Product in Iterations;172
9.1.6.4;Integrating Test and Development;176
9.1.6.5;Designs and Documentation;179
9.1.6.6;Managing Tiger Teams;180
9.1.7;The Benefits and Pain Points;183
10;176104_1_En_9_Chapter_OnlinePDF.pdf;186
10.1;Chapter Chapter 9: Summary and Wrap-Up;186
10.1.1;The Essence of Agile;186
10.1.2;Building an Agile Community;188
10.1.3;Comparing once again;188
11;176104_1_En_BM2_OnlinePDF.pdf;191
11.1;: Index;191