InfoQ Homepage Agile Conferences Content on InfoQ
-
Making People Feel Empowered with Intent-based Leadership
Intent-based leadership is about giving control and decision-making power to people who have the information. When we give control to people who have the competence and clarity, we create an environment where great things happen. An interview with Jenni Jepsen about intent-based leadership, giving influence and control to people, and creating an environment where people can feel empowered.
-
Kanban at the Dutch National Archive
Bianca Griffioen gave a talk at the Lean Kanban Benelux 2015 conference about how kanban has been adopted to visualized, prioritize and manage work at the infrastructure and services department of the Dutch National archive. InfoQ interviewed her about why they decided to go for kanban, how they introduced kanban and use it, how the team and stakeholder feel about kanban and what they learned.
-
IT Hosting with Kanban: A Case Study from an Insurance Company
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.
-
Agile with Internal Coaches and Facilitators
An interview with Andreas Schliep and Peter Beck about why internal coaches and facilitators are important when organizations want to increase their agile maturity, advantages and disadvantages of working with external coaches, how internal coaches contribute to agile adoption, what internal coaches and facilitators can do to be ready to work effectively, and qualification of internal coaches.
-
Rebuild or Refactor?
Should you rebuilding or refactoring software?An interview with Wouter Lagerweij about what it is that makes refactoring so difficult, if rebuilding software is less risky than refactoring, and how continuous delivery fits with rebuilding software.
-
Q&A with David Anderson on Enterprise Services Planning
Enterprise Services Planning is a way of planning, scheduling, sequencing, and selecting work for professional services. It extends Kanban for enterprise-wide service improvement. InfoQ interviewed Anderson about what Enterprise Services Planning (ESP) aims to deliver, how it can be used to manage risks, how cost of delay can be used inside ESP, and why feedback loops are important in ESP.
-
Role of Testers in Agile Teams
Karen Greaves and Sam Laing will give a keynote titled "testers are dying" at the Agile Testing Days 2015; InfoQ will cover this conference. InfoQ interviewed them about how agile impacts the role of testers, what testers can do to shorten the lead time of testing, collaboration between testers and other team members in agile teams, and the value that testers can contribute in agile teams.
-
Turn the Ship Around - Towards Leadership at Every Level
At the Agile Tour London 2015 Wim Heemskerk and Dirk Mulder hosted a session about creating leadership at every level, based on the book Turn the Ship Around by David Marquet. InfoQ interviewed them about how hierarchy can hinder transitioning to agile, why organizations should develop leaders in stead of followers, and on applying leadership lessons from the book to increase the agility.
-
Getting Business Advantage from Continuous Delivery
Gojko Adzic presented a keynote on "how to turn continuous delivery into competitive business advantage" at the Agile Tour London 2015. InfoQ interviewed Adzic about getting benefits from continuous delivery, Gojko's three rules of continuous delivery, possible problems and risks, and using multi versioning with continuous delivery.
-
Planning with #NoEstimates
People are used to making plans and taking decisions using estimates, even though they are often not so good in estimation says Gil Zilberfeld. The #NoEstimates movement explores alternatives for estimation. At the Agile Testing Days 2015 Zilberfeld will do a workshop on Planning with #NoEstimates. InfoQ will be covering this conference with write-ups, Q&As and articles.
-
Role of Autonomy in Agility
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.
-
Directing complex IT-landscapes with Agile
Where many organizations use agile to develop IT products, agile principles and practices can also be applied for maintaining landscapes of commercial products. Gert Florijn and Eelco Rommes will talk about directing complex IT-landscapes in public sectors such as healthcare and local and national government organizations at the Agile and Software Architecture Symposium 2015.
-
Experiences from the Scaled Agile Journey of Vodafone Turkey
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.
-
Agile Fluency at the Agile Alliance & Agile Open Northwest Open Space Conference
At the combined Agile Alliance and Agile Open Northwest Open Space event in Portland Declan Whelan and Diana Larsen led two sessions in which they explored the application of the Agile Fluency model for understanding and addressing technical debt and showed a game based on the model which teams can use to help them identify practices and principles they want to adopt based on their fluency goals
-
Scaled Scrum at Swiss Postal Services
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.