Attivio | Unified Information Access Blog

Attivio is a huge fan of Atlassian Software and the Atlassian product suite as their products provide the foundation on which we've built our development process. Their upcoming Atlassian Summit will be a showcase of new features, product plug-ins, and practical implementation advice and customer stories. I'm very excited to have the opportunity to speak at the Summit and share our real-world experiences with Agile development and Atlassian's Tools.

My talk will cover Agile quality including our general approach to QA, and how we've used Atlassian's tools to build an integrated, efficient QA environment that produces very high quality releases. I'll break down our process into three main pieces: continuous integration, code coverage and unified testing.

Are you a fan of the Atlassian tool set? We are! If you're planning on attending the Atlassian Summit on May 31st in San Francisco make sure you check out the session that is being presented by Attivio's resident expert, Rik Tamm-Daniels, VP of Engineering.

Monday 4:45pm

High-Octane Dev Teams: Three Things You Can Do To Improve Code Quality
Bugs are a big problem. But we know they are inevitable. Finding bugs fast and dealing with them early results in higher quality code. This session explores the practical approaches to improving code quality with automated testing, continuous integration and effective code review.

Atlassian Speaker: Brendan Humphreys
Customer Speaker: Rik Tamm-Daniels of Attivio

Key Takeaways:

• Overviews of key concepts and how to get started

• Walk-throughs and configuration tips for Clover, Bamboo and Crucible

• Stories from the trenches

Click here to check out the event's website

This is the first in a series of posts describing Attivio's approach to Agile from an implementation perspective. Requirements management is one of the most interesting parts of planning in an Agile environment. The challenge lies in balancing Agile's fundamental acceptance of frequent requirement additions and modifications, against investing time in defining those same changing requirements at a detailed level. This challenge is especially apparent when the scope of your development project is large.

In my first post I described the methodology we use to build software. Now I'd like to explain how we ensure that the software built is of extremely high quality.