When you look around, there are a lot of leaders recommended for software development. We have the functional manager and the project manager, the scrum master and the black belt, the product owner and the customer-on-site, the technical leader and the architect, the product manager and the chief engineer. Clearly …
In this interview from OSCON 2008, authors Shane Warden and Jim Shore describe what agile programming is and why it makes projects succeed. [youtube bfmLsQq6OUU]
A small presentation that explains the reason why Agile Software Development projects make economical sense. [youtube OWvSnYjqOTQ]
Five Guidelines for Writing Need Statements. User Requirements usually are just raw data that describes a symptom or a limited solution. As an agile practitioner, I want to present “translation” guidelines for user requirements so that they can give more value to a final product. Watch this video on confreaks.com …
All tests automation systems have certain common tasks. Different tools tend to focus on some tasks and put less emphasis on other tasks. While examining 11 home-grown test automation tools at F5, we found certain patterns. There were six different tasks that all tools addressed to varying degrees. We found …
Continuous Integration (CI) is a software development practice where members of a team integrate their work frequently. Usually each person integrates at least daily leading to multiple integrations per day. When integration is verified by an automated build (including test) the gross and obvious integration errors are detected as quickly …
