InfoQ Homepage Collaboration Content on InfoQ
-
Scaling Agile - Slice and Understand Together
This second article in the series about making scaled agile work digs into how to slice requirements. If this is done right, it will not only result in good slices, but also a common understanding of the product we’re about to build or enhance.
-
Q&A on the Book Executive’s Guide to Disciplined Agile
The Executive’s Guide to Disciplined Agile explains how disciplined agile works at different levels in the organization. It provides a framework with principles and practices to help you to streamline information technology and business processes in a context-sensitive manner.
-
Improving Corporate Cognitive Performance in IT Organisations
The biggest tool in the software engineer’s toolkit is the brain, yet few organisations go out of their way to educate and create the conditions in which the brain can work at its best. Explore the different domains of the brain and their links to the performance of software engineers and see what organisations can do to create workplaces that propagate advanced levels of cognitive performance.
-
Six Ways Agile Can Turn Static
Agile development in the right circumstances enables organizations to release high quality software that changes rapidly to drive businesses forward. It just doesn’t work all the time. Success requires collaboration, transparency and real-time visibility into project risk and quality.
-
Q&A on the Book "The Stupidity Paradox"
In "The Stupidity Paradox", Andre Spicer and Mats Alvesson explore how knowledge intensive organizations employ smart people and encourage them to do stupid things. Functional stupidity can be catastrophic, however a dose of stupidity can be useful. The book advises how to counter stupidity or reduce the consequences, how to exploit it, and how to benefit from it.
-
Q&A on The Digital Quality Handbook
The Digital Quality Handbook explores the challenges of testing mobile and web applications and shows how to apply agile practices to deliver quality at speed. Some of the topics covered are test automation, sizing mobile testlabs, addressing test flakiness, crowdsourced testing, performance testing, and applying DevOps practices.
-
Q&A on the Book Timing Is Almost Everything
Executives can and should get involved with the way that software is being developed. In his book Timing is Almost Everything, Roland Racko shows how you can increase software success by using a "management by query" executive style in the early stages of software development initiatives to influence how teams think and behave.
-
Consensual Software: How to Prioritize User Safety
This article covers how consensual software will help address online harassment and abuse vectors before they get out of hand. It also covers some features the GitHub Community & Safety team has built and how we review features from other teams.
-
The Microgaming Idea Factory: Innovation in Practice within a Leading Online Gaming Software Company
It’s easy to get so bogged down in the pressure of daily work that we don’t have time to think creatively or space to implement ideas. We talk about empowering staff, but few are offered any opportunity to innovate outside their direct role. Microgaming built the Microgaming Idea Factory to ensure innovation was company-wide. Winner of The Spark Award 2017, sponsored by hotelbeds.
-
Book Q&A on Product Mastery
The best product owners are insatiably curious about their customers; they observe them in action, interview them, and collaborate with them and bring them into the development process, said Geoff Watts. In his new book Product Mastery he explores what he calls “the difference between good and great product ownership”.
-
The Divisive Effect of Separate Issue Tracking Tools
Separate issue tracking systems for Development and IT Operations are a source of conflict and ineffectiveness for many organizations. For effective Database Lifecycle Management (DLM), we typically need shared issue tracking systems where DBA teams can see upcoming work from Development and Development teams can see details of live service issues logged from Production.
-
Teams and the Way They Work
The terms “self-organised” and “cross functional” are often used to describe a team. What does this mean, and how will you recognise if your team has these features? Great teams work with the uniqueness of each person’s skills, experiences and outlook – forging the motivation to achieve a shared goal, within the constraints in which they operate.