InfoQ Homepage Culture & Methods Content on InfoQ
-
How to Evaluate a Good Fit for XP?
XP might not be for everyone. An interesting discussion on the Extreme Programming group, tries to find the factors, on which, an individual should be evaluated, to determine, whether he is fit to be on an XP team.
-
Klocwork Insight Brings Code Analysis to the Desktop
Earlier this year Klocwork released a desktop product, Klocwork Insight, bringing their automated source code analysis features to individual developers. InfoQ recently sat down with Klocwork CTO Gwyn Fisher to discuss the product.
-
An Introduction to Lean Thinking
Lean software development, which we hear a lot about these days, may be still a bit of a mystery for people who come to Agile via Scrum or XP. Earlier this year, at an Open Party was sponsored by InfoQ China, Ning Lu of ThoughtWorks China offered an introduction to Lean thinking, and said the biggest obstacle to Lean thinking can be the manufacturing mindset.
-
Truthfulness - an Agile Value?
Declan Whelan wrote a thought-provoking blog citing an idea he learned from Mishkin Berteig about an (unspoken) principle behind successful Agile teams: truthfulness. The idea is simple: without individuals being honest and open, most agile practices will not work.
-
Presentation: Introduction to Agile for Traditional Project Managers
In this presentation filmed during Agile 2007, Stacia Broderick introduces Agile to traditionally trained project managers by making a comparison between Project Management Institute's (PMI) best practices and their equivalent Agile techniques.
-
FxCop Rules Join the Pipeline Builder for System.AddIn
Microsoft has created FxCop rules for projects leveraging the extensibility framework System.AddIn. This joins the out-of-band project Pipeline Builder as a must-have for developers using this .NET 3.5 framework.
-
Interview: Hakan Erdogmus on TDD Misunderstandings and Adoption Issues
In this interview made during Agile 2007, Dr. Hakan Erdogmus, Editor in Chief of IEEE Software, discusses about TDD starting from a study done by Ron Jeffries and Grigori Melnik and published as "TDD--The Art of Fearless Programming" in the IEEE Software magazine. Hakan talks about current misunderstandings regarding TDD's role in software development and the adoption issues it faces.
-
The BPMN 2.0 Debate Continues
With the continuous merging between SOA and BPM, an attention to BPM design and implementation continues to attract the attention of bloggers whose comments span a wide range of problems from business process design to implementation.
-
Getting Up-to-Speed on NDepend and Code Metrics
Any tool is only good if it is in the hands of a developer who knows how to use it. NDepend is one of those tools which is very powerful but addresses an aspect of software development too few architects or developers understand, software metrics.
-
Announcing: New Google C++ Testing Framework
The folks at Google have recently open-sourced their xUnit-based testing framework for C++ development. The framework is said by project developer Zhanyong Wan to have been in use internally at Google for years by thousands of their C++ developers.cc
-
Is Stream-oriented a better UI paradigm than Document-oriented for today's knowledge workers?
In Bryce Harrington’s opinion, document-oriented paradigm of user interface is not any longer optimal. Most often people deal with streams of information rather than static documents. Harrington advocates for a shift towards a new UI paradigm that would make stream management easier. Many tools and technologies are already based on stream-oriented approach; others are instrumental for adopting it.
-
Presentation: Heartbeat Retrospectives to Amplify Team Effectiveness
In this presentation filmed during QCon London 2007, Boris Gloger speaks about retrospectives. Agile development teams learn and improve by inspecting and adapting. High performing teams inspect and adapt not only their code and tests, but also their methods and interactions.
-
Failures in Agile Development
The Agile software development community discusses it successes on a regular basis, but rarely do we publicly discuss our failures. Robin Dymond has taken the first step by documenting one of his.
-
Interruption Driven Development
Scrum talks about having minimum disruptions during the sprint. However, in the real world, if the system is already in production, within each sprint there is a strong possibility of getting production support issues. The post tries to uncover some ways to take care of these interruptions with Scrum.
-