The Agile codex re-inventing Agile through the science of invention and assembly
| Otros Autores: | |
|---|---|
| Formato: | Libro electrónico |
| Idioma: | Inglés |
| Publicado: |
New York, NY :
Apress L. P.
[2021]
|
| Materias: | |
| Ver en Biblioteca Universitat Ramon Llull: | https://discovery.url.edu/permalink/34CSUC_URL/1im36ta/alma991009633578906719 |
Tabla de Contenidos:
- Intro
- Contents
- About the Author
- Part I: The Accident
- Chapter 1: Clear Ownership
- Daily Standup Day 1: Who's on first?
- Shared Lists
- Ownership
- Untangling
- Chapter 2: Small, Independent Units of Work
- Daily Standup Day 2: Merge conflicts!
- Daily Standup Day 3: Need a reviewer!
- Daily Standup Day 4: I broke some stuff. I think.
- Daily Standup Day 5: Turns out I need this other thing.
- Chapter 3: Sized
- Daily Standup Day 6: Five hours or five weeks…
- Chapter 4: Sequenced
- Daily Standup Day 7: …or five hours over five weeks?
- Chapter 5: Inputs, Transition Criteria, Outputs
- Daily Standup Day 8: Did you say something?
- Chapter 6: Stakeholder Approval
- Daily Standup Day 9: Oops. I forgot to tell you. Or ask you.
- Part II: The Agile Codex Theory
- Chapter 7: The Problem
- Plan for the Imperfect Plan
- Optimize for Adaptability
- Don't Surrender to Dependencies
- Chapter 8: The Codex
- The Principles of the Agile Codex
- Small Units of Work
- Sized
- Sequenceable
- Acyclic Dependency Tree
- Single Owner
- Application
- Chapter 9: The Agile
- Clear Ownership of Work at All Times in Each Stage
- Clear Inputs
- Clear Transition Criteria
- Clear Outputs
- Stakeholder Approval
- Chapter 10: Benefits
- Low Overhead
- Detailed Auditing
- Quick and Safe Deliveries
- Many Quality Gates
- Chapter 11: From Invention to Assembly Line
- The Importance of Dependencies
- Building the Assembly Line
- In Review
- Chapter 12: Team Functions
- User Experience (UX)
- Product Management (PM)
- Engineering Management (EM)
- Development (DEV)
- Quality Engineering (QE)
- Documentation (DOC)
- Operations (OPS)
- Customer Support Group (CSG)
- Chapter 13: Software Development Life Cycle
- Phases
- Planning
- Execution
- Releasing
- Choosing a Cadence
- How SDLC Length Affects Practices.
- Constructing the Codex
- Chapter 14: Risk Management
- Categories of Risk
- Product Risk: How Clearly and Comprehensively the Product Can Be Defined
- Technical Risk: How Clearly and Comprehensively It Is Understood How to Build It
- Market Risk: Any Demand-Side Shift Which Creates an Arbitrage Opportunity for a Quick Feature Pivot
- Business Risk: Any Supply-Side Shift Which Creates an Arbitrage Opportunity for a Quick Feature Pivot
- Today and Tomorrow Risk
- Positive Interactions with Risk
- Risk Quadrants and Risk over Time
- Planning for Resilience
- Conclusion
- Part III: The Agile Codex Practice
- Chapter 15: Building Blocks
- Planned Release
- Epic
- User Story
- Acceptance Criteria
- Tasks
- Dependencies
- Adjacent Teams
- Story Points
- Bug
- All Together
- Chapter 16: Workflow
- Planning
- Release Planning
- Epic Grooming
- User Story Grooming
- Epic Commitment
- Execution
- Setting Up the Tree
- The Board
- Needs Sign-Off
- Signed Off
- In Progress
- Fix Needed
- QE
- PM / UX
- Closed
- External Dependencies
- The Sprint or the Kanban
- Adjusting
- Releasing
- Feature Complete
- QE Complete
- The Terminal Sprint
- Chapter 17: Metrics
- Predicting
- Analyzing
- Adjusting
- Opportunistic and Non-Epic Work
- Multi-release Epics
- Chapter 18: Teaching the Teams
- From Agile to Agile Codex
- Agiling Well with Others When They Don't Agile As Well
- Chapter 19: What Next?
- Tooling
- Synchronization Gap
- Heuristics
- Who Can Do What
- Risk Ranking
- How Perfect Is Perfect Enough?
- Who Is Available, How Much, and When?
- Dials and Knobs for Scenario Planning
- Make It Easy to Visualize
- Reporting
- Conclusion
- Index.
