January 21, 2013
Many people consider that software architecture is a burden for agile software development and that a “good” design will naturally emerge as code is produced during each Scrum sprint. This however rarely the case and as in many other activities, you have to find the right balance between doing enough but not too much software architecture. In the article, “A Risk-Driven Model for Agile Software Architecture“, George Fairbanks, the author of the book “Just Enough Software Architecture – A Risk-Driven Approach“, explains how to achieve this balance.
The main rule is that the effort you spend on designing your software architecture should be commensurate with the risks faced by your software development project. The article examines how risk reduction is central to all engineering disciplines. It explains how to choose techniques to reduce risks and show how you can balance planned design with evolutionary design during agile software development projects.
December 15, 2011
Use cases, user stories, or backlog items already define broadly the scope of a project. Many teams consider requirements as something provided by the business users, product owners or customers. Asking business users to provide the scope is effectively relying on someone who has no experience designing software solutions to give us a high level solution design. This article explains how project teams can work together with business users to come up with the right scope. To reach this goal, you need to start with business goals, and not with user stories, and derive the scope from that.
October 3, 2011
The clarity of requirements is an issue for many software development projects. Based on a course on Agile Requirements, this article at summarizes the levels of Agile (and frankly non Agile) requirements and how you can use a four step process for gathering them.
March 29, 2010
Methods & Tools is a free e-magazine for software developers, testers and project managers. Spring 2010 issue has just been published with the following articles:
* Using WatiN to Leverage Common Elements in Web Testing – structure your Web testing efforts
* Five Symptoms of Mechanical Agile- detect agile adoption issues
* Writing Testable Code – testable code is better code
* Model-Based Testing Adds Value – a quicker way to functional testing plans
* Tool: Sonar – monitor code and project quality
* Tool: Express Agile Project Management – a simple tool for Scrum
* Tool: Apache JMeter – for load and functional testing
60 pages of software development knowledge that you can download from http://www.methodsandtools.com/mt/download.php?spring10
February 26, 2010
OpenSourceScrum.com is an interesting directory of open source tools for Scrum containing also links to tools reviews.