Agile development and business goals the six week solution
Agile Development and Business Goals describes a unique, state-of-the-art methodology that aligns the critical but often ""silo-ed"" software development process with core company goals. Eschewing long-winded ""agile philosophy"" in favor of a formally priorit...
| Autor principal: | |
|---|---|
| Formato: | Libro electrónico |
| Idioma: | Inglés |
| Publicado: |
Burlington, MA :
Morgan Kaufmann Publishers
c2010.
|
| Edición: | 1st edition |
| Materias: | |
| Ver en Biblioteca Universitat Ramon Llull: | https://discovery.url.edu/permalink/34CSUC_URL/1im36ta/alma991009627816906719 |
Tabla de Contenidos:
- Front cover; Agile Development &Business Goals: The Six Week Solution; Copyright page; Dedication page; Brief Table of Contents; Complete Contents; Who is This Book Written For?; Chapter Summary; Acknowledgments; Chapter 1: Introduction: Ask Yourself These 10 Key Questions; Introduction; Ten Questions to Ask About your Software Development Process; Why Listen to Us?; Chapter 2: The Problem: Why SoftwareProjects Fail; Introduction; Historical Perspective; The Scope of Software; Software Development Often Fails; The Need for Process; A Common Question; Software Development is Hard-Very Hard
- Why Other Agile Methodologies Often FailWhy Waterfall Processes Often Fail; High Visibility; Death March; Man in a Room; The Rogue Developer; ""Are you Done Yet?""; Budget Black Hole; Why the Six Week Solution is Different; Chapter 3: Expectations: What It Meansfor Software to Succeed; Introduction; Software Development Sometimes (Accidentally) Succeeds; Is Aligned With Business Needs; Manages the Cost of Change; Is Built in an Automated Way; Factors Quality Into the Core of the Process; Is Not Constantly Being Redeployed; Progress is Constantly Being Made; Delivers Something of Value
- Is EvangelicalIs Predictable; Is both Tactical and Strategic; Is Game Changing; Allows Management to Stay Informed; Is Measurable; Chapter 4: Overview of the Six Week Solution; Introduction; Additional Problems; Components of Agile Alignment; Why Six Weeks?; Cycle Commitments; Developer Compensation: Cod; Six Week Iterations; Time Boxing Development: Key Deadlines; Week 1: Cycle Kickoff; Week 3: Mea Culpa; Week 6: Testing; Steering With Business Goals; Chapter 5: The Solution's Critical Pieces; Introduction; The Big Game; The Entire Company Must Buy In; Work Space; Personnel Roles
- Hiring SmartCompensation; Development Tools; Cycle Commitments; Chapter 6: Managing the Cost of Change; Introduction; Flattening the Curve With Feedback Loops; Avoiding the Curve By Managing the Unknown; Lowering the Curve By Increasing Productivity; Providing Effective Tools; Languages and Tooling; Buy, Don't Build; Effective Communication; Gauging Performance With Pairs; Chapter 7: Assuring Software Quality; Introduction; The Value of Quality; External Software Quality; Internal Software Quality; Symptoms of Design Rot; Quality and Software Craftsmanship; Size of Work Pieces; Unit Testing
- Chapter 8: Integrating Automation Into your Development ProcessIntroduction; Continuous Integration; Build Process; Metrics; Automation Tools; Chapter 9: Other Software Development Approaches; Introduction; Simplified Evolution of Software Processes; Chapter 10: Risks With Using This Approach; Introduction; Workplace Challenges; Work Environment; Why This is Not a Risk; Risk: Abandoning Quality for Bonuses; Management Challenges; Quality Concerns; Design Debt; Hard to Transition; Smaller but Still Potentially Problematic Risks; Chapter 11: Transitioning to the Six Week Solution; Introduction
- Before you Do Anything, Though
