InfoQ Homepage Culture & Methods Content on InfoQ
-
Gaming Happiness At Work
Dan Mezick introduces Gaming Happiness at Work, then discusses related goals, rules and scoring, the relationship between games and happiness, and how to bring it all together in work meetings.
-
The Ideal Programmer - Why They Don't Exist and How to Manage Without Them?
Mike Williams outlines some of the main characteristics that make developers and teams perform better than the average.
-
The Value Proposition for Agility–A Dual Perspective
Hakan Erdogmus and John Favaro explain why agility is good and when. They associate agility with flexibility which can lead to a better but more costly decision making process.
-
We Are No Engineers
Jim Benson develops the idea that software is not engineered, and it is better done collaboratively by a communicative team using Agile and Kanban methodology and tools.
-
Building Scalable Products that Customers Love
Per Jonsson discusses Lean Startup in the context of real world examples, and helpful tools for startups - Feedback Loop, Customer Development and the Lean Canvas.
-
It's All About You!
Sue McKinney discusses the roles of managers and developers within an organization where everyone owns delivery and is accountable.
-
Use and Abuse of Other People's Cucumbers - When Cucumbers Go Bad
Matt Wynne discusses Mortgage-Driven Development and adopting other people’s tools and processes without adaptation or consideration to actual needs.
-
The Power of Play: Making Good Teams Great
Portia Tung believes that play at work can improve team relationship and can fire up creativity.
-
Being Followed: How Individuals Help Teams Become Excellent
Mike Hill advises individuals on becoming coaches for their teams using 5 techniques: Sorting, Releasing, Situating, Modeling, and Inviting, and learning what should be avoided when coaching.
-
Software’s Hidden Clockwork: A General Theory of Software Defects
Les Hatton theorizes the possibility to predict the number of defects in software systems based on the observation that such systems have properties independent of why, how or who implemented them.
-
Entirely Predictable Failures
Poul-Henning Kamp considers that if developers are not getting better, we are going to repeat many of the major IT project failures. He exemplifies with major Denmark project failures.
-
Embracing Variability
Don Reinertsen proposes addressing uncertainty not by considering it harmful nor by embracing it but by efficiently reducing it in the context of the economic laws governing the software dev process.