Making the Switch to JIRA Studio

37
Making the Switch to JIRA Studio Jesse Gibbs & David Yu, Atlassian Jim Drewes, Contegix Bryan Schmidt, Intelligent Insites Aaron Roller, Akuacom Alex Koloskov, Reaxion

description

Making the Switch to JIRA Studio. Jesse Gibbs & David Yu, Atlassian Jim Drewes, Contegix Bryan Schmidt, Intelligent Insites Aaron Roller, Akuacom Alex Koloskov, Reaxion. Agenda. Studio Summary Unique Features Latest Release How do you switch? Contegix hosting summary - PowerPoint PPT Presentation

Transcript of Making the Switch to JIRA Studio

Page 1: Making the Switch to JIRA Studio

Making the Switch to JIRA Studio

Jesse Gibbs & David Yu, AtlassianJim Drewes, Contegix

Bryan Schmidt, Intelligent InsitesAaron Roller, AkuacomAlex Koloskov, Reaxion

Page 2: Making the Switch to JIRA Studio

Agenda

• Studio Summary– Unique Features– Latest Release– How do you switch?

• Contegix hosting summary• Customer migration stories• Q&A

Page 3: Making the Switch to JIRA Studio

Housekeeping• All phone lines are muted• Submit the questions via

GoToWebinar any time– Indicate panelist

• e.g. “Jesse – When is the next Studio release?”

• Q&A at the end• Recording will be available

Page 4: Making the Switch to JIRA Studio

JIRA Studio

Hosted, fully-integrated

Page 5: Making the Switch to JIRA Studio

JIRA Studio – Concept to Launch

Tools for:• Reqs, specs, backlog• Release & Iteration Planning• Project tracking• Coding & Debugging• Testing• Code review• Technical documentation• Support

Page 6: Making the Switch to JIRA Studio

JIRA Studio – True Collaboration

• Developers– Coding– Test automation & CI– Code review

• Managers– Project Planning– Tracking & reporting

• Product Owners– Backlog– Requirements– Release Planning– Launch planning

• Contributors– Docs, training material

• Stakeholders– Visibility

Page 7: Making the Switch to JIRA Studio

JIRA Studio – Unique Features

Unified Quick Navigation & Search

Page 8: Making the Switch to JIRA Studio

JIRA Studio – Unique Features

Automatic linking– Issues– Wiki pages– Changesets– Reviews– Build plans– Build results

Page 9: Making the Switch to JIRA Studio

JIRA Studio – Unique Features

Update issues with SVN commit comments– #time, #comment, #<transition>

Page 10: Making the Switch to JIRA Studio

JIRA Studio – Unique Features• Unified Activity Streams

Page 11: Making the Switch to JIRA Studio

JIRA Studio + Google Apps

Page 12: Making the Switch to JIRA Studio

JIRA Studio 2.2 – Now Available!Updated Apps• Fisheye 2.2• Crucible 2.2• JIRA 4.1• Greenhopper 4.4Other App Versions• Confluence 3.1• Bamboo 2.5• Subversion 1.6.5

Page 13: Making the Switch to JIRA Studio

Migrating to JIRA Studio

Migration features• Import source• Import issues

– JIRA– CSV

• Import wiki

Limitations• External LDAP• Limited plug-in support

– Managed upgrade schedule

• No terminal access• I18n

Page 14: Making the Switch to JIRA Studio

Contegix – JIRA Studio Hosting

• Atlassian managed hosting partner• Provide all of the infrastructure that powers

JIRA Studio

Page 15: Making the Switch to JIRA Studio

Contegix – Studio Infrastructure

• How do Atlassian and Contegix integrate?

Provisioning

Page 16: Making the Switch to JIRA Studio

Contegix - Hardware

Page 17: Making the Switch to JIRA Studio

Contegix – Network & Facilities

• Located in St. Louis, Missouri, USA• 5 Network Carriers (XO, Level(3), Sprint,

Verizon, WilTel) – BGP Routed• Two power feeds with automatic failover• Backup generators capable of running

indefinitely• Everything is on UPS power

Page 18: Making the Switch to JIRA Studio

Contegix – Security

• Instance– Each customer has their own VM.– Shorewall software firewall.– No shared Databases.– Data stored on highly redundant RAID-50 SAN.

• Facility– Security cameras throughout data center.– Secured lobby.– Code access required to access upper floors of building.– Double-door man traps requiring a biometric scan and two proximity

badge swipes to enter any data center.

Page 19: Making the Switch to JIRA Studio

Contegix – Backups

• Local Backups– Weekly SVN Dump– Nightly DB Dump– Weekly Attachments Copy

• Instance Backup– Snapshot of entire instance taken nightly and

stored on SAN

Page 20: Making the Switch to JIRA Studio

Contegix – HA/DR

• Instances aren’t tied to specific hosts.• All data stored on SAN rather than local disk.• If a host fails, instances are automatically

restarted on another host.• Mechanisms available to pull your data off.

– SVN dumps– WebDAV

Page 21: Making the Switch to JIRA Studio

Customer Stories

