Ever considered going hosted? Find out why SaaS may make sense for your development teams. This session shares one customer's experiences with Atlassian developer tools, and their thinking around JIRA Studio and on-demand dev suites. Customer Speaker: Jeff Schnitter of Work Day Key Takeaways: * Best practices for efficient dev teams * Tips and tricks for tuning Atlassian's dev tools suite * Considerations for SaaS dev suites

1. JIRA Studio
Agile Development Suite
Michael Knighten
Director Hosted Services

2. Agenda
Introductions
• Michael Knighten, Atlassian
• Jeff Schnitter, Workday
Overview of Studio (Michael)
Workday - Overview (Jeff)
• Why Studio? (Jeff)
• Challenges & opportunities (Jeff)
Questions (Jeff and Michael)

9. Team

10. Team + Process
Specify
Tasks
Code
Verify
Document

11. Team + Process + Tools
Specify Wiki
Tasks Issues
Code Source + IDE
Verify Review
Document Wiki

12. Benefits of Hosted
Regular upgrades to latest component applications
24 x 7 network and application support
no upfront cost for hardware or license
monthly or annual billing scales with you
up and running in matter of minutes
available anywhere, perfect for distributed teams
hosted and maintained by professionals in state-of-the-
art facility

13. Benefits of Integration
get the latest in Atlassian dev tools features, quickly and
automatically
intuitive hyperlinking to issues, wiki, source files, etc.
single sign-on to entire development suite
special integration points - the NavBar, Activity stream,
SVN commit messages, etc. - all pre-configured and
ready to go

14. New
Price change to $25/user (cut in half!)
GreenHopper agile planning tools now bundled for free
for all Studio customers!

15. Possibilities for Future
Continuous Integration
GIT support
Trac import
Application upgrades: Confluence 3.0, FishEye/Crucible
2.0, JIRA 4.0
New dashboards, gadgets and more

16. JIRA Studio: Why SaaS Makes Sense

17. Introduction
Jeff Schnitter
• Build Engineer, Workday, Inc.
• Responsible for end-to-end maintenance of
JIRA, Confluence, Fisheye, Subversion,
Bamboo.
• Installation, configuration, upgrades, backups,
user-reported problems.

18. About Workday
• Founded in March, 2005, by former PeopleSoft
founder and CEO Dave Duffield, with former
PeopleSoft chief strategist, Aneel Bhusri.
• Develops SaaS solutions for Human Capital
Management, Financials and Payroll.
• 380 Employees, 84 Customers.
• Largest customer: 220,000 Employees.
• Offices in U.S., Germany, Ireland.

19. At Workday we use JIRA for EVERYTHING

20. Workday Build Environment
• As a SaaS vendor, key to our development
procedures is that we must be SAS-70
compliant.
• Our CSO says: “JIRA + Confluence = SAS-70
compliance”
• Requirements documented in Confluence.
• JIRAs created to track completion of work.

21. Confluence Feature Forms

22. Software Versions Per Release
• Tracked in a separate JIRA project.

23. Software JIRA data in Confluence page
• Page is displayed using XSLT macro.

24. Confluence Page for each Software install
• Installers customized for Workday environment.

25. Tracking Patch Builds at Workday

26. Build Project in JIRA
• Only development managers can edit a BLD
JIRA.
• Developers edit the BLD JIRA, link issues that
will be fixed and edit fields to request access for
their team.
• A daemon process (using Matt Doar’s Python
CLI) checks the BLD JIRA and then grants
access to Subversion.

27. Auditing and Automation in the BLD JIRA
• Access requests captured in JIRA change
history.
• All access requests captured in JIRA change
history.

28. Subversion hooks
• Require a JIRA key before allowing a commit.

29. Subversion hooks
• Compare branch to JIRA Fix Version.

30. Subversion hooks
• User must be in JIRA branch commit group.

31. BLD JIRA Workflow
• Bamboo build based on JIRA workflow change.

32. Environment Status in Confluence
• QA environment status pages in Confluence.

33. Bamboo for deploying builds to QA
• Distributed build team (California and Ireland).
• “Follow the sun” development. Work starts in
Ireland, handed of to California.
• Build team struggled to communicate status.

34. Bamboo Build Framework (BBF)
• A build must complete all steps.
• A restarted build will pick up where it left off.

35. Shared build ownership in Bamboo
• Bamboo status makes sharing easy.

36. Build Scripts are stored in Subversion
• JIRAs opened for build failures.

37. Build changes no longer hidden
• All changes “auto” documented

38. Fisheye shows exact change made
• No lengthy emails required to convey changes.

39. SaaS = Save Yer Ass, Anecdote #1
• We were managing our own mail server and
had a shell script coded incorrectly, so our 180
day purge script deleted current email.
• Oh, yeah, and our backups had been failing.
• We lost 5 days of mail.
• Compare that to a 2 hour gmail outage.

