Early results of a study on the effects of agile development practices are showing improvements in productivity and quality. These results aim to answer questions on development projects schedules and budgets. They also provide insight in the results of outsourcing and co-located teams.
Tobias Mayer started Business Craftsmanship: an organizational development and transformation approach to teach and apply ideas from Agile software development to any knowledge work context. Several posts have been published, for example about “Core Values” and “In Praise of Processes”.
There have been numerous attempts over the years to determine the best way to measure the effectiveness of an Agile adoption. Some recent articles have reignited the debate around the most useful metrics.
During his talk at DevOps Days in Gothenburg Mitchell Hashimoto, co-author of Vagrant and system admin at Kiip, proposed an experience-based roadmap for moving organizations from a traditional black box ops culture to an (ideal) white box culture where developers are free to change the production environment.
Most new Agile teams transition from hours based estimates to relative estimation using story points, but do we even need estimates at all?
Facebook is probably the hottest company today, driving a very high level of interest and scrutiny. Despite a high level of secrecy, Yee Lee, a product manager at Skype, has assembled a large collection of notes detailing how code ships at Facebook.
Agile development model has spawned a lot of interest, conferences, books across the entire software development community. The paradigm of effective software development has taken a shift in the right direction. One area which still needs some refactoring is the best way to hire for an Agile team.
Tom Hollander, a Solutions Architect at Microsoft Australia, held a presentation entitled The Role of an Architect in an Agile Team at TechEd Australia where he discussed what he does as an architect leading an agile team.
The Rational Unified Process(RUP) was developed through the 1990's as a framework for software engineering best practices. Features such as iterations, simplicity, focus on value and regular feedback were identified as being important for Asuccessful software engineering. A number of authors have built methodologies that adapt UP to different project domains. This article examines some of them.