We're holding an Atlassian Doc Sprint on 22-24 February. You may have already heard about it. This is a quick reminder to the people who are coming and an invitation to join us if you haven't already.

What will happen in the doc sprint? We'll cloister ourselves in a room with some computers, some geeks and plenty of chocolate. After three days, we'll emerge with lots of shiny new tutorials plus the accompanying plugins and gadgets. And we'll be a lot wiser than when we went in. It's a bit like Big Brother but with open doors. The biggest loser will be the one who eats the least chocolate.

We already have a number of people coming and a plan for the tutorials we want to develop. Our schedule is shaping up nicely.

Want to join us? Come play with the Atlassian tech writers. Grab a chocolate middle name while there are still some left and sign up.

Algorithmic Trading Accelerator enables Banco Fator clients to develop customized strategies BEDFORD, Mass., Feb 08, 2010 (BUSINESS WIRE) -- Progress Software Corporation (NASDAQ: PRGS), a leading software provider that enables enterprises to be operationally responsive, today announced that Banco Fator Corretora, a Brazilian bank and brokerage firm, has deployed the Progress(R) Apama(R) Algorithmic Trading Accelerator. The Apama Algorithmic Trading Accelerator will play a critical role in Banco Fator's new electronic trading strategy, enabling it to more effectively develop high frequency, proprietary trading tactics, rapid customization, and low latency execution of trades on behalf o...

Ingres Corporation, the leading open source database management company and pioneer of the New Economics of IT, announced today that Roger Burkhardt, president and CEO of Ingres, will participate in an InformationWeek virtual event this week titled, "Modernizing IT Governance, Risk and Compliance to Accelerate Flexibility and Visibility." Burkhardt joins as part of a panel on "How to Prepare for a GRC-enabled Cloud: Understanding New Requirements Around Building Stronger Governance in the Public Cloud."

One of the biggest challenges we face in IT is demonstrable & measuable ways to access the quality of IT specifications.

So, it was extremely refreshing to find a great article just published this week over at www.ModernAnalyst.com titled: ’ Using Extreme Inspections to Significantly Improve Requirements Practice’.

The article focusses on applying Quality Assurance techniques to IT documentation. It’s written by German engineer Rolf Goetz, who has obviously been at the coal face and clearly appreciates many of the challenges we all face in establishing more empirical ways to improve process.

Much of what Rolf talks about leverages work from Tom and Kai Gilb and others.

What I found refreshing, is that the article shines a light on the area of quality, similar to our mantra at VisibleThread. As ModernAnalyst (where this article was published) is a relativly mainstream portal for BAs, highlighting the value of inspections to this much wider audiance is great to see.

The emphasis in the article is on collaborative inspections. Rolf and indeed many of the proponents of these techniques, prefer the term ‘inspection’ over ‘reviews’, specifically suggesting ‘inspection’ of a random set of document pages yielding clear metrics around defects that can be extrapolated to the rest of the doucment(s).

I’m not so sure I care as much about the nuances of terms like ‘inspection’ vs ‘review’. I do however very much agree with the notion of spot checking a random sampling of document pages frequently rather than taking a more big bang ‘gated review’ approach. The latter is by definition somewhat more reactive and less effective that the former. Either approach however is preferable to the status quo in many organisations that we come across, i.e. little or no formal review.

So, whether we have frequent inspections or more back ended review of specifications, any kind of early intervention during the analysis phase and formal/informal review or inspection process is to be heartily welcomed. Too often, many organisations do not have even rudimentary vetting/validation procedures in place.

What was doubly exciting for me in this article is that you see the actual ROI of inspection in clear terms. Utilising the approach of ‘extreme inspection’ in one case Rolf cites, we see a reduction in the number of defects per page by 50%. Clear empirical evidence of actual defect reduction as a consequence of inspections in real projects is hard to come by and so Rolf’s case studies are useful to consider.

Broadening out the discussion; we’re currently working with a number of major customers especially in the financial services sector & without exception, the key goal is to establish an effective review (inspection) process backed by automation and very clear metrics.

In this respect, Rolf’s article is timely and very welcome in that it shows clear evidence in a ‘real-world’ example of what is possible from a defect detection perspective in specifications, albeit in a manual way. We are seeing that automation via VisibleThread can substantially magnify the efficiency of the rate of discovery of these defects, indeed often allowing inspection where heretofore resourse pressures have made it difficult to pull off.

I’ll be interested to see more of this kind of of coverage in the main stream media. My hope also is that VisibleThread can allow wider exposure and adoption in a meaningful way of the types of techniques described. Now there’s a very exciting thought…

If you’re interested in looking into this area more, Tom Gilbs work can be found at: http://www.result-planning.com/Requirements and Niels Malotaux at http://malotaux.nl/nrm/pdf/ReviewInspCourse.pdf

Fergal.

