The state of testing survey 2015 aims to provide insight in the adoption of test techniques and practices, test automation, and the challenges that testers are facing. Ongoing developments have impact on testing, such as the Internet of Things (IoT) and the adoption of agile where developers and testers collaborate in teams and competencies become more important than roles and titles.
At the XP Days Benelux conference, Paul Kuijten did a session called "kill all projects" where he questioned if getting rid of all projects could be a good idea. InfoQ did an interview with Paul about project management practices that can be valuable for agile, and the funding of product development.
Guillaume Duquesnay uses his experience with games and roleplaying in his work as an agile coach. At the Agile Tour Brussels he talked about leadership, facilitation and management styles where no authority was involved. InfoQ interviewed Guillaume on his coaching, facilitation and leadership skills, and asked him if playing games gives happiness and fun to people, and make them more productive?
The Product Owner role is regularly debated and discussed. The challenges of the role and the responsabilities encompased by it are a frequent source of discussion and advice. Recently there has been discussion about common aspects of the role and the important activities a product owner needs to ensure happen on an agile project, and the difference between the product owner and product manager
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.
Patrick Wilson-Welsh, Chris Beale, Gary Baker, John Huston, Daryl Kulak, and others are attempting to popularize the idea of a new role, the "Agile Team Lead", to supplant many of the existing leadership roles found in and around agile teams.
In this presentation recorded during QCon London 2008, Udi Dahan, The Software Simplist as he calls himself, explains why sometimes it is not enough to apply good OOP and patterns lessons. He introduces a new principle: make roles explicit.
Mapping traditional software development roles to just the three roles in Scrum can be challenging. Mike Cottmeyer attempts to provide an effective mapping which would help the teams.
Vikas Hazrati recently posted an article on Agile Journal, defining his ideal characteristics of an Architect working in an Agile team, reflecting how the role of Architect has changed in light of Agile practices.
At Qcon London, Kevin Jones spoke from his experiences about Building Better Apps using MSF for Agile with Visual Studio Team System (VSTS). Using examples from Agile teams, he walked through the layers and components of Microsoft's tools, emphasising their flexibility. For Agile teams considering / already committed to Microsoft, this video provides an experienced viewpoint & may be worth a look.
Service Governance is an essential aspect of a successful Service Oriented Architecture. Its establishment has to be planned and tested out early in the initial phases of a SOA initiative. In this article, Jean-Jacques Dubray shows what it takes to create such a structure efficiently.