Kelsey van Haaster will give a talk at 1st Conference about how to develop a road map to agile fluency for teams and organisations. InfoQ interviewed her about the possible ways to do an agile fluency assessment, example of findings and improvement opportunities that came out of the assessments and things that she learned, and advice for readers who want to use the agile fluency model.
At the Agile Practitioners 2016 conference Huib Schoots talked about testability. He stated that low testability, anything that makes our software hard to test, slows teams down, and explored how testability can be increased.
At the Lean Kanban Benelux 2015 conference Jeroen Molenaar shared his experiences working as an agile coach with the Dutch solar car team that has won the world solar challenge in Australia.
Selena Delesie gave a keynote at the Agile Testing Days 2015 about leadership principles that she sees in successful agile companies. InfoQ interviewed her about how leadership principles from Sir Richard Branson are related to the foundations of agile and asked her which principles are giving companies a competitive edge and how companies can deploy agile to become more competitive.
Autonomy is one of the core guiding principles at Spotify. It enables employees to make decisions as close to the works that is being done as possible. At the Agile Greece Summit 2015 Kristian Lindwall and Cliff Hazell from Spotify explained why autonomy is at the heart of agility.
Small and medium sized companies have adopted the agile way of working in Greece and there are few examples of agile in larger organizations, interest in agile from the local industry is growing. Among the topic discussed in agile meetups are whether companies should implement Scrum or Kanban, Scrum for startups, dealing with fixed price and scope contracts, productivity, and happiness in teams.
How to use Rory Story Cubes for sprint retrospective.
Oliver Hankeln shares the anti-patterns he found for handling failure in organizations: hiding mistakes, engaging in blame game, the arc of escalation and cowardice. He then suggests corrective actions for each of them.
It is very important to have courageous communicators in agile teams. Senior leadership should support the role of courageous communicators.
This post includes the limitations of Five Whys technique.
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.
Laughing can help to create a better team climate which can lead to better results. There is compelling evidence that happiness and positivity can lead to success. Here are some suggestions for what you can do when you want to improve happiness in teams.
In agile software development feedback plays an important role. Many are aware how feedback supports dealing with changing requirements and adjusting the way of working in teams with retrospectives. But there is more that feedback can do in agile. “An effective feedback cycle in Scrum is more than having sprints and doing retrospectives” says Kris Philippaerts.
The introduction and integration of agile approaches to an organization should be regarded and treated as an agile project itself says Andreas Schliep. An interview with Andreas about pitfalls when trying to scale agile, on ScALeD and how it compares to Agility Path, LeSS, SAFe and DaD, and on continuous improvement and scaling retrospectives.
Pair Programming is good for increasing the software quality and collaboration within team members but it is hard to implement. This news describes the reasons why it is hard and how to figure out good practices of pair programming for your team.