Why We Need Architects and Architecture on Agile Projects

Why We Need Architects and Architecture on Agile Projects

ChariotSolutions via YouTube Direct link

Experiment on Branches

16 of 35

16 of 35

Experiment on Branches

Class Central Classrooms beta

YouTube videos curated by Class Central.

Classroom Contents

Why We Need Architects and Architecture on Agile Projects

Automatically move to the next video in the Classroom when playback concludes

  1. 1 Intro
  2. 2 Why We Need Architects (and Architecture) on Agile Projects
  3. 3 Three Questions...
  4. 4 Astronaut Architect?
  5. 5 Seagull Architect?
  6. 6 Incompetent Fools?
  7. 7 Agile Design Values
  8. 8 Some Agile Myths
  9. 9 Steward Architect
  10. 10 Stewardship
  11. 11 How Much Architecting Do You Need? Project Criticality
  12. 12 Qualities of Any Good Architecture
  13. 13 Small v. Large Projects
  14. 14 Small Project Architecture Practices
  15. 15 Design "Spikes"
  16. 16 Experiment on Branches
  17. 17 Manage Technical Debt
  18. 18 Keep Architecture in Mind
  19. 19 Sustainable Development
  20. 20 Strike a Balance
  21. 21 Types of Project Risks
  22. 22 Architecture Debt
  23. 23 Product Landing Zones
  24. 24 Good Acceptance Criteria
  25. 25 What's Different?
  26. 26 Landing Zones on Agile Projects
  27. 27 Architecture Spikes
  28. 28 XP Design Spike
  29. 29 What You Do In an Architecture Spike
  30. 30 Criteria for an Architecture Spike: Actionable Results
  31. 31 3 Ways To Manage Architectural Tasks
  32. 32 What Can Go On An Architecture Backlog?
  33. 33 The Agile Architecture Landscape
  34. 34 Differences Between Agile and Traditional Architecture
  35. 35 Values Important to Agile Architects

Never Stop Learning.

Get personalized course recommendations, track subjects and courses with reminders, and more.

Someone learning on their laptop while sitting on the floor.