Teams consist of individuals working together. Individuals have their own specific beliefs and perceptions. If you know where a person’s perceptions are coming from, you can better understand why they see things different than you do and behave in a certain way. Being able to understand people helps to find better ways to collaborate and communicate in teams.
Niels Pflaeging, founder of the BetaCodex Network, did the opening talk organize for complexity - how to get life back into work on the second day of the Dare Festival Antwerp 2014. He explained how decentralizing organizations is paramount to increase their performance and agility.
At the Dare Festival Antwerp 2014 Jurgen Appelo talked about his new book Management 3.0 Workout and showed examples how organizations can improve the way that they manage themselves.
At the Lean Kanban France 2014 conference Bjarte Bogsnes gave a keynote presentation about beyond budgeting. In his presentation he talked about the problems with traditional management and how transparency and self regulating management comes to the rescue, and the principles and practices of beyond budgeting.
Esther Derby talked about leaders at all levels at the Lean Kanban Central Europe 2014 Conference. She showed how you can create a more flexible organization with improved communication and decision taking by working on the conditions for leadership at all levels in the organization.
Bob Marshall explains the reason of failing of scrum master in most of the organizations as the lack of awareness on the part of adopting scrum and scrum master’s responsibility to tackle organizational dysfunction.
In the book series the art of managing remote teams authors share their experiences and provide advice on establishing and working with remote teams. The books are intended for people who are about to setup an offshore or nearshore team, or people who are already managing a remote team and want to improve.
Agile retrospectives are mostly done at the team level or at a project level. What if you need to conduct a retrospective with 50 teams or more? Luke Hohmann describes how a large scale agile transformation project did a huge retrospective to create insight on what was going well and what needed to be improved.
The Guide to Critical Success Factors in Agile Delivery discusses the values, benefits and challenges of agile and proposes critical success factors for implementing an agile delivery in the federal government. InfoQ interviewed Paul Gorans about implementing agile practices, how agile impacts acquisition and procurement, scaling agile communication and the usage of reviews in agile.
In the article culture is the true north Arne Roock talked about the “feel good manager”: a role which helps to foster and grow the culture in an organization. InfoQ talked with Magdalena Bethge, Feel Good Manager at Jimdo, about supporting the culture and collaboration, happiness, and helping employees to find their work-life balance.
The Manifesto for Agile Software Development values "working software over comprehensive documentation". This core value asks us to think about how much and which kinds of documents are needed and when they need to be written.
In "experiences with a distributed agile team", Joost Mulders and Andriy Korpan presented how they integrated a near shore development team from Ukraine in a Dutch product development organization using agile practices. At the XP Days Benelux 2013 conference they talked about the do’s and don’ts of distributed agile.
In the XP Days workshop Agile cross borders, Hoang-Anh PHAN & Anais Victor explored how you can deal with language barriers in a multi cultural organization. They work for the Vietnamese company Officience who provides outsourcing services to French customer, using the English language to communicate and work together.
At the Agile Tour Brussels conference, Luc Taesch facilitated a workshop about understanding and listening. He applied "cognitive science" or "neuroscience" for IT Professionals, and provided solutions to help them dealing with interrupting thoughts and feelings.
Retrospectives are often considered to be a valuable agile technique, but sometimes teams have difficulties doing them: insufficient control of things, thinking that they can’t improve, difficulties defining good actions, or much complaining. Teams may find retrospectives boring, and a waste of their time. How to deal with this, and help teams to discover better ways to do retrospectives?