InfoQ Homepage Culture & Methods Content on InfoQ
-
Panel: Who Says You Have to Be a Guy to Be a Geek?
Susan Potter and JP Chance address the issue of being few women in software development teams, explaining why it matters, and what can be done to improve the situation.
-
The Kiev Experiment: Evolving Agile Partnerships
Simon Ogle, Alexander Kikhtenko, and Peter Thomas present a case study of a development team transitioning from a waterfall approach to 15 offshore Agile teams over a period of 5 years.
-
Team Leadership in the Age of Agile
Roy Osherove discusses three maturity stages of a team and adjusting leadership accordingly, along with techniques meant to bring craftsmanship and maturity in a software development team.
-
Innovation at Google
Patrick Copeland on pretotyping: innovators beat ideas, pretotypes beat productypes, data beats opinions, doing beats talking, simple beats complex, now beats later, commitment beats committees.
-
Learning and Perverse Incentives: The Evil Hat
Liz Keogh talks about perverse incentives that hinder the ability to reach the purpose for which they were created for, outlining the need to focus on the system built not its solutions.
-
Remediation Patterns - How to Achieve Low Risk Releases
Jez Humble presents remediation patterns based on prevention, low risk release through automate provisioning and deployment plus dev/test/ops collaboration, and incremental delivery.
-
Collaboration Over Contracts in Agile “Offshore” Outsourced Development
Craig Larman explains the internal workings of a customer-supplier relationship, advising on how to proceed to ensure an offshore Agile development that is fulfilling for both parties.
-
From Months to Minutes - Upping the Stakes
Dan North reviews many Agile practices and concepts, mentioning what has really made the difference over the years and what has not, outlining what helps high performing teams to do their job.
-
The Invisible Computer Lab
Fraser Speirs presents how computers are used at Cedars School, makes some suggestions on what educational software needs in order to be efficient, and how he sees the future of ICT in education.
-
Making Apps That Don’t Suck
Mike Lee considers that a software engineer makes great applications not because he follows good rules but because he has a better way of looking at the world and he learns from experience.
-
Using Design Thinking to Stop Building Worthless Software
Jeff Patton outlines the concepts behind design thinking: clear problem definition, ideation, iteration, and execution plans that emphasize continuous learning, accompanied by real-life examples.
-
Letters From The Edge Of An Agile Transition
Chris O'Connor tells the successful story of a team’s transition to Agile in the middle of a major product release, mentioning the difficulties encountered and how they tackled them.