Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Denver Atlassian User Group 062117
Similar to Denver Atlassian User Group 062117 (20)
More from denveraug
More from denveraug (19)
Recently uploaded
Recently uploaded (20)
Denver Atlassian User Group 062117
- 1. JASON GOLDEN • SLALOM PAUL STALLWORTH • UC BOULDER Denver AUG Meeting June 21, 2017
- 2. Sponsor ReleaseTEAM DevOps and SCM experts releaseteam.com
- 3. Next Meeting 7/19 – 5 Min Plugins Share and demo your favorite plugins! Future Meetings: 8/16, 9/12 @ Summit! Sponsor? Contact us! denver_co@atlassianusergroups.com
- 4. Summit U.S. 2017 Atlassian Stack Packaged software suite for Enterprise and DevOps teams, DevOps Marketplace, streamlined pricing https://www.atlassian.com/enterprise/stack Sept. 12-14 San Jose, CA $1,200 Sessions preview at August AUG News Atlassian Playbooks Tool-agnostic techniques Atlassian teams use to do great work https://www.atlassian.com/team-playbook
- 5. Summit 2017 - Convince Your Boss! • Template for download at https://www.atlassian.com/company/ev ents/summit-us/pricing
- 8. MARK ELIASEN RELEASETEAM JIRA and Tempo Timesheets Unify Dev, Ops and Business teams using time tracking and reporting
- 9. Unified Time Tracking with &
- 10. 10 Today’s Presentation Join Mark Eliason from ReleaseTEAM to learn how you can unify Dev, Ops and Business teams using the time tracking and reporting power of JIRA and Tempo Timesheets. Mark has spent the past 18+ years as a DevOps and Software Configuration Management professional. He is a Senior DevOps Consultant with ReleaseTEAM and is Atlassian Certified in JIRA Administration and Agile Development.
- 11. 11 Senior SCM & DevOps consulting since 1999 300+ years combined experience Veteran owned Nationwide services Tool selection, integration Mentoring, training, staff augmentation Administration, installation, customization, upgrades Strong partner alliances Atlassian & Tempo GitHub, GitLab, Perforce, SmartBear, Chef, JFrog and more!
- 12. 12
- 14. 14 Information Overload “It's not information overload… It's filter failure.” -- Clay Shirky
- 15. 15 Application & Device Overload “Happiness is a moment with you without you.”
- 16. 16 Warp Speeds “It never gets easier. You just go faster.” -- Greg LeMond
- 17. 17 Globally Distributed Teams “Globalization has changed us into a company that searches the world… to find… the world’s best talents and greatest ideas.” -- Jack Welch
- 18. Dev + Ops = DevOps But what about the other teams? What about budgets? How long did that take? Where is time getting billed?
- 19. 19 Time Tracking Challenges They’re the same! Information Overload Time accounting for every user for every project for every category Application & Device Overload Time tracking disconnected from issue management Globally Distributed Teams Systems need to become a common language & perform at scale worldwide
- 21. None of these solutions are bad.
- 22. 22 But What Can You Do Differently? TEMPO TIMESHEETS
- 23. 23 TEMPO TIMESHEETS Flexible time tracking features built on top of JIRA Most popular time tracking Marketplace add-on Leverage what you already know & love Provides visibility & insight into where time is spent No more disconnect from Issues Team, Cost Center, Project, Issue and Filter views...and more! Extends time tracking workflows, permissions & access Timesheet approval & rejection, line item metadata, time locks Work on JIRA Server, JIRA Cloud or mobile platforms
- 24. 24 0 2000 4000 6000 8000 10000 12000 14000 16000 18000 vs. The World TEMPO TIMESHEETS Atlassian Marketplace installation data – June 2017
- 25. 25 Aerospace Client – Case Study Existing JIRA customer • 2000+ users nationwide • 200 users in initial rollout • Two offices, 1 hour apart Home grown time tracking “solution” • Poor performance • No history or notifications • No workflow or rejection options • No comprehensive view of information • Time entry in both JIRA & time tracking tool • Intensive month-end data collection & formatting (30-40 hours… every month)
- 26. Demo (almost)
- 27. 27 Data Structure TEMPO TIMESHEETS TEMPO TIMESHEETS Accounts Teams Worklog Attributes Projects Project Permissions Issues Worklogs Groups Workflows Screens*
- 28. 28 Data Structure TEMPO TIMESHEETS TEMPO TIMESHEETS 1h 4h 2h 4h 4h 1h 8h .5h 4h $ $ $ $ $ rejected approved east west
- 29. Demo (for real)
- 30. Thank You! For more information: info@releaseteam.com hmorgan@releaseteam.com meliason@releaseteam.com
- 31. Dinner! Big Daddy’s Burger Bar 100 E. 120th Ave. B-120, Northglenn, CO 80233
Editor's Notes
- https://www.enterpriseirregulars.com/116202/race-pipeline-atlassian-aint-playin-introducing-devops-marketplace/ Boss talking points
- One of the realities of working in the information age is having to sort through more and more data, in both your home and personal lives. You need to make sure you have some way to zero in on what matters – the right information delivered to the right people at the right time.
- Server and desktop applications. Cloud applications. Mobile apps. Desktops. Laptops. Smart phones. Tablets. Even refrigerators these days! Much like the amount of information we have to manage these days, how do streamline what you need and get rid of technology clutter whether you’re at your desk or on the go?
- Faster, quicker, better. Information, application and device clutter can slow you down… so can heavy and/or redundant processes. Do the systems you use help you achieve your goals, or do they hold you back?
- Gone are the days where systems only live within the four walls of your office building. Your co-workers and teams may sit next door, they may be an hour away… or they may sit halfway across the globe. Do your systems suit the needs of an increasingly distributed workforce?
- When we think about DevOps, we often think in terms of engineering, product and service delivery teams… and there are a lot of very commonly used technologies in the DevOps space. Version control, issue management, requirements management, test management, configuration management – they all play a critical role in DevOps, particularly in development and IT-based teams. But what about other teams in the organization and what about the business side of things? The people creating products and services in your organization may not have to directly think about things like budgets or funding sources, but those are always under the hood of any Dev or Ops initiative.
- So we know what types of challenges we face in DevOps. What kind of challenges are there when you start thinking about the time you spend on company initiatives, and how are they different from DevOps? They’re not!
- Earlier, we talked about application and device overload. If you’re using JIRA for issue management and you’re already logging work against issues, there’s a very good chance you also have to log time in another application that’s completely disconnected from the work you’ve already done… this might be a fully featured enterprise-grade system, or it might be something as simple is a spreadsheet you fill out in Microsoft Excel.
- There’s nothing inherently wrong with using JIRA in combination with any of those other solutions. They all serve different needs in organizations, whether the focus is on enterprise HR management, manufacturing, integrated time clock management, etc. The thing to remember is that the more systems you use, the more information you have to manage. More systems equals more work for users, even if the systems are easy to use.
- But what can you do differently? Is there a way to eliminate the disconnect between your JIRA issues and the time you need to log for the business? Is there a way for DevOps and Business teams to work on the same platform? Is there a way to reduce information, application and device overload and work together no matter where you are in the world? The answer is yes – Tempo Timesheets.
- Tempo Timesheets is the most popular time tracking add-on in the Atlassian Marketplace, shown on the left. They have twice as many installations & downloads as the next few competitors combined. When you look at the rest of the time tracking landscape, their success and popularity is even more evident.
- Last year, I helped an organization replace a home-grown time tracking solution with JIRA and Tempo Timesheets. As JIRA users, you can probably already see that even JIRA on its own would help solve a lot of these problems. Tempo Timesheets ranked highest on their critical path “wish list” and helped them take time tracking to the next level. Immediate wins – improved performance, fully tracked history, JIRA plus Tempo notifications, customizable JIRA workflows plus Timesheet approval & rejection options, easy access to information, elimination of redundant data entry and the ability to collect all the necessary month-end data from a few easy to run reports. Is it a perfect solution? No. And it’s still evolving. But it’s light years ahead of the system that was in place before.
- Before we look at Tempo Timesheets in action, let’s take a high-level look at how the combination of JIRA plus Tempo Timesheets manages your data….
- All of the things you’re accustomed to managing in JIRA is still the same. JIRA still manages Projects, Permissions, Issues, Worklogs, Groups, Workflows, Screens, etc. There’s one minor exception for screens, in that Tempo adds their own “Log Work” screen that can be used in place of the out of the box version. But other than that, JIRA is still JIRA. A few of the high level things Tempo Timesheets adds – 1) Accounts: Similar to a JIRA project – used to track and categorize cost centers or funding sources), 2) Worklog Attributes: an extension of JIRA’s worklogs, allowing you to add metadata to worklogs if you need to, and 3) Teams: Similar in concept to JIRA’s groups. Tempo’s Teams play a critical role in the Timesheet approval & rejection process, provide some extra permissions, and also give you an easy way to filter time.
- JIRA Issues, Worklogs and Users on the left, Tempo Accounts, Worklog Attributes and Teams on the right. In this example, JIRA Projects are linked to Tempo Accounts. This allows an Issue to be linked to an Account through a new custom field automatically created by Tempo. Worklog Attributes can be used to provide extra info in individual Work Logs. Tempo Teams pull users together based on your time-tracking approval hierarchy. This might be the same as your JIRA Project membership and roles, or it could be completely different.
- If you’d like to see a live demo of JIRA and Tempo Timesheets or need help with any of your DevOps needs, we’d be happy to hear from you!