40. SaaS = Save Yer Ass, Anecdote #2
• I wrote some clever Ant scripts to manage JIRA
and Confluence upgrades and installs.
• I have a production server and a test server.
• I thought I was on the test server.
• I wiped out the production JIRA database.
• SQL backups had been failing for 6 weeks.

41. SaaS = Cover Yer Ass, Anecdote #2
However, I did survive.
Thank you! Thank you, Atlassian
for XML backups.
Jeff

42. Why JIRA Studio Makes Sense
• It bundles the apps we already use: JIRA,
Confluence, Fisheye, Subversion, Crucible.
• It saves $$$.
• Maintenance, upgrades and support are
simpler.
• Let the experts manage the application. See
previous anecdotes.
• But most importantly . . .

43. Why JIRA Studio Makes Sense (for me)
• It frees up MY time so I can do more important
things

44. JIRA Studio Cost Analysis
• With all the benefits I’d get from Studio I was
willing to pay a certain premium over my current
Total Cost of Ownership of the Atlassian Suite.
• However, in this economy management might
not be willing to pay a premium even for the
huge benefit.

45. JIRA Studio Cost Analysis
Item JIRA On Premise Notes
Studio
Yearly Developer Licenses 25000 0 100 developers
Yearly Collaborator License 10000 0 250 collaborators
Yearly Confluence Maintenance 0 4000
Yearly JIRA Maintenance 0 4000
Yearly Fisheye Maintenance 0 4000
Yearly Crucible Maintenance 0 4000
Confluence Plugins 3750 3750 Gliffy, Greenhopper
Yearly Data Center Fees 0 31200 $2600/mo
Yearly Server Costs 0 10000 3 servers, 10K per server,
depreciated over 3 years
Yearly FTE Support 25000 50000 ¼ FTE for Studio, ½ FTE for
On Premise

46. JIRA Studio Cost Analysis
JIRA Studio On Premise Notes
Totals $ 63,750 $ 114,950 Wow!
• Recall that I was willing to pay a premium over
my current On Premise solution cost.
• JIRA Studio will save my company
approximately 50 K per year!

47. How JIRA Studio frees up my time
Current Open Issues in my JIRA Queue
Upgrade Confluence from 2.8 to 2.10.
Create Disaster Recovery Plan for JIRA and Confluence.
Simulate JIRA and Confluence disaster and enact Disaster Recovery
plan.
Investigate implementing Crucible at Workday.
Investigate why we're getting Nagios alerts about JIRA backup space.
JIRA Attachment backups are failing.
Upgrade Subversion to 1.5.6.

48. What I worry about with On Premise solution
• Uptime – I’m not a performance or network guru.
• Backups – I’m in a constant battle managing the filesystem and
begging for more disk space.
• Performance – Users: “Confluence is really slow today.” Jeff:
“I’m working on 3 builds and I’m NOT a performance guru.”
• Disaster Recovery – Where would I hide if we ever had a
crash that lost data?
• Upgrades – With so many Atlassian products I’m always
upgrading.

49. What I worry about with JIRA Studio
• Confluence Plugins – We love plugins! Can we live with
limited plugins and user macros?
• Trust – You love your teenager, but do you want to hand her the
keys to your car?
• Scalability – Will JIRA Studio scale as our company grows?
• Migration – How can I migrate Subversion, JIRA and
Confluence without major disruptions to users?
• Process Changes – How many customizations will be
affected?

50. What Workday worries about with JIRA Studio
Three main concerns identified by my I/T team:
• Security – Our data must be secure.
• Security – Hang on. Our data must be REALLY secure.
• Security – Did I mention security?

51. Workday wants to be in the “right” headlines

52. Workday wants to be in the “right” headlines

53. Workday wants to be in the “right” headlines

54. SaaS and Security
• Companies are careful about allowing another
company to have access to their data.
• One data breech can spell the end for a SaaS
vendor.
• Workday has been very persistent in working
with Atlassian to ensure data is secure and data
privacy maintained.

55. SaaS and Security
• It can be frustrating waiting for legal and
security teams to verify that a vendor and a
solution is secure.
• I’m grateful for downright paranoia of Workday’s
team verifying security.
• I sure as heck don’t want to be “that guy” who
recommended a solution that made our data
insecure.

56. Summary
• Any loss of control is far outweighed by other
gains.
• Huge savings in moving to JIRA Studio.
• Setup, configuration and maintenance is much
simpler than on premise solution.
• JIRA Studio frees up time to devote to other
tasks.
• Solid team in Atlassian and Contegix behind
Studio.

57. Kudos
• Michael Knighten – Manager of JIRA Studio.
Patiently and thoroughly responded to our
questions.
• Jeff Turner – Technical whiz. Has helped me
with many configuration, migration and setup
issues.
• Contegix – Hosting company used by
Atlassian. They promise (and deliver!) five
minute response time on issues.

58. haveasec.com/summit
SURVEY!!