Great Big Agile An OS for Agile Leaders /

• Κύριος συγγραφέας: Dalton, Jeff (Συγγραφέας, http://id.loc.gov/vocabulary/relators/aut)
• Συγγραφή απο Οργανισμό/Αρχή: SpringerLink (Online service)
• Μορφή: Ηλεκτρονική πηγή Ηλ. βιβλίο
• Γλώσσα: English
• Έκδοση: Berkeley, CA : Apress : Imprint: Apress, 2019.
• Έκδοση: 1st ed. 2019.
• Θέματα: Software engineering.; Project management.; Software Engineering.; Project Management.

Big Agile leaders need an empirical, "high-trust" model that provides guidance for scaling and sustaining agility and capability throughout a modern technology organization. This book presents the Agile Performance Holarchy (APH)-a "how-ability" model that provides agile leaders...

Πίνακας περιεχομένων:

• Part 1: The Agile Performance Holarchy
• Chapter 1: The API Is Broken
• Part 2: The Performance Circles
• Chapter 2: Performance Circle: Leading
• Chapter 3: Performance Circle: Providing
• Chapter 4: Performance Circle: Envisioning
• Chapter 5: Performance Circle: Crafting
• Chapter 6: Performance Circle: Affirming
• Chapter 7: Performance Circle: Teaming
• Part 3: Ceremonies and Techniques
• Chapter 8: Acceptance Testing
• Chapter 9: Agile Agreement
• Chapter 10: Agile Digs
• Chapter 11: Agile Partner Assessment
• Chapter 12: All Hands Raised
• Chapter 13: Arc of Conversation
• Chapter 14: Automated Build
• Chapter 15: Backlog Grooming
• Chapter 16: Best Practices Board
• Chapter 17: Big Room Planning / Release Zero
• Chapter 18: Brainstorming
• Chapter 19: Burn Down Chart
• Chapter 20: Confirmation
• Chapter 21: Continuous Deployment
• Chapter 22: Continuous Integration
• Chapter 23: Class, Responsibilities, Collaborators (CRC) Cards
• Chapter 24: Daily Stand-Up
• Chapter 25: Definition of Done
• Chapter 26: Definition of Ready
• Chapter 27: Dot Voting
• Chapter 28: Epics
• Chapter 29: Evaluation
• Chapter 30: Frequent Releases
• Chapter 31: Gemba Walks
• Chapter 32: Gemba Kaizen
• Chapter 33: Goal, Question, Metric (GQM)
• Chapter 34: Incremental Development
• Chapter 35: Kamishibai (Board and Cards)
• Chapter 36: Kanban Board
• Chapter 37: Kano Model
• Chapter 38: Lean Coffee
• Chapter 39: Mob Programming
• Chapter 40: Obeya Room
• Chapter 41: Open Space Technology
• Chapter 42: Pair Programming
• Chapter 43: Peer Reviews
• Chapter 44: Planning Poker
• Chapter 45: Product Backlogs
• Chapter 46: Product Scenarios
• Chapter 47: Project (Team) Chartering
• Chapter 48: Prototyping/Spike
• Chapter 49: Release Planning
• Chapter 50: Retrospectives
• Chapter 51: Review
• Chapter 52: Roles and Accountabilities Game
• Chapter 53: Scrum of Scrums
• Chapter 54: Scrum Wall / Scrum Board
• Chapter 55: Self-Selection/Self-Subscription
• Chapter 56: Spike (Design Spike)
• Chapter 57: Sprint
• Chapter 58: Sprint Demo
• Chapter 59: Sprint Planning
• Chapter 60: Stakeholder Identification and Management
• Chapter 61: State of the Team
• Chapter 62: SWOT Analysis (Strengths, Weaknesses, Opportunities, Threats)
• Chapter 63: Team Agreement
• Chapter 64: Team Estimation Game
• Chapter 65: Team Room Set-Up
• Chapter 66: Technical Debt
• Chapter 67: Test-Driven Development
• Chapter 68: Three Diverse Humans
• Chapter 69: Training
• Chapter 70: Unit Testing
• Chapter 71: Velocity
• Chapter 72: Visual Information Management
• Part 4: Next Steps for Leaders
• Chapter 73: Using the Agile Performance Holarchy
• Appendix A: Quick Reference Tables
• Glossary.-.