This video describes the continuous integration system built to help manage testing automation at Google. Continuous integration systems play a crucial role in modern software development practices, keeping software working while it is being developed.

Everyone draws inspiration and motivation for software development from different sources. For most, it’s often frustration. We make life decisions, define new features, or refactor code when we get too annoyed by current circumstances. This is where I admit that I have a low tolerance for frustration. Having been frustrated a great deal during my career, I’m going to discuss several anti-patterns that I’ve seen in code and how to use the Dark Side of the Force (frustration, anger, and rage) to escape from them.

At the Forward Internet Group in London, we are implementing a more extreme version of Agile that is consistent with the Lean Startup movement. In essence, the business has empowered the developers to do what they think is right for the business. We have watched well-defined Agile roles evaporate completely as other environmental factors are applied. Finally, we have arrived at Programmer Anarchy, an organization often following none of the standard Agile practices, having no BA or QA roles, and even missing any managers of programmers, yet still conforms to …

The software development industry isn’t delivering software successfully! So what’s really going on? Well, things such as agile and software craftsmanship certainly take you down some dangerous paths, and don’t even get them started on Java 7!

Craig Larman author of “Scaling Lean & Agile Development: Thinking & Organizational Tools” and “Practices for Scaling Lean & Agile Development: Successful Large, Multisite & Offshore Products with Large-Scale Scrum” discusses large-scale Scrum for large, multisite, and/or offshore product development.

his video demos how to quickly get to a fully agile project setup with continuous deployment. Everything is in the cloud – GIT repo, Jenkins, MongoDB and the app server. The system deploys automatically with every successful commit. The app itself is minimal, but does have a simple web interface and a database. The idea is that once you get this “walking skeleton” type app running in the cloud with continuous deployment, you can get user feedback early and often, and evolve more quickly.

Agile software development was born ten years ago, with a gathering of industry luminaries in Snowbird, Utah. They were frustrated that so much ceremony and effort was going into so little success, in failed project after failed project, across the software industry.

This short tutorial explains the Scrum Artifacts associated with Scrum Development, including User Story, Product Backlog, Sprint Backlog and Progress Charts.

I’ve wondered for some time whether much of Agile’s success was the result of the placebo effect, that is, good things happened because we believed they would. The placebo effect is a startling reminder of the power our minds have over our perceived reality. Now cognitive scientists tell us that this is only a small part of what our minds can do. Research has identified what I like to call “an agile mindset”, an attitude that equates failure and problems with opportunities for learning, a belief that we can all …

Most software architecture efforts have a strong waterfall nature to them. Software architects create an end-state vision with a multi-year plan to achieve it. Of course, the business and technological contexts both change long before that can be achieved. The result is a series of half-finished, very expensive, enterprise architecture initiatives. Instead, we should create architecture that is specifically optimized for change, with principles about where to place certain decisions and how to adapt over time.