Agile Zone is brought to you in partnership with:
  • submit to reddit
Mitch Pronschinske05/26/11
0 replies

Videos: State vs. Interaction Testing & Learning to Love Your Manual Testers

At the 2010 Norwegian Developer's Conference, Hadi Hariri explained state and interaction testing so that developers could use both to their full advantage when building sturdy unit tests.  At another presentation, Karianne Berg showed attendees that manual...

Robert Diana05/25/11
0 replies

Bridging The Technology Communication Gap

Throughout my career, I have been blessed with the ability to effectively translate technology issues to business users. At one point I was even told that I “explain technology to the users in a way that makes sense and does not make them feel...

Steven Lott05/25/11
0 replies

Agility and following a "Strictly Agile" approach

I've seen some discussion on Stack Overflow that is best characterized by the question: "What is Strictly Agile?", or "What's the Official Agile Approach?".Someone shared this with me recently: "Process kills developer...

Giorgio Sironi05/25/11
0 replies

The eXtreme Programming Values

Values are more important than practices: the latter are only an aspect that can change to adapt to people (people over processes, remember?), but they're often the practical (what a pun) aspect of XP and of the Agile credo that is easier to teach. Francesco...

Larry White05/24/11
2 replies

Save the baby code

Code reviews are both a standard part of the development process and the biggest wasted resource in software engineering. Approaches vary from face-to-face discussions to online systems like Review Board.  They share two things: They’re arguably the...

Giorgio Sironi05/24/11
0 replies

How to bomb a technical talk

In the jargon of conference speakers, bombing means presenting a talk which does not go well: content is lost or poorly understood because of the way it is presented, the audience prepares to leave early and in general have an hard time. Scott Berkun points...

Giorgio Sironi05/23/11
0 replies

Practical PHP Testing Patterns: Humble Object

The problem: we have to test a component which is tied to a framework or library. This time we cannot modify its design to aid testability, for example by introducing arguments in the constructor to allow for injection. The Api has to move between the...

Nicolas Frankel05/23/11
0 replies

Vaadin courses on JavaBlackBelt

For those of you who haven't heard of JavaBlackBelt, it's an e-learning community site. Once registered, users can use the site in a variety of ways: First, one can take courses on a variety of programming-related subjects. Then, one can pass exams on...

Daniel Ackerson05/22/11
3 replies

Prerequisites for Continuous Deployment

Although we’ve skirted around the edges of Continuous Deployment on this blog, we haven’t really gone into any details. The main reason for this is simply that neither Matthias nor myself have ever continuously deployed to our...

Israel Gat05/21/11
0 replies

Making Agile Work From Vivek Kundra to Devops and Compounding Interest: Cutter’s Special Issue on Technical Debt

The Cutter Consortium has published a special issue of the Cutter IT Journal (CITJ) on Technical Debt. As the guest editor for this issue I had the privilege to set the direction for it and now have early exposure to the latest and greatest in...

Katie Mckinsey05/20/11
0 replies

Daily Dose: Release of MeeGo 1.2

The much anticipated release of MeeGo 1.2 has officially been announced this week! MeeGo 1.2's OS is home to several reference kernels, including those for the Intel Atom and ARMv7 platform. Linux and Windows are the currently supported platforms.  A Mac OS...

Marco Tedone05/19/11
14 replies

Call to Agile Folks: is There a Need for a Separate QA Team?

Recently I confronted myself (yet again!) with a contradiction between theory and practice. All the Agile books I have read and the courses I've attended and all Agile people I've been speaking to have been saying the same thing: you don't need a QA...

Katie Mckinsey05/18/11
0 replies

Daily Dose: LinkedIn Goes Public!

LinkedIn, the popular social networking site for professionals, is going public! Selling at $45 per share, the 7.84 million shares total to an amazing $352.8 million. Originally, LinkedIn had considered offering the shares at $32-$35 per share. Soon,...

Jim Moscater05/18/11
0 replies

Microsoft Bringing "Ops" into Visual Studio (vNext)

In this week's keynote speech at Tech*Ed North America 2011, Microsoft Corporate Vice President Jason Zander announced the new features for "vNext", the codename they've chosen for the next version of the Visual Studio IDE. The major change to VS...

Jim Highsmith05/18/11
1 replies

Enterprise Agility Generates 30% Higher Profits

“An overwhelming majority of executives (88%) cite organisational agility as key to global success. Other studies support this idea as well: research conducted at MIT suggests that agile firms grow revenue 37% faster and generate 30% higher profits...

Michael Sahota05/18/11
1 replies

Agile – The Good, The Bad, and The Ugly

This is your chance to hear about the Ugly harsh realities, the Bad news and the Good opportunities for Agile. In many ways this concludes the past months series on Agile Culture. Stop reading now if you want to take the blue pill and ignore the harsh...

Mitch Pronschinske05/18/11
1 replies

Go 2.2: Free Community Edition No Longer Requires a License

When it comes to practicing what you preach as a software company, ThoughtWorks Studios is a prime example of an organization that eats its own dogfood.  Before the reboot of their release management software, called "Go" (Formerly...

Israel Gat05/18/11
0 replies

Schedule Constraints in the Devops Triangle

Last week’s post “The Devops Triangle” demonstrated the extension of Jim Highsmith‘s Agile Triangle to devops. The extension relied on adding compliance to the three traditional constraints of software development: scope, schedule, cost. A...

Giorgio Sironi05/18/11
0 replies

Git backups, and no, it's not just about pushing

Git is a backup system itself: for example, you can version your .txt folders containing TODO lists. Since Git version your files just like it does for code, after accidental deletion or modifications it will be able to bring you back.Yet, if you do not...

Giorgio Sironi05/18/11
0 replies

Practical PHP Testing Patterns: Dependency Lookup

How can we substitute real collaborators with Test Doubles, for the purpose of testing in isolation? We have to build a small and handy indirection over the new operator and in general over the creation of objects.Usually we can just introduce Dependency...

Roman Pichler05/17/11
1 replies

Business Analysts in Scrum

A new article on business analysis and agile based on interviews with a group of people including Ken Schwaber, Alistair Cockburn, Ellen Gottesdiener, and myself reminded me to share my thoughts on the role of business analysts in Scrum. But before we...

Michael Dubakov05/17/11
1 replies

Development Practice: Design Ideas Board

Feedback cycles are very important in software development process. To create cool products we need to get feedback as early as possible, and we need this feedback fast. Design Ideas Board is an interesting way to collect feedback from co-workers on...

Esther Derby 05/17/11
1 replies

There’s I(ntelligence)Q, and then there’s I(nfluence)Q

People who work in software are smart people who take pride in their abilities to understand complex information and solve difficult problems. But much of the work isn’t only about smarts. Creating most software requires the help and cooperation of...

Mitch Pronschinske05/17/11
0 replies

Video: The Last Mile - Continuous Delivery at

In this video you'll find a short overview of release pipeline approaches being implemented behind the scenes at use a blend of software engineering practices from the Agile...

Giorgio Sironi05/17/11
0 replies

The 4 rules of simple design

A colleague of mine told me a bit ago that Red-green instead of Red-green-refactor was becoming an issue: many commits where made just when the green bar was reached. A reason for this behavior was the fear of overdesigning the system and code for tomorrow...