Many people who explain agile software development often discuss project and planning practices, but hardly mention the development phase—as if actual development were an afterthought. In this insightful video, renowned software architect Neal Ford drills into the real details of agile engineering practices from a pure development perspective, based on work that he and others have done in the field.
Which development and design practices make the agile approach work? What are the pros and cons of feedback mechanisms? How do you test the entire stack? This video explores those questions and a host of related topics in depth.
- Learn best practices such as continuous integration, pair programming, and continuous delivery
- Discover how to interact with story cards and agile estimation
- Handle enterprise concerns like integration with other software packages
- Explore different version control strategies
- Delve into real-world problems, like convincing management that agile development is the way to go
- Evaluate the results of your development efforts
Project managers, business analysts, developers, and anyone else interested in the engineering practices common in Agile software development. This material discusses agile development and testing in both the concrete and abstract, covering both how and why things work on agile projects. Anyone interested in the mechanics of how to build software will find interesting food for thought.
About the O’Reilly Software Architecture Series
- Why does agile software development work?
- Pair programming
- Continuous integration and deployment
- Version control strategies
- Testing the entire stack
- Design practices
- Emergent Design
- Evolutionary architecture
Clearing a path from developer to architect and enriching that path once you arrive. Software architecture is a massive multidisciplinary subject, covering many roles and responsibilities, and it is a fast-moving discipline where entire suites of “best practices” become obsolete practically overnight—yesterday’s best practice is tomorrow’s anti-pattern. No single path or curriculum exists; different types of architecture—application, integration, enterprise—require different subject emphasis. And yet, year after year, the job “software architect” places in the top ten of most Best Jobs surveys.
Keeping up with new approaches is challenging because you must maintain both technical depth and breadth. Whether you are at the outset of a career as an architect or in the midst of such a career, the O’Reilly Software Architecture series brings together a rich variety of topics, deep dives, innovative thinking, practical tips, and unfettered access to expert know-how that you can incorporate into a path that makes sense for you.