News & Insights

The Connamara Client Engagement Philosophy – Part 6

Philosophy 5:

Decline projects when the client can’t grasp the concept of iterative releases (no big bangs)

Some of our potential clients want to give us a fully specified project to undertake, where the expectation is that we build to that specification and deliver in one big bang a finished product.

When we see this, we immediately feel that there is a mismatch between our development methodology and the client expectations. A client who thinks this way is assuming that they know 100% what problem they are trying to solve or what opportunity they are trying to capture.

Our approach to delivering solutions to our clients is to assume that neither Connamara nor the client 100% understand the problem or the opportunity and that the client is willing to learn and adapt along the way to deliver a better solution. To play to this assumption of continuous learning during a project, we break the project down into smaller amounts of work that march us toward the solution. Each of the smaller units of work is designed to deliver some value to the client either through delivered functionality or better knowledge as to the problem at hand. This approach affords Connamara and the client the optionality to adjust course.

We feel that delivering value in smaller iterations is the best approach for creating custom solutions for our clients. When a client insists on a big bang delivery or is not amenable to our approach we will decline the project.

Related Reads

Embracing the Remote Revolution: Our Journey as a Remote-First Company

Labor Day Special: Celebrating a Work Culture That Knows No Boundaries As we gather around the virtual breakroom on this.

25 Business Lessons from 25 Years in Business

We reached out to our team members for timeless lessons learned in 25 years in business.

Unveiling Our Next Chapter: Discover Connamara’s Revamped Website and Brand Identity, Celebrating 25 Years of Excellence 

You may have noticed that we recently changed our look. After months of designing and planning, we’re excited to unveil.

Behind Connamara’s Code: Mike Gatny, Part 2

In Part One of our interview with Mike Gatny, VP of Engineering & Head of Sales Engineering at Connamara, Mike detailed what.

Tips from a Work-From-Home Hipster

I’ve been posting silly GIFs and videos on an internal Slack channel at the beginning of every week for I.

Why Connamara Supports Recovery on Water (ROW)

There is no such thing as a bad time to give back to your community. But with October being Breast.

Why We Chose Our Company Values — and How We Live Them

The term “values” is overused and frequently misused in business today. While values are certainly crucial to any company, too.

Get Your FIX: Why (and How) Connamara Supports QuickFIX

The QuickFIX open source project is an important part of what we do at Connamara, and has been for nearly 20 years.

The Connamara Client Engagement Philosophy – Part 5

Philosophy 4: Identify and explain project risks to the client before accepting a project All software projects entails risk. Be.

The Connamara Client Engagement Philosophy – Part 4

Philosophy 3: Only accept projects where there is a clear understanding and agreement of the features of the software to.