Dave Thomas aka "Smalltalk Dave" was kind enough to join Bob Payne for this podcast while the two of them were both attending Agile 2007. These podcasts are a great way to get the inside scoop to what many of the world's popular conference speakers really feel about the topics that matter most.
Bob Payne finally got a hold of Josh Kerievsky so the two could record one of our friendly discussion podcasts together. Bob and Josh discuss the benefits of e-Learning courses for software developers, and how his own companies provides these classes along with other certifications.
What can a test manager do when a project manager says, "Test faster!" or tries to cut the amount of testing to meet a project release date? Fiona Charles says that you can argue for the time and resources you need by incorporating the endgame into your estimations. In this week's column, Fiona details how to structure a winning argument by paying close attention to all the activities that occur during testing.
NCache lets you cache data closer to your application in the middle-tier so you can reduce expensive trips to the database. This in turn significantly speeds up your application. It also makes it more scalable because the load on your database is reduced allowing it to handle a larger number of clients without any hardware upgrades.
Today's Rich Internet Applications (RIAs) bear about as much resemblance to the early Web sites of the 1990s as today's cars bear to a Model T. While the principle may be the same, the underlying technology is radically different. However, while safety testing for automobiles has improved significantly in the past hundred years, Web-application testing remains stuck in a 1990s mindset. In this week's column, Bryan Sullivan explains that QA must change its testing approach in order to maintain the security of the code.
Linda Hayes has always found software development metrics to be problematic. The data either skews perceptions of the project or the actions of the team members. In this article, Linda explains that by turning down the volume of what is being said and measured and simply watching what is actually happening, you can strip away the assumptions and biases that often obscure the truth.
Organizations are recognizing the need for strong process architecture to manage their operations. Increasing acceptance of International models and practices like CMMI, ITIL, Six Sigma stands testimony to the fact., In such a scenario, it becomes imperative that organizations have a clear strategy when they put in place a process improvement program. In other words, the process for implementing a process improvement program also needs a proper structure. Using Quality Function Deployment (QFD) as a tool for initiating a process improvement program could come in handy.
Service Desks traditionally serve the operational and production aspects of IT organizations and their respective business units. However, business services that consist of applications typically start their lifecycle as requirements from the originating business unit, then follow a development lifecycle before entering the operations realm. This development lifecycle
is commonly a blind spot for service desks manifesting most typically via an incident logged against an application in production requiring maintenance or upgrade work to be completed by development.
This summer in 2006, the Agile Project Leadership Network (APLN) co-sponsored the 2nd Annual 'State of Agile Development' Survey. Almost 1,700 respondents from 71 countries shared their companies' experiences using of Agile methods and the challenges that they face with future adoption. Teams have begun to quantify the value that their projects have achieved and are steadily expanding the types of Agile practices and tools that they use. IT metrics are well-understood. Business metrics must also play a role, but few were included in the scope of this survey.
In this article, the authors propose that the most effective teams—those that show a tremendous improvement in productivity and value to their organizations—have individual team members who take ownership, act responsibly, and are disciplined in recognizing and responding to change at a personal level.