I was fortunate enough to catch up with Tarun Upadhyay after he got back from a business trip to India. Tarun is co-founder of hCentive and currently serves as the CTO. hCentive helps make health expenses easier to manage for end consumers. From the begining, hCentive chose JIRA Studio as the hosted software development suite of choice because it allowed them to develop in the USA and India.

hCentive at a glance

• Founded: 2009
• Headquarters: Virginia, USA
• Employees: 19
• Number of offices: 2 (USA and India)
• Number of customers: Product is under development, none yet
• Products used: JIRA Studio

The interview

Tell me a little about hCentive
hCentive is disrupting health care by letting people share their health care expenses in an anonymous way and, in the process, creating tools and information that can allow people to:

• reconcile their health care bills
• find an affordable health insurance plan
• search for high-quality and right-price doctors, medicines and procedures available to them
• decide their FSA/HSA limits and file claims for them automatically

When did you start using Atlassian tools?
We were using Atlassian products at my last company, so it was obvious and, almost natural, for us to continue using Atlassian products here. We were using the same tools that make up JIRA Studio now (JIRA, Confluence, Subversion, GreenHopper). We had also worked with Rally, Serena, and IBM software in the past. When we started hCentive, we evaluated all of these products again, but ultimately went with JIRA Studio.

Why did you pick JIRA Studio instead of the a la carte tools?
One big thing for us was having a hosted solution. We are a fully "clould-served" company — in the sense that we do not have any servers in our local offices (just folks with laptops), so we were looking for a solution that we didn't have to host internally.

An important aspect of cloud-hosted solutions is the price. We are a young compnay and we did not want to pay an upfront fee. We are more comfortable with long-term, smaller monthly fee models.

Also, our teams are distributed across multiple offices and we wanted a set of tools that work great together for an agile team that is working in a distributed environment.

JIRA Studio scored over the other products we evaluated. Serena came very close, but one big leg up which Atlassian has is the fantastic level of support you guys provide and how quickly you answered our questions and helped us set up right away.

Who uses JIRA Studio and what are they primarily using it for?
Everybody in the company uses JIRA Studio. Different people use it for different things. Everyone at least uses JIRA and Confluence. Confluence is used from our developers down to our finance person and our office managers. JIRA is used for everything from office management issues to core product development. Subversion, FishEye, and GreenHopper are used primarily by our development and QA teams. GreenHopper is actually used quite a lot.

Are people using it in ways you hadn't expected?
To start with, people were using JIRA Studio in the way we expected, but over time, we have seen a variety of different patterns which we didn't anticipate. For example, one challenge for us was how to do daily stand-ups since we are distributed between the US and India. GreenHopper was amazingly useful there; our head of engineering created some OpenSocial dashboards in JIRA and GreenHopper to figure out what people had done in the last 24hrs which makes running standups a breeze. Another interesting thing we have done is to use the OpenSocial gadgets to integrate our dashboards with Google's Gmail. A lot of people started accessing JIRA from inside Gmail which we found very interesting and we didn't anticipate.

Were there adoption challenges in terms of getting people into JIRA Studio?
We anticipated that people would have some trouble, but people got it very very quickly. No one in the engineering group had issues, but even people who are less technical also 'got it' pretty quickly which was pretty impressive.

What kind of feedback have you heard from your staff regarding JIRA Studio?
We have heard only good things, especially in terms of customization options.

Any follow-up comments?
Atlassian is a great company and the tools you develop are excellent for distributed teams. You guys really make it easy and you really get how distributed teams work. JIRA Studio perfectly fits our company which must have a hosted solution.

Thanks Tarun!

With so many Atlassian blogs, we like to regularly post a "blog roundup" (just like Balsamiq does). Here is a summary of just a few of the posts we wrote in the last couple weeks:

JIRA 4.0 Gadgets on the iPhone. You may recall a recent post in which one of our developers talked about his plugin for JIRA that provided a cleaner UI when accessed via iPhone. Andreas is at it again, this time tackling the problem of viewing JIRA 4.0 gadgets while on-the-go. Read more.

Social Media Monitoring in the Wiki. An incredibly useful macro that often goes unnoticed is the Widget Macro. In short, it allows you to embed multi-media content from other web sites into your Confluence page. Read more.

Get product training at Atlassian Summit 2010. At Atlassian Summit 2009, the training courses sold out due to very high demand. This year, at Summit 2010, we've added more courses to better meet demand. Read more.

Webinar Recording: Zendesk integration with JIRA. Last week, I was a guest on a special Zendesk integration webinar talking about integrating your Zendesk with Atlassian JIRA. Read more.

Video: JIRA Bridge for HP Quality Center. David Brown of Orasi presented on the JIRA Bridge for HP Quality Center. This is an enterprise-class integration solution that enables organizations to harness the full potential of JIRA and HP Quality Center software. Read more.

Want to follow all the stories as they happen? Read and subscribe to these blogs:

• JIRA blog RSS
• Confluence blog RSS
• Dev Tools blog RSS
• News blog RSS
• Developers blog RSS
• All blogs RSS

