Dead code needs to be found and removed; leaving dead code in is an obstacle to programmer understanding and action, and there's the risk that the code is awakened which can cause significant problems. Deleting dead code is not a technical problem; it is a problem of mindset and culture.
Applying the teal paradigm helps organizations increase team members' engagement and allows teams to grow. Teal oriented organizations think of themselves as "living organisms"; they are human centric and liberating towards their employees, and look for the resourcefulness in humans rather than looking at humans as resources.
Feedback can be used to build trust in teams and help individuals improve their skills and grow in their craft. Emily Page and Doug Talbot shared their experiences from experimenting with peer feedback at Ocado Technology at Spark the Change London 2016. An interview with Emily Page, Organizational Catalyst at Ocado Technology.
When developing a high speed printer based on a new print technology things change often; you need an effective and flexible solution for managing a large project with many different disciplines. Océ Printing Systems decided to customize Scrum and scale it to enable collaboration and make progress transparent.
Studying successful organisations can inspire you and provide ideas to improve your own organisation. Helena Moore explains how reading case studies about high performance leadership and culture from organisations like Netflix, Zappos, and Virgin, and visiting organisations like Timpson has helped to understand what makes these organisations successful and to find ways to apply them.
Regina Martins talked about anti-patterns of agile leaders at the Agile Practitioners 2016 conference. InfoQ interviewed her about what makes leadership important for agile, the key attributes that can make somebody a great leader, examples of leadership behaviour that hinder agile teams and how to deal with them, and asked her to share stories of great leadership.
Odile Moreau presented a case study of a big insurance company who started their Agile journey with Kanban for IT Hosting teams at the Lean Kanban Benelux 2015 conference. InfoQ interviewed her about the situation at the insurance company, what made them decide to choose Kanban, how teams use Kanban to manage flow and coordinate, and asked her to share learnings from this Kanban journey.
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.
At the Agile Greece Summit 2015 Erhan Köseoğlu presented a case study of scaling agile from Vodafone Turkey. InfoQ interviewed him about why Vodafone decided to implement agile, how they dealt with situations where people resisted, how they established a culture that supports agile, how they involved their customers in the agile transition, and which advice he want to give to C-level executives.
Swiss Postal Services has used scaled Scrum with seven teams to replace a legacy system. InfoQ interviewed Ralph Jocham about how they scaled Scrum and dealt with legacy issues, using a definition of done, how they managed to deliver their system three months earlier than planned, and the main learnings from the project.
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.
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.
Lindsay Holmwood, Flapjack's creator, offers advice to enable fast, with quality, feedback loops and to support small, discrete changes. Holmwood asserts that to get quality feedback there are five main issues to think about: the CAP theorem; SLA definition; SLA validation; interfaces between services; data and infrastructure immutability.
InfoQ interviewed Hans Aerts, vice president software development and agile coach at TomTom, about why they decided to adopt SAFe and how it was introduced and used to simplify the organizational structure and stop doing projects, why they focus on throughput rather than output, how they modified SAFe for Custom Systems, and what using SAFe has brought TomTom.
Here's an experience story from a tester who decided to move onward and become a Scrum master to help her team to become more agile, with learnings from their agile journey and pieces of advice for doing change in organizations.