You can increase the quality of products by constantly increasing the level of automation of the delivery process and working with DevOps teams who constantly deliver small features to get quick customer feedback. A case story from ING Lease explaining the problems they had, experiences from the first steps of their agile and DevOps journey and exploring what they want to achieve in the future.
In the closing keynote of the Agile Eastern Europe 2015 conference Yves Hanoulle did an experiment together with his son Joppe in pair presenting. InfoQ interviewed Joppe and Yves Hanoulle about doing experiments, checking the safety of the environment and ways to make it safer, learning from failure, and presenting in pairs at conferences.
It is very important to have courageous communicators in agile teams. Senior leadership should support the role of courageous communicators.
Introducing and managing change in organizations can be challenging. InfoQ interviewed Jason Little who is involved in organizing the Spark the Change Canada 2015 conference about the leadership and management approaches that radical companies use, on finding better ways to manage people and about what will happen to management in the near future.
Lisette Sutherland has been doing interviews with people that are working in or managing remote teams. She talked about building trust on remote teams at the No Pants Festival 2015.
Larry Maccherone, a Data Scientist at Tasktop Technologies, gave a talk at QCon London 2015 regarding the importance of metrics usage and how they should influence important decisions in the organizations.
This post includes the limitations of Five Whys technique.
Music can be used as a metaphor to illustrate learnings from agile and testing. Alexandra Schladebeck and Huib Schoots will do a live performance in their keynote “where words fail, music speaks” at the Agile Testing Day Netherlands 2015. An interview about artistic parallels between music and agile testing, what agile teams can learn from musicians, and feedback in agile software development.
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.
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.
Jens Hoffmann facilitated a workshop on leading creative collaboration to make ideas and people grow at the OOP 2015 conference. In his workshop he explored how we can lead ourselves and others. He did exercises with the attendants where they practiced collaboration, listening and using powerful questions.
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.
Impediments are issues that hinder agile teams. They are problems that teams are facing, which they need to solve. Managers can help agile teams in several ways to solve impediments.
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.