The volatility in the market requires that organizations become able to adapt to changing demand as fast as possible while gaining the highest value. To implement agile managers need to team up to remove impediments in the organization says Ahmet Akdag. An agility transformation is about learning to try, fail and learn.
At the recent Agile 2015 conference the Agile Alliance hosted the fifth annual industry analyst panel briefing in which a group of commentators answered questions on the theme of agile trends and future directions.
Some people stress the need for agile training with certification, as it helps to select candidates and lays a foundation for an agile transformation. Others are against certification, in their opinion they don't reflect people's abilities and skills properly and people who have no certifications might be better candidates than others who have. Are you pro or against agile certification?
Dan Tousignant, Agile Executive Coach and Trainer at Cape Project Management, proposed a matrix to help organizations choose their Agile approach.
InfoQ interviewed Jeff Sutherland about the problems that larger organizations have when adopting Scrum, how they can increase their capability for handling impediments, improving agile leadership, what Scrum masters can do to help teams to become agile, and his advice to managers when their organization is implementing Scrum.
Even with best intentions it can be challenging for people to follow up on actions that they agreed to do. They can start to doubt if they can do the actions and become afraid to fail. Several authors have recognized this and came up with suggestions for dealing with it and making change happen.
The state of testing 2015 report shares results from this year's testing survey that was organized by Joel Montvelisky from PractiTest and Lalit Bhamare from Tea-Time with Testers. It provides insights in the adoption of test techniques and practices, test automation, and the challenges that testers are facing. InfoQ did an interview with the organizers of the survey.
An interview with Ivan Kusalic, Software/DevOps engineer at Nokia HERE in Berlin, about why they decided to apply DevOps, how DevOps has changed their way of working, which benefits they are getting, and the challenges that they had and how they dealt with them when development and operations became one team. Kusalic also gives some advice for applying DevOps with teams.
James Shore presented a workshop at Agile Australia titled “Bringing Fluency to your Agile teams: Coaching for Best-Fit Agile”. The focus of the workshop was the use of the Agile Fluency model, which he and Diana Larsen have developed, as a tool for coaches to use when choosing the approach to working with teams based on their level of fluency with the agile values, principles and practices
InfoQ did an interview with Menno Vis, IT director of bol.com, about the benefits of increasing agility, how bol.com deploys Scrum, using roadmaps with agile, the challenges that have been faced when scaling agile, the main focus area's at bol.com for agile scaling, establishing loosely coupled teams, and the things that bol.com does for their people to have fun while doing their work.
InfoQ interviewed Frank Penning, PMO manager from Philips Lighting, about the main challenges that Philips Lighting is facing in product development, why Scrum is not enough, how they apply SAFe, and the benefits that they have gained from deploying agile methods for product development.
InfoQ interviewed Andrea Provaglio about business models for execution, optimization and discovery, dealing with uncertainty and leveraging it to create business value, understanding both value and cost, growing a discovery mindset, and creating a culture where people have the courage to make mistakes and can learn from them.
InfoQ interviewed Jan van Moll about regulatory demands for software in healthcare, satisfying these demands with waterfall project or with a mix of waterfall and agile, and introducing agile in an R&D organization that needs to fulfill regulatory demands.
Martin Fowler describes yagni practice, why its is important and the costs of building presumptive features. Yagni is an acronym that stands for "You Aren't Gonna Need It". It is an Extreme Programming (XP) practice which states a programmer should not add functionality until deemed necessary.
Continuous Integration can help to find integration issues earlier and to visualize the status of the build to all involved. Integration problems can be detected at build-time in stead of run-time during testing and teams can get immediate feedback on changes that they made and on the impact on components that are developed by other teams.