InfoQ interviewed John Willis about what made him decide to talk about burnout, the possible effects of burnout for a person, how burnouts are impacting the software development industry, leading indicators of a potential burnout and how they can be used to prevent burnouts, and suggestions for dealing with mismatches between employees and organizations that can cause a burnout.
Andrea Tomasini will give a keynote talk titled "Stop Scaling, Start Growing an Agile Organization" at the Agile Eastern Europe 2016 Conference. InfoQ interviewed him about growing agility.
InfoQ interviewed Martin Kearns about how agile contracts differ from contracts for waterfall projects, how contracts can deal with scope changes, major disturbances or delays during development, how contracts can enable agile behaviour and help all those involved to work together based on an agile mindset, and the role that lawyers can have when organizations want to use contracts with agile.
This post covers the challenges of an introverted mob programmer and some possible solutions.
Naresh Jain, conference chair and founder of Confengine opened the second day of the Agile India conference with his talk titled the Dark Side of Collaboration. The premise of his talk is that in the rush to encourage collaborative workspaces and the hype about the benefits of collaborative work organisations have forgotten the importance of solitary thinking time for creativity and ideation.
Eduardo Nofuentes talked about agile beyond software at 1st conference in Melbourne, Australia. He explored how you can deploy the agile principles and values outside software development, and gave examples of how he has used them to increase business agility when working with call centres and other non-software teams.
Dan North talked about models and techniques for giving and receiving feedback and how to apply them effectively at the QCon London 2016 conference.
Operable.io announced Cog, a ChatOps platform that provides fine-grained access control, UNIX-like pipelining of commands and audit logging features.
An interview with Erin McManus and Ryan McKergow about the need for business analysis in agile, how agile impacts the role of the business analyst, the changes that they have seen in business analysis when agile is being adopted, and specific business analysis practices that that they can recommend for agile teams.
This third post and last in the series on leadership fit for the 21st century covers the keynote given by David Marquet at the evening seminar on leadership fit for the 21st century about intent-based leadership and the leader-leader model.
Andy Kelk talked about nurturing and growing agile teams at 1st Conference in Melbourne, Australia. His talk is based on the blog post Culture Gardening.
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.
InfoQ interviewed Stephen Carver about how bringing in procedures and rules often doesn't help to prevent problems, enabling communication between engineers working in different companies, taking learnings from failure to a next level to prevent similar problems, and what engineers can do if they want to influence decisions on developing and releasing products.
InfoQ interviewed Dan North about the activities that are performed by database administrators and how they are related to those done by developers and by operations, how database administration is usually organized, how the database fits into DevOps or Continuous Delivery, and what he expects that the future will bring for database administration when organizations adopt DevOps.
Thomas Bradford talked about his experience with maintaining a monolith Java based system with zero test coverage and large technical debt at the Agile Testing Days 2015. InfoQ interviewed him about the problems that they had maintaining the system and the technical debt that had been build up, why they decided to take a different approach and how they improved team morale.