Agile Software Development in the Large
Agile Software Development in the Large
Diving into the Deep
About the Book
Agile processes have revolutionized the software development industry. They're faster and more efficient than traditional software development processes. They enable developers to embrace requirement changes during the project, deliver working software in frequent iterations, and focus on the human factor in software development. Unfortunately, agile processes are either designed for small or mid-sized software development teams or rigid frameworks are provided for large-sized teams. Yet, also large teams have to deal with rapid changes - so rigidity is not helpful for them!
With Agile Software Development in the Large, Jutta Eckstein--a leading speaker and consultant in the agile community--shows how to scale agile processes to teams of 1 to 300. In fact, the same techniques are also relevant to teams of ten or more developers, especially within large organizations.
Topics include:
- the agile value system as used in large teams
- the impact of a switch to agile processes
- the agile coordination of several sub-teams
- the way project size and team size influence the underlying architecture
Stop getting frustrated with inflexible processes that cripple your large endeavors! Use this book to harness the efficiency and adaptability of agile software development.
About the Author
Bundles that include this book
Reader Testimonials
Ken Schwaber, Co-developer of Scrum
From the founder and director of the Agile Alliance, the Scrum Alliance, and Scrum.org.
Jutta is a highly regarded professional whom I know personally and professionally. ... She is what I regard as a thought leader in agile processes and patterns. As such, she hs a lot to say and the industry will be the better for her guidance and advice.
James Noble, Coauthor of Small Memory Software
From the Victoria University of Wellington: This is the first book addressing large projects
The major strengths of this book are the topic area - of growing importance to both practitioners and educators world-wide- and the down-to-earth, pragmatic tone in the writing. Other XP books address small projects in idealized, greenfield environments: This book is the first I am aware of addressing large projects within more traditional environments.
Diana Larsen, Co-Author of Agile Retrospectives: Making Good Teams Great & Liftoff: Start and Sustain Successful Agile Teams
Best Description of Agile SD approaches
I am crazy about this book. I think it's the best, most readable and understandable explanation I've read about using Agile software development approaches. It's message is accessible to both technical and non-technical readers. The practices are described in a way that works, whether in large, scaled-up environments or small, intimate ones. Since it became available, I have been telling my non-Agile and toe-in-the-Agile-water clients and colleagues about it every chance I get.
Table of Contents
- Acknowledgments
-
1. Introduction
- 1.1 Questioning Scaling Agile Processes
- 1.2 Examining Largeness
- 1.3 Raising Large Issues
- 1.4 Specifying the Projects in Focus
- 1.5 Detecting the Agile Method for Scaling
- 1.6 Identifying the Reader
- 1.7 Revealing the Structure of the Book
-
2. Agility and Largeness
-
2.1 Fundamentals of Agile Processes
- The Agile Manifesto
- Agile Methods Considering Largeness
- 2.2 Agile Principles Under a Large Magnifier
- 2.3 Cloak Agile Process
-
2.4 People Shape the Process
- Culture of Change
- Adaptation
- Communication
-
2.5 Mistrust in Applicability
- Documentation
- Design
- Testing
- Refactoring
- 2.6 Summary
-
2.1 Fundamentals of Agile Processes
-
3. Dealing with Large Teams
-
3.1 People
- Responsibility
- Respect and Acceptance
- Trust
-
3.2 Team Building
- Building Teams and Subteams
- Team Roles
- Team Jelling
-
3.3 Interaction and Communication Structures
- Open-plan Office
- Flexible Workplace
- Encouraging Communication
- Communication Team
- 3.4 Trouble shooting
-
3.5 Virtual Teams
- Distributed Teams
- Open Source
- 3.6 Summary
-
3.1 People
-
4. Dealing with the Process
- 4.1 Defining the Objectives
- 4.2 Providing Feedback
- 4.3 Short Development Cycles, Iterations, and Time-boxing
-
4.4 Planning
- Result-Oriented Planning
- Planning Tools
-
4.5 Integration
- Integration Strategy
- Integration Team
- Tools for Configuration Management and Version Control
-
4.6 Retrospectives
- Attendance
- Techniques
-
4.7 Getting Started with an Agile Process
- Learn from History
- Start Small
- Finalizing the Architecture
- Grow Slowly
-
4.8 Culture of Change
- Learn and Change Processes
- Introducing Change
- Force Courage
- 4.9 Summary
-
5. Dealing with the Technology
-
5.1 Architect and Architecture
- Architectural Lead
- Simple Architecture
- Architecture as a Service
- 5.2 Avoid Bottlenecks
- 5.3 Ownership
- 5.4 Choosing Technology
-
5.5 Techniques and Good Practices
- Testing
- Refactoring
- Standards
- 5.6 Summary
-
5.1 Architect and Architecture
-
6. Dealing with the Company
- 6.1 Communication and Organization Structure
-
6.2 Project Planning and Controlling
- Planning
- Controlling
- Fixed-price Projects
-
6.3 Enterprise-wide Processes
- Process and Methodology Department
- Enterprise-wide Processes
- Certification and Adaptation of a Process
- 6.4 Enterprise-wide Tools and Technology
- 6.5 Quality Assurance and Quality Control
-
6.6 Departments on the Edge
- Human Resources
- Legal Department
- Marketing
- Production
-
6.7 The Customer
- The Role of the Customer
- Integrating the Customer
-
6.8 Company Culture shapes Individuals
- Skills
- Providing Training
- Establishing a Learning Environment
-
6.9 Resources
- Insourcing
- Outsourcing
- Full-Time and Part-Time Project Members
- 6.10 Summary
-
7. Putting it all together: A Project Report
- 7.1 The previous History
- 7.2 The Customer
- 7.3 The Team
-
7.4 Organizational Departments
- Process and Methodology
- Tools and Technology
- Quality Control and Assurance
- Project Planning and Controlling
- 7.5 Starting Off
-
7.6 Growing the Team
- Learning from Previous Problems
- Training
- Establishing Short Iterations
- Learning to Reflect
- Enabling Communication
- Dealing with Outsourced Teams
- 7.7 Unresolved Issues
- 7.8 Summary
- 8. Afterthoughts
-
Bibliography
- Books
- URLs
- About Jutta Eckstein
- Other Books by the Author
- Notes
Other books by this author
The Leanpub 60 Day 100% Happiness Guarantee
Within 60 days of purchase you can get a 100% refund on any Leanpub purchase, in two clicks.
Now, this is technically risky for us, since you'll have the book or course files either way. But we're so confident in our products and services, and in our authors and readers, that we're happy to offer a full money back guarantee for everything we sell.
You can only find out how good something is by trying it, and because of our 100% money back guarantee there's literally no risk to do so!
So, there's no reason not to click the Add to Cart button, is there?
See full terms...
80% Royalties. Earn $16 on a $20 book.
We pay 80% royalties. That's not a typo: you earn $16 on a $20 sale. If we sell 5000 non-refunded copies of your book or course for $20, you'll earn $80,000.
(Yes, some authors have already earned much more than that on Leanpub.)
In fact, authors have earnedover $12 millionwriting, publishing and selling on Leanpub.
Learn more about writing on Leanpub
Free Updates. DRM Free.
If you buy a Leanpub book, you get free updates for as long as the author updates the book! Many authors use Leanpub to publish their books in-progress, while they are writing them. All readers get free updates, regardless of when they bought the book or how much they paid (including free).
Most Leanpub books are available in PDF (for computers) and EPUB (for phones, tablets and Kindle). The formats that a book includes are shown at the top right corner of this page.
Finally, Leanpub books don't have any DRM copy-protection nonsense, so you can easily read them on any supported device.
Learn more about Leanpub's ebook formats and where to read them
