|
|||
|
In June's issue... Agile insanity, Codegeist winners are revealed, an update on our 20% time experiment and more. Happy reading!
|
||
|
May I have the envelopes, please?
FishEye, likewise, has only had its plugin framework for a few months. Dan Hardiker of Adaptavist was able to get the very first FishEye plugin working, the Developer Report Plugin. Like Ross, he started with a simple reporting framework, but he was able to demonstrate the potential of plugins in FishEye, and point out some valuable directions for further development.
As usual, Confluence was our most fiercely contested category, with almost thirty entries. After much discussion and debate, the Confluence developers selected Martin Breest's Confluence Page State Plugin.
(And, in case you were wondering about those spiffy little product badges sported above, they're part of our new product badge collection.)
|
||
|
JIRA Studio, our latest hosted offering, combines JIRA, Confluence, FishEye, Crucible and SVN via a number of plugins to provide a seamless development environment to the end user. Search is an area where the integration between products has been lacking so far. Each application provides powerful search mechanisms, however there was no global mechanism to search all applications. Implementing global search in Studio proved to be one of the more interesting features I’ve worked on so far. After doing a technical spec I estimated this piece of work would take 81 hours.
|
||
|
Here at Atlassian, we like our Agile methodologies. We like our pair programming. And we definitely like our story cards. Some people think story cards are old school, and that all this "agile" stuff is slight-of-hand. This video proves them ... right.
|
||
|
It's been ten weeks since we started our 20% time experiment at Atlassian, and about eight weeks since the first time someone from marketing asked me "Have we done anything yet?" I think that among some people there was an expectation that we would just turn on the 20% spigot, and out would come a steady stream of new ideas and implementations. Of course, that's not going to happen. 20% of ten weeks gives each developer at most ten working days, and with the effort of having to fit them around already-tight release schedules, I doubt anyone's used up more than half their allotment so far. Most teams were a month or so into the programme before they could spare any significant developer time. Still, we've had some successes already.
|
||
|
Have you seen these awesome Confluence plugins? In minutes you can create and collaborate on diagrams with Gliffy and mockups with Balsamiq:
|
||
|
While I have been long familiar with Design Patterns in software development and find myself using a reasonably broad pattern language in my daily work, I had not until recently been made aware of the Simpleton Pattern. If you do your own research you may be led to believe that Simpleton is an anti-pattern. It has also been noted that Simpleton is best suited to the BBM architectural style. Some engineers at Atlassian maintain that the Simpleton characterises properties of developers themselves rather than of the software. At first it may seem that implementing Simpleton requires great skill and attention to detail. In fact the opposite is true! Simpleton doesn't require special training or framework support. In fact if you look at some of your own legacy code you may be surprised to see that you have in fact unwittingly produced several implementations yourself. I know I have!
|
||
|
Here are a few sites and blogs we've been tagging around the office:
|
||
|
We have tickets to one of the best techical Java and agilty event series up for grabs — let us know if you're interested! Cheers, Your mates at Atlassian
|
|||
|
Other ways to keep on top of what's happening at Atlassian: |
|||
Read or subscribe to our 
See what everyone's talking about on the Atlassian 
Get a