Software development in agile is based on testing says José Díaz. Agile has brought us real teams of development and testing without borders. Some of the currently relevant topics in agile testing are the transition from waterfall to agile methodologies, tester skills and Certified Agile Tester, DevOps and mobile testing.
Organization that are adopting agile often look for ways to establish self-organized teams where team members are able to take more responsibility. Agile software development teams could improve their decision making by using the consent principle and sociocratic procedures. Sociocratic governance structures can also be used to scale up agile principles to every level of the organization.
At the upcoming Agile India conference Mark Lines, co-creator with Scott Ambler of Disciplined Agile Delivery (DAD) a process decision framework designed to help organizations to apply agile and lean for their unique context, will present a whole-day workshop on DAD. In advance of the conference he spoke to InfoQ about the challenges DAD is designed to help overcome and the value of certification
Agile suggest teams to self-organize their work. The questions arise what self-organization is and what organization can do to make it possible for teams to become self-organizing.
In February 2015 both Gartner and Software Advice released research and analysis into agile lifecycle management/project management tools. The Gartner Magic Quadrant identifies that the big players have a competitive advantage and the Software Advice study found which aspects of the tools projects managers find most useful.
Diana Larsen is keynoting at the upcoming Agile India conference. Her talk is titled "Dancing Along the Agile Fluency Path" in which she will present a model for achieving and assessing the level of fluency an organisation has in their adoption of agile values and principles. She spoke to InfoQ about collaborative work cultures, barriers to agility, retrospectives and the value of open space.
The majority of change initiatives fail because people feel that they do not have any influence in the proposed changes and don’t understand how they affect them or would make things better for them says Dave Gray. Liminal thinking is a change approach that focuses on understanding how people construct and change their beliefs. It provides a skill set to create and use thresholds to effect change.
People often don’t decide and act rationally, according to studies from the area of behavioral economics. Pierre Hervouet describes how our brain takes decisions, talks about experiments on using personas and the IKEA effect and explains what we can learn from these experiments for agile software development.
At the OOP 2015 conference Colin Hood talked about bridging the gap between requirements engineering process definition and successful iterative roll-out. He presented how the introduction of improvements to requirements engineering can be done better when done step by step, and how relative safety is needed to enable people to take the steps.
Antifragility emphasizes embracing chaos or randomness through adapting and evolving. It can help enterprises to be more able to deal with and even gain from uncertainty and disorder, making them more flexible and adaptive to events that happen.
The Fearless Journey game, designed by Deborah Hartmann Preuss, builds upon the patterns described in the book Fearless Change. It is a game that teams can play to learn how to address obstacles over which they have no authority. Martin Heider and Holger Koschek facilitated a workshop where they talked about using patterns in change and played the Fearless Journey game.
InfoQ spoke to VersionOne about their Winter 2015 release. It gives the ALM tool additional capabilities around scaling, supporting strategic initiatives across organizations, estimation using Monte-Carlo analysis and improves the capabilities around integration with multiple version control systems.
Scrum helps us to see what is happening. We can run experiments in Scrum sprints to improve the way of working using organizational models that help us to reinvent organizations in a way that “agile” becomes natural says Olaf Lewitz. InfoQ interviewed him about how to de-scale organizations and increase consciousness and how to create a culture that enables and fosters honest communication.
In too many cases agile is failing to deliver on its promise says Steve Holyer. At the OOP 2015 conference Steve explained how we can choose the rewards and benefits that we want to get out of agile development and plan the investments to achieve them. He presented the agile fluency model and explored a solution-focused approach for organization to find their path in adopting agile.
“An agile enterprise is able to anticipate and respond swiftly to changes in the marketplace” says Scott Ambler. InfQ interviewed Scott about the reasons why agile projects are failing, how to increase budgets for building new systems, disciplined DevOps, harmonizing agile and lean, and on coaching for enterprise agility.