• Bryan Schmidt, Intelligent Insites• Aaron Roller, Akuacom• Alex Koloskov, Reaxion

Page 22: Making the Switch to JIRA Studio

• Product:– InSites Enterprise

Visibility Platform

• Location:– Fargo, North Dakota

• Established in 2007• Team size: 24

InSites Applications

Real -Time Location Systems

Page 23: Making the Switch to JIRA Studio

Automating the Healthcare EnterpriseClinical IT SystemsClinical IT Systems Operating Room IS Emergency Dept IS Other Departmental IS Electronic Medical Record Positive Patient ID

Asset ManagementAsset Management Tracking, Locating, & Status Automated Work Orders Theft/Loss Prevention Inventory Tracking Room Management

Operational WorkflowOperational Workflow Bed Management Transport Management Unified Messaging/Alerts Reporting & Analytics Automated Task Routing

Patient & Staff SafetyPatient & Staff Safety Staff Panic/Duress Emergency Response Wireless Nurse Call Wander Prevention Infant Abduction

Building SystemsBuilding Systems Temperature Monitoring Door Locks/Access Control Audible and Visual Alarms Telemetry Fire Alarms

PassivePassiveDataData

Page 24: Making the Switch to JIRA Studio

• What lead us to use JIRA studio?

• Hosted solution• Support/Maintenance• Integrated with IntelliJ• Had all the features we

needed for our small development team

Page 25: Making the Switch to JIRA Studio

• How do we like JIRA Studio?

Benefits:•Hosted•Accessible from anywhere (home/office)•IT support •Supports a growing team•Integrated Subversion has worked well for us

Page 26: Making the Switch to JIRA Studio

• How do we like JIRA Studio?

Improvements:•Query tools•Performance slows when more than 3000 issues•Planning for feature work versus bugs

Page 27: Making the Switch to JIRA Studio

Akuacom – The Company

• Small “Green Tech” start-up company• Software manages energy consumption for buildings

• Recently acquired by Honeywell• Development team of 4 rapidly growing to 20• Remote team of developers in China• www.akuacom.com

Page 28: Making the Switch to JIRA Studio

Aaron Roller – AAWhere

• Started consulting for Akuacom in January• Assisted in preparing for Honeywell acquisition• Architect/Developer/Co-Founder of MotionBased.com

• Architect/Manager of Garmin Connect• JIRA/Confluence/Hudson/SVN/Maven @ GC• Tony Pelosi provided Agile Project Management• AAWhere products use JIRA Studio + Google Apps• www.aawhere.com

Page 29: Making the Switch to JIRA Studio

Old Development Environment

• JBoss/EJB/JSF/Web Services• ANT Builds / CVS• Media Wiki / Bugzilla • Hudson (recent addition)• Eclipse/IntelliJ or any IDE

Page 30: Making the Switch to JIRA Studio

New Development Environment

• JIRA Studio (Using every App)• Maven Builds / Nexus Repository Mgr.• Agile process• No flaky VPN• 10 Developers / 5 Collaborators and growing

Page 31: Making the Switch to JIRA Studio

Best of JIRA Studio

• Instant Software Start-Up • Imports from Legacy Tools worked well• Seamless Integration across Studio Apps• Activity Stream gives the pulse• Automatic Upgrades & Expert Admins• Integration with Cloud Computing (Bamboo)• Faster connection for China Team/Remote Dev

Page 32: Making the Switch to JIRA Studio

JIRA Studio Improvements?

• Maven Repository Manager• Better JIRA/Confluence Linking• Support More Plugins• Larger Support Team• IP & Trade Secret concerns for large companies

• Bamboo or Maven doc generator integration• JIRA Studio Growing Pains

Page 33: Making the Switch to JIRA Studio

Next Steps at Akuacom

• JIRA Studio set up a solid foundation• Continue to focus on Agile Development• More use of Greenhopper• Add system testing to Bamboo• Requirements in Confluence• Hire more people• www.akuacom.com

Page 34: Making the Switch to JIRA Studio

Mobliss Inc.Trademarks: PressOK Entertainment and Reaxion

• Mobile games/apps developer and publisher• Size of team - ~35• 3 offices – Seattle, Moscow, Minsk

Page 35: Making the Switch to JIRA Studio

War on IT

• At some point, we had 3 IT administrators and ~20 servers

• That was way too much• We declared a war on IT – no more servers• We migrated:

– E-Mail/Calendars to Google Apps– VCS/Issues/Wiki to JIRA Studio– Production servers to Amazon

• And we’re doing great!

Page 36: Making the Switch to JIRA Studio

Dark Side

• WE LOVE JIRA STUDIO! – Doesn’t mean that it’s perfect though. Nobody is.

• Things that may become problems:• VCS: Subversion is the only choice, right now• VCS: Forces certain structure of repository, may not be

compatible with existing structure• Google Docs Integration: Great idea, but needs improvement• In general, JIRA Studio is updated few months after

standalone versions. For geeks it’s pretty tough.• Plug-ins installation has to be performed by Atlassian

support (which is very responsive, by the way)

Page 37: Making the Switch to JIRA Studio

Any Questions?

JIRA Studio

Recording available soon!