Enable brands to reach highly targeted users at scaleReally know the make-up of your audience in more detailNarrow-slice your audience into discrete addressable segments to give greater value to each impressionWe’ve integrated into the main DSPs, including AppNexus, andDoubleClick Ad Exchange, Invite MediaWe’ve integrated into DFP for your direct buysWe’ve created the patendedVisualDNA visual quiz, which collects audience data at scale through a fun and engaging image-based quiz. 85% completion rate.
First implementation September 2005I have championed, implemented and maintained on-premises and Studio Atlassian products in all my last 3 jobsAustralian company1st job JIRA and Confluence2nd job full Atlassian suiteCurrent job JIRA StudioNo formal training – maybe that would help?
I had to provide overview of per user cost for Standalone vs Studio vs existing trackerWith modest growth, regular updates and yearly licensing fees, cost is similar.JIRA Studio doesn’t include overhead of server administration, patching, etc.Nb. Spreadsheet can be replaced with dot point overview of cost comparison over time if necessary, less emphasis on actual costs, more on comparison and less overhead
Things that I had to consider, and provide solutions for, at my current company.Moving a large repository > 5GMigrating a non-confluence wiki – eg. MediaWiki, Google SitesExternally hosted source code – ‘Making the switch to JIRA Studio’ webinar answered many questionsCan’t use your own source repository as MasterCan’t use plugins – long wait for requested pluginsEg. Confluence – Numbered Headings – important for acceptance, just one more excuse for Office-lovers to push backGoogle Apps integration is awesome – makes adding new users a breeze.Some users are hesitant, but come around after using it for a few weeks.Learning curve can be steep.Cannot underestimate importance of a gradual migration plan to introduce development team to new features, rather than BigBang approach.Email > JIRA is good for people who ‘just don’t have time’Custom forms also
Developers want a clear picture of what they’ll be working on in a SprintFreedom to pick up unassigned tasks themselvesCommunication within the teamSys Admins wantControl releases of code to different environmentsEnforce quality and stabilityManagers wantSee workload of developersAbility to plan releases and prioritise new featuresTrack velocity and know ahead of time if a release date is at riskStakeholders wantTo know when a feature will be liveMonitor project at a high levelConfidence that a project is on track
UsingPhing as an ant builder after mention in forumRequiring JIRA ticket number in commit message with precommit hook python scriptSimple check – could be more complex with existing plugin (Commit Acceptance) or more work on Script and API integrationCode reviews using crucible, setting aside time can be difficultTracking velocity, risksStartup environment means goal posts can move regularilyImportant to identify ‘surprises’ and revaluate roadmap – we use labels and produce reports to show how scope and/or direction changes have affected roadmapAlso use Greenhopper to help Bus Dev how to reprioritise based on resources and existing estimatesPanic Status board shows project progressCurrent issues being worked onNumber of tickets remaining in current sprintCustom dashboards for QA staff to prevent losing ticketsmake sure QA workload will not put the release at risk
Many different Ad Campaign systemsDoubleclick for PublishersAd ExchangeApp NexusMore I don’t even know aboutNo centralised management systemCustom app built to enter Campaigns and monitor Contextual Targeting performanceRather than build our own workflow management system, tap into power of JIRAPush Campaigns to JIRA via APIUtilise JIRA to monitor and prioritise CampaignsTraffickers prefer the centralised approach, even though there is some overheadProvides historical insight into how a Campaign changes, eg. Client spend, performance, etc.Could be better with on-premise, ability to hook into Campaign Management API’s in vendor apps
JIRA Studio at VisualDNA
JIRA Studio @ VisualDNA<br />Atlassian User Group - London<br />
A brief history<br />5+ years using JIRA as a Developer<br />3 years as a Tech Lead / Project Manager<br />Started out with JIRA 2.6 implemented in a Java web-app development house with 20+ developers across multiple projects<br />Currently managing LAMP project with 10 developers<br />
Considerations and blockers<br />Migration tasks<br />Internal data privacy policies and legals<br />Feature/customisation options<br />Performance (UK -> Contegix)<br />Google Apps<br />Getting user acceptance<br />Handover, training “If it’s not in JIRA, it doesn’t exist”<br />
Agile Project Management<br />phing integration<br />Commit triggered builds<br />Continuous integration<br />Regular code reviews <br />Tracking velocity and identifying risks early<br />Activity Stream RSS in Growl<br />Status Panic board using JIRA API<br />SCRUM or Kanban – let the project choose<br />
Online Ad Campaign Management<br />Centralised campaign management across multiple service providers<br />Custom workflow specific to needs of Clients and Traffickers<br />Media Management<br />Campaign prioritisation via calendar view<br />Integration with custom app via SOAP API<br />
What would make it better<br />External !hosted code repository<br />Contegix SVN as slave<br />Per-instance plugins<br />Git support<br />Custom fields<br />