Testing teams and their managers need to unlearn the traditional mindset and practices when they want to adopt an agile way of working says Navneet Goyal. At the International Conference on Software QA and Testing on Embedded Systems he gave a talk about how test teams should adapt themselves in agile projects.
Codenvy has evolved its flagship service from a cloud-based code editor to a full fledged, container-based development environment. Codenvy CEO and Founder Tyler Jewell told InfoQ that Codenvy is no longer an “IDE, but an orchestration engine” that wants to optimize “everything before the commit.”
Organizations should create an environment where people feel empowered and trusted, with a culture where leaders can thrive says Pawel Brodzinski. An interview in which Pawel shares his view on leadership and culture, explains what it is that makes leaders thrive in organizations and what organizations can do to create an environment where leadership would emerge.
Complexity is a direct indicator of software quality and costs: if the complexity for any code is high, the quality of that code will be lower and it will cost more to manage it. Complexity measurements can be used to estimate development and test activities and to decide where refactoring is needed to improve quality and prevent problems.
Devices are becoming increasingly interconnected through the internet where they are communicating directly with each other. Testing such machine to machine (M2M) systems can be difficult due to their complexity and the usage of different platforms, as Peter Varhol explained in his talk about testing in the M2M world at the QA&Test 2014 conference.
By using Model Driven Development component tests could be skipped and integration and system testing went a lot smoother, said Bryan Bakker in the presentation Model Driven Development (MDD) and its impact on testing. Main results from the MDD approach are a reduction of the amount of testing and increased reliability of the code that was generated from a mathematical model.
Testability must be explicitly designed in the system said Peter Zimmerer from Siemens AG. Test architects should drive testability and collaborate with architects, designers and testers in using good design and engineering practices. At the QA&Test 2014 conference Peter gave a tutorial about design for testability for embedded software systems.
Blockades in work, like insufficient information, unclear requirements or having to wait for tools or systems to become available can have a systematic cause. It could be the case that similar problems that block the team keep happening until the underlying causes are addressed. You can use your blockades as treasures of improvement to sustainably improve the way work is done.
Ryan Mckergow explains various ways to set up story walls for agile team. This post includes setting up columns, rows, selecting colors and avatars for the story wall.
There are several recent posts and discussions dedicated to a fairly common approach to software development: Fear Driven Development.
Creating and maintaining a Quality Management System (QMS) can be difficult, certainly when organizations have multiple product lines where different regulations and standards are applicable. InfoQ interviewed Willem van den Biggelaar about the benefits of having a QMS, dealing with multiple regulations, assuring adherence, how a QMS can support agility and deploying a QMS in an agile way.
Last week VersionOne and CA Technologies announced that they have integrated their Project and Portfolio Management (PPM) and Agile Project Management (APM) products to provide an enterprise solution which the two organisations say gives users the ability to have a strategic view of a complete portfolio at the executive level no matter what methodology teams might use.
Bob Marshall explains the reason of failing of scrum master in most of the organizations as the lack of awareness on the part of adopting scrum and scrum master’s responsibility to tackle organizational dysfunction.
Dave Thomas and Martin Fowler participated in a panel for the GOTO Conference series, focused on ‘A retake on the Agile Manifesto’, inspired from Dave’s blog, ‘Agile Is Dead (Long Live Agility)’. In this Q&A, Dave (also known as Pragmatic Dave) explains his thoughts around the panel, his blog and why he believes it’s time to focus less on agile and more on the practical application of agility.
The 2014 CAST Research on Application Software Health (CRASH) report states that enterprise software built using a mixture of agile and waterfall methods will result in more robust and secure applications than those built using either agile or waterfall methods alone. InfoQ interviewed Bill Curtis about structural quality factors, and mixing agile and waterfall methods.