InfoQ Homepage Culture & Methods Content on InfoQ
-
/articles/dvcs-guide/en/smallimage/starting_blocks_small.png)
Distributed Version Control Systems: A Not-So-Quick Guide Through
Since Linus Torvalds presentation at Google about git in May 2007, the adoption and interest for Distributed Version Control Systems has been constantly rising. We will introduce the concept of Distributed Version Control, see when to use it, why it can be better, and have a look at three actors in the area: git, Mercurial and Bazaar.
-
/articles/fields-it-depends/en/smallimage/poker.jpg)
Software Development Lessons Learned from Poker
There is no silver bullet. We know it, but don't act like it. Your language, tool or process is better, right? Jay Fields says: "It depends". The right choices varies with context, people, and more. This article touches upon how a lot of things must impact a choice; learning culture, skill levels, teamwork, incomplete information, metrics - and context.
-
/articles/Agile-adoption-study-china/en/smallimage/scrum.gif)
Improvement, Success and Failure: Scrum Adoption in China
This recent inquiry, by InfoQ China editor Jacky Li, picked 5 very different cases of Scrum adoption in China, which got different results, and asked: Why did you use Scrum? How did you adopt it? What problems did you encounter, and why did it succeed or fail? Despite the small sample size, it's an interesting comparison, pointing out that improvement doesn't ensure success.
-
/articles/qconlondon-2008-summary/en/smallimage/qconlogo.jpg)
Key Takeaway Points and Lessons Learned from QCon London 2008
This article presents the main takeway points as seen by the many attendees who blogged about QCon. Comments are organized by tracks and sessions: Keynotes, Architectures you've always wondered about, The Cloud as the New Middleware Platform, SOA, REST and the Web, Evolving Java, Banking, Agile in Practice, Programming Languages of Tomorrow, Effective Design, .NET, The Rise of Ruby.
-
/articles/agile-version-control/en/smallimage/versioncontrol.JPG)
Version Control for Multiple Agile Teams
When several agile development teams work on the same codebase, how do we minimize chaos, and ensure there's a clean, releasable version at the end of every iteration? Here Henrik Kniberg outlines the scheme used in "Scrum and XP from the Trenches". This paper is not so much for version control experts as for the rest of us, who just want to learn simple and useful ways to collaborate.
-
/articles/agile-people-facilitation-skills/en/smallimage/DevelperAbuseMatthew_small.jpg)
Help Your Teams Trade Cubicles for Communication Skills
The Agile “self organising team” paradigm demands new skills of team members – including the people skills for which they may once have depended upon their Project Managers. Far from being redundant, management can now play an important role in helping teams learn new ways to communicate and collaborate. This article proposes some strategies for imparting new skills and suggests some resources.
-
/articles/better-best-practices/en/smallimage/dan_north.jpg)
Better Best Practices
Organizations often introduce Best Practices as part of a change program or quality initiative. These can take a number of forms, from cheat sheets to full-blown consultant-led methodologies, complete with the requisite auditing and accreditation. In this article, Dan North shows how best practices can not only fail to help, but even have a severe negative impact on your top performers.
-
/articles/lean-muda-muri-mura/en/smallimage/muda-muri-mura.png)
The Three M's - The Lean Triad
The discussion of applying lean principles to software development has largely focused on identifying and eliminating waste (in Japanese: muda). Lean Thinking equally aims to remove overburden (muri) and unnecessary variation (mura). Roman Pichler discusses the relationship of the "three M's" and proposes to eliminate overburden as the first step toward a leaner process.
-
/articles/retrospective-prime-directive/en/smallimage/RetrospectivePrimeDirective.png)
Questioning the Retrospective Prime Directive
The 'Retrospective Prime Directive' is a practice used by many teams as part of their continuous improvement cycle. As outlined in Norm Kerth's book, it is intended to foster the deep learning that is the heart of a retrospective. This article is an enlightening conversation, captured by Linda Rising, between senior practitioners on the benefits and the challenges of using this practice.
-
/articles/process-component-models/en/smallimage/small.png)
Process Component Models: The Next Generation In Workflow ?
Tom Baeyens, founder of JBoss jBPM gives his view of the state of the BPM / workflow market and introdces a new type of workflow technology called process component models.
-
/articles/hiranabe-lean-agile-kanban/en/smallimage/Fig5_task-board_tiny.jpg)
Kanban Applied to Software Development: from Agile to Lean
In this InfoQ article Kenji Hiranabe applies lessons learned while working with Japanese manufacturers. While many Agile teams are optimizing only a portion of the value stream, Hiranabe proposes a simple way to adapt lessons from Lean Manufacturing's "Kanban" visual tracking system to make process visible to more of the organization, for better communication and process improvement.
-
/articles/patrick-smacchia-interview/en/smallimage/image_ndepend_ver2 6.jpg)
Talking .NET Code Analysis with Patrick Smacchia
Patrick Smacchia is a Visual C# MVP with over 15 years of software development experience. He is the author of Practical .NET 2 and C# 2, books about the .NET platform. He has worked on software in a variety of fields including the stock exchange at Société Générale and a satellite base station at Alcatel. He's currently the lead developer of the tool NDepend.