InfoQ Homepage Teamwork Content on InfoQ
-
Q&A with Tom Roden and Ben Williams on Improving Retrospectives
InfoQ interviewed the authors of fifty quick ideas to improve your retrospectives about why they wrote the book and how ideas are described, when you can do retrospectives, what facilitators can do to establish safety, why facilitators should not be the ones who solve problems, celebrating successes, good practices for getting actions done, and the value that teams get from doing retrospectives.
-
Innovation at Telefónica with Lean Startup
Creating digital products is different from building traditional telco products: the uncertainty is much higher, the way of creating value for the customer is totally different and lifecycle is much faster says Susana Jurado Apruzzese. Telefónica adapted Lean Startup to their processes, culture and organization to make it work.
-
Q&A on the Scrumban [R]Evolution
In the book “The Scrumban [R]Evolution: Getting the Most Out of Agile, Scrum, and Lean Kanban" Ajay Reddy describes what Scrumban is, explores the principles and theories on which it is based, and shows how Scrumban can be deployed in organizations.
-
Leadership, Mentoring and Team Chemistry
How does fire fighting compare to DevOps? Michael Biven, team lead at Ticketmaster, shares important lessons on leadership, mentoring and team chemistry from his experience as a fire fighter.
-
Q&A on the Book Agile Impressions
Gerald Weinberg shares his observations of the agile movement "where it came from, where it is now, and where it's going" in the book Agile Impressions. In the book he explores the agile basics and principles, discusses how he has seen them being violated, and offers ideas and examples for applying the agile principles.
-
Scaling Mobile at XING: Platform, Framework and Domain Teams
This article describes learning from XING on how to scale mobile development such that as many teams as necessary can contribute to the development of mobile apps (on both iOS and Android platforms) and at the same time keep the apps consistent, stable and shiny. It summarizes the key decisions and structural changes they made in order to enable scaling mobile from 2 to 10 teams.
-
Conversation Patterns for Software Professionals - Part 4
In the fourth article in the Conversation Patterns for Software Professionals series Michał Bartyzel focuses on asking the right questions.
-
What is Success for a Scrum Master?
Experienced Scrum Masters explain how they define and measure their own personal success as Scrum Masters, and share their lessons learned about how to achieve success. From dealing with stakeholders, to how to improve coaching skills and how to help the team achieve a sustainable pace, the lessons come from many years of experience and will help you improve your performance as a Scrum Master.
-
A Case for Diversity in Our Workspaces
Dr. Sallyann Freudenberg makes a case for supporting neurodiveristy in our workplaces.
-
The World is One Family - Why That Matters for Software Corporations and Professionals
Rev. C. L. Gulati of Sant Nirankari Mission presented the opening keynote on the conference theme – Vasudhaiva Kutumbakam – The World is one family, at the Regional Scrum Gathering South Asia 2015. Kamlesh Ravlani, one of the volunteer event organizers, spoke with him about this philosophy, its implications for global organizations and why the software community should care about it.
-
Practices for DevOps and Continuous Delivery
DevOps is an attempt to break the barrier between development and operations teams, who are both required for the successful delivery of software says Danilo Sato. His book Devops in Practice: Reliable and automated software delivery provides a hands-on approach for implementing continuous delivery and DevOps practices.
-
Business, Design, and Engineering: Developing Collaboration-Culture
The collaboration of a company and its multidisciplinary units has never been more crucial than now. Everything we make today depends upon our ability to stay current, move nimbly, innovate, engage and delight. Those things are too difficult to achieve without cross-team collaboration.