Prefer Twitter? You can follow us here.

CppChecker is a smart and fast checker for C/C++ Files. It uses the outputs generated by gcc, PC-Lint or doxygen and generates markers. The markers are intuitively set, so that in most cases the marker corresponds to the location where the actual ...

Dynamic invariant detection runs a program, observes the values that the program computes, and then reports properties that were true over the observed executions. Daikon can detect properties in C, C++, Eiffel, IOA, Java, and Perl programs; in s ...

Splint is a tool for statically checking C programs for security vulnerabilities and coding mistakes.

Squale is a qualimetry platform that allows to analyze multi-language software applications in order to give a sharp and comprehensive picture of their quality.

Gendarme is a extensible rule-based tool to find problems in .NET applications and libraries. Gendarme inspects programs and libraries that contain code in ECMA CIL format (Mono and .NET) and looks for common problems with the code, problems that ...

Yasca consists of two components: * a framework for conducting source code analyses, and * an implementation of that framework, leveraging custom plugins, FindBugs, PMD, and Jlint Yasca is a command-line tool. Just point it at your code base and ...

A tool for monitoring traceability between requirements and Java code. Create a traceability matrix using annotations. Report format: HTML.

PHP Parser analyses PHP scripts including all included files and checks whether variables, constants, functions and classes are both used and defined. The script displays either only errors, a complete data list or the fully annotated script.

jUML is a UML diagram application capable of reverse engineering Java source code to create relationship diagrams, source code generation based on a user created UML diagram, and saving/restoring of jUML projects.

Shiny is a lightning fast, fully documented & by-far-easiest-to-use C/C++/Lua profiler with no extensive surgery. Results are smoothed & shown in run-time as a call-tree or sorted-by-time.

UCDetector (Unnecessary Code Detector - pronounced "You See Detector") is a eclipse PlugIn tool to find unnecessary (dead) public java code. For example public classes, methods or fields which have no references. UCDetector creates markers for th ...

This is a guest blog post from the Atlassian product training team leader, Stafford Vaughan. At Atlassian Summit 2009, the training courses sold out due to very high demand. This year, at Summit 2010, we've added more courses to better meet demand.

While our development teams have been busy adding features to our products, the training team has the task of ensuring our customers get the most out of the products. Did you know that since 2006, over 5000 participants from 350 companies have participated in Atlassian training courses? We've compiled a few simple reasons why we think you should get involved in a training course at the 2010 Summit.

• Training is cheap. Cheaper than usual, in fact. The usual rate per attendee is $750, but we're reducing that to just $249 for one course, or $400 for two courses.
  
• Training is more personal. At the Atlassian Summit you'll have the opportunity meet the trainers face-to-face.
  
• We're adding a track with Atlassian plugin development courses. This is a totally new set of courses that will be launched at the 2010 Summit.
  
• Something for everyone. Whether you're a first-time user or an experienced administrator, we're running a range of training courses to cater for all attendees.
  
• Learn from the experts. Each of our trainers has had years of experience in the field, and we're happy to talk about those experiences and best practices.
  
• Becoming a development pro. Improve your chances of winning Atlassian's 2010 Codegeist competition by getting development tips from some of our most experienced plugin developers.
  
• Four years in the making. We first delivered training in 2006, and the course materials are the result of constant improvement over that time.
  
• Learn about the latest features. We'll be delivering training on the latest product versions at the Summit, so if you want to know what has been updated recently, it's one of the best overviews available.
  

And if that isn't enough to convince you, check out our extensive range of customer testimonials about our training.

If you can't make it to the Summit, you can also contact our team at training@atlassian.com to get a training session delivered at a time that suits you.

We look forward to seeing you in a training course at the 2010 Summit!

It has been way to long (besides yesterday) since we shared some NCover perspective about where we are headed with the next few versions that we have rattling around in our heads.

Sure, it's going to be cool. Maybe that whole "better than sliced bread thing". But the reality is that it will only get that way with your input and suggestions.

We want feedback...

So light up the conversation pipeline.

conversation@ncover.com

Tell us how you are using the platform. We want to know.

• Are you storing your NCover configuration in source control and having your developers pull down these setting?
• Do you have a workflow in place to merge together all testing activity across developer and testing roles?
• Are you using our control filters to divide large amounts of metrics into sizable reporting clusters that can be delivered to different management roles?
• What is your "coolest" NCover innovation yet? Your secret formula for deploying NCover?

Also, tell us what you want in our next versions? We want your feature included.

• Do you want a plug-in to Visual Studio? (Are you planning to upgrade to VS2010?)
• Do you better, faster access to all the data that we are collecting?
• Do you need to deploy and manage enterprise solutions more effectively?

We listen. You don't have to shout (although that could be fun). Just tell us about your dream product.

Company Extends Its Ability to Meet Real-Tme Analytics Processing Needs of Enterprises, in Financial Services and beyond