Agile has been growing as a movement for much of this decade. And what started near 2009 with a few organizations rocking the process boat has become a tidal wave of support, interest, and work towards Agile methods of software. Often forgotten in that mix is that, Agile, when founded in 2001, was understood to be a dramatically different way for software developers to create software, and not just a different method to do project management. There are differences in how developers write code on a minute-by-minute basis, differences in team composition, differences in how code is tested, differences in the build process, and differences in governance, or even the type of governance for software projects.
While most of us have begun to participate in the groundswell of Agile, how many of us have gone back to the Agile basics, and changed how code is written, what testing means in our organization, and shrunk the acceptable lead time in moving new releases to production from months to minutes? To do Agile and to sustain agile, we must make not only process, team, and product changes, but we must also make changes to our test processes, our build process, and our development processes. Otherwise, the speed of agile process and product work will founder on the insufficient speed of our technical technique.
This course outlines what a modern Agile technical process looks like. What’s the development approach, what’s the testing approach, and what’s the outline of the build approach (that’s a separate class)?
- Agile refresher
- Agile engineering introduction
- Agile engineering topics
- Unit Testing
- Test Driven Development ( TDD )
- Agile build introduction
- Agile testing introduction
- Agile testing topics
- Static Code Analysis
- Test testing
- Automated web testing
- Automated service testing
- Behavior Driven Development (BDD)
- Additional automated testing topics