Recommended
Recommended
More Related Content
What's hot
What's hot (9)
Similar to NYC AUG Kick Off Recap: Jira, Trello, Lightning Talks
Similar to NYC AUG Kick Off Recap: Jira, Trello, Lightning Talks (20)
More from AUGNYC
More from AUGNYC (19)
Recently uploaded
Recently uploaded (20)
NYC AUG Kick Off Recap: Jira, Trello, Lightning Talks
- 1. 2018 NYC AUG Kick Off New York February 22, 2018 / 6:00 PM 90 MEMBERS ATTENDED
- 2. Agenda 6:00 pm Doors Open 6:25 pm Opening Note 6:30 pm Jira & Trello: When to use Each? - Trevor Longino, Unito.IO 7:05 pm A Lightning Talk on Giving a Lightning Talk - Dileep Bhatt, NYC AUG Leader 7:20 pm Starting Small with Jira, but Planning for Growth - Craig Castle-Mead, Y&R 8:00 pm Closing Note & Raffles 8:10 pm More Food, More Drinks, Networking 9:00 pm Doors close
- 3. Let’s Talk JIRA + Trello
- 4. ● Trello & why to use it ● Trello PM “Hacks” ● Trello as part of an org’s workflow Tonight you’ll learnSo you can decide if you’re gonna duck out for more beer in the middle ● JIRA + Trello ● JIRA in an org ● Unito (of course :P) ● Questions Trell o Jira
- 5. about me Trevor Longino ABOUT CMO, Unito.io Mustache Officer & evangelist for Unito.io, a work management tool sync engine
- 6. Unito syncs work management tools like Asana, Jira, GitHub and Trello together to make collaboration between teams easier. We’re the backend for cross-team collaboration.
- 11. What is Trello?
- 16. TEAM KANBAN
- 21. PERSONAL KANBAN
- 26. GATHER REQUESTS
- 29. WHAT ABOUT JIRA
- 33. ● Brainstorming ● Kickoffs ● Short (1 -2 sprint projects) ● “Lowest Common Tool” ● Big (2 + sprint projects) ● Working with team members who are committed on multiple projects ● Multiple mutually dependent projects When to switch toolsTrello & Jira, side by side Trell o Jira
- 34. “JIRA SUCKS”
- 36. ● High level views ● Kanban ● Planning & day to day task management ● Forecasting ● Complex project delivery ● Customization, but be careful Know your strengthsTrello & Jira, side by side Trell o Jira
- 37. WORKING TOGETHER
- 44. THANK YOU
- 47. DILEEP BHAT | CO-LEADER | AUG NYC AUG NYC Lightning Talk How to Give a Lightning Talk?
- 48. Goals Takeaways What & Why of a Lightning Talk? What topics do NYC AUG members want to hear about? How easy is it for me to present at the next AUG event?
- 49. What is a Lightning Talk? Presentation Guidelines 5-7 Minutes 5 Slides 1-3 Takeaways Ending with ‘What’s Next?’
- 50. Why a Lightning Talk? Lightning Talk (LT) Introduce yourself, start a conversation on a topic Swap stories, share knowledge, generate ideas, foster collaboration Encourage participation & more user driven content Practice speaking & present your interesting ideas
- 51. Topic Ideas Tools, Craft, Teams Tips & Tricks, Lessons Learned, Real World Examples How are we using and customizing tools to our firm’s needs? Non-Atlassian tools & integrations Issues encountered & problems in need of a solution Interesting Side Projects
- 52. Topic Examples Requested by AUG Members What are top 3 plugins you can’t live without? How did we implement SSO and SSL solutions? Portfolio – How does it work for the enterprise and how do you long term planning? How do you configure Atlassian Tools across multiple departments? How do non-software teams in my firm use Jira?
- 53. Topic Examples And More… How do we encourage adoption and educate users? How do we keep our clients/users happy? How do we use JIRA for physical asset management? How do we handle governance and compliance requirements of Atlassian tools in our firm? How do Atlassian Tools compare to competitors? ….And even more
- 54. Next Steps Thinking about Giving a LT? AUG Leaders are here to help! Distill ideas, practice dry runs Get in touch with one of us!
- 55. Questions?
- 56. Thank You! DILEEP BHAT | CO-LEADER | AUG NYC
- 58. Starting Small with Jira, but Planning for Growth
- 60. Agenda • UHUB overview and some statistics • Things to keep in mind as you’re rolling out Jira • Questions
- 61. *** DISCLAIMER *** These are my opinions and may go against advice from Atlassian themselves, and other admins / experts, however they have been valuable in our environment
- 62. UHUB is a platform of tools customised for agencies to enable collaborative work within and between agencies, customers and vendors on a wide range of functions.
- 63. Statistics (Jan 2018) Jira • 16,000 users • 10,000 projects • 750,000 issues • 3,150,000 comments • 18,500 hours of resource planning • 1,100,000 hours of logged work HipChat • 6.5 million messages Confluence • 16,000 users • 345,000 pages BitBucket • 3,700 repositories • 970 GB of code
- 64. 0 200000 400000 600000 800000 1000000 9/2/2012 9/2/2013 9/2/2014 9/2/2015 9/2/2016 9/2/2017 9/2/2018 9/2/2019 9/2/2020 9/2/2021 Issue Creation over time (UHUB)
- 65. Usage (Jul 2017 - Jan 2018)
- 66. What does it take to support this? Team • 1 x Melbourne • 1 x Singapore (1 more coming soon) • 1 x London (coming soon) • 3 x New York • 1 x Austin • 1 x Vancouver Everyone has a mix of directly engaging with the businesses (BA role) + end user support (JSD), subset of the team manage the infrastructure. Growing amount of automation via Puppet Enterprise – first upgrade yesterday (Bamboo) was a one click event.
- 67. Infrastructure Team • 1 x Melbourne • 1 x Singapore (1 more coming soon) • 1 x London (coming soon) • 2 x New York • 1 x Austin • 1 x Vancouver What does it take to support this?
- 68. Before you start: • Groups • Groups cannot be renamed. Refactoring is a pain • Settle on a naming convention • Make sure it allows for growth For authorized internal use only – not for redistribution
- 69. Before you start: • Groups – NEST • Company (assign licenses / global permissions here) • Region • Country • Office • Department For authorized internal use only – not for redistribution
- 70. Before you start: • Usernames – use email as the username • Especially if you’re using an external user directory (LDAP/AD etc) For authorized internal use only – not for redistribution
- 71. Before you start: • Architecture • Use psql (if you’re not using cloud) For authorized internal use only – not for redistribution
- 72. Permissions: • Use permission schemes instead of roles (roles should be for exceptions) • Use groups instead of users (users should be for exceptions) • Create a “base” permission scheme for each entity (department / office / etc) For authorized internal use only – not for redistribution
- 73. Governance: • Limit elevated privileges For authorized internal use only – not for redistribution
- 74. Governance: • Limit elevated privileges • Limit elevated privileges For authorized internal use only – not for redistribution
- 75. Governance: • Limit elevated privileges • Limit elevated privileges • No really For authorized internal use only – not for redistribution
- 76. Governance: • Disable “Configure Fields” For authorized internal use only – not for redistribution
- 77. Governance: • The customer is NOT always right (kind of) • They’ll often ask for a technical solution • Try and understand the business reason for the request • Work on the best way of delivering on the business reason For authorized internal use only – not for redistribution
- 78. Governance: • One add-on for one task For authorized internal use only – not for redistribution
- 79. Clone projects: • Don’t use the project create UI to create projects – it creates a new scheme each time • Setup master templates, use ScriptRunner’s clone project
- 80. Marketing: • Don’t promote the product, promote the benefits • Think about user personas and sell a narrative that is supported by feature • Promote different benefits to different types of users • “A day in the life of” • Account Manager (Confluence Blueprints, live collaborative editing) • Project Manager (Create Jira tasks from the Blueprint, use BigGantt to map out timeline) • Resource Manager (Use Tempo products to schedule resources) • Production resources (Jira workflow, prove they’re over-booked) • C Suite (High level reporting – Tempo, BigGantt, EazyBI)
- 81. Be prepared to make unpopular decisions: • Be firm but fair • Pick your battles – give small wins to some users to build the relationship
- 82. You don’t know everything: • Come to an AUG • Make friends with other admins • Participate on community.atlassian.com • Create a relationship with an Atlassian Partner – there’ll be times you need to supplement your internal skillset
- 83. A Confluence tip: • Don’t give anyone the “Restrictions” permission. It will bite you in the ass.
- 84. Summary • Plan ahead • Some refactoring is easy, some is an absolute pain. • Solve business problems • Engage with the users, work to understand the driving force for each ask. • Governance • Be firm but fair.
- 85. Quemments?
Editor's Notes
- But isn’t that just the same thing as JIRA kanban boards?
- What do we use the tools for @ Unito
- Claify exactly that we’re stepping drom Cross-Team to Team to Kanban board from the same source view
- So with all of this discussion about Trello, you mightt think I’m gonna tell you that you don’t need JIRA. Hah, no. Trello is a great tool for when you want a user-friendly presentation and a UX that’s not likely to overwhelm. It’s not great for complicated views of tasks or for using data to understand deep fundamental truths about your work. That’s what JIRA is for, and it’s strengths in comparison lie in Add otehr points about when we divide work from Trello to a more complex tool, but in
- Forecasting
- Monitoring delivery of complicated projects
- And the Atlassian Marketplace’s ability to customize the product to do anything you can imagine. Only 60 - 70
- John Cutler writes an article about the love/hate relationship many people have with JIRA https://hackernoon.com/trello-jira-sucks-and-tool-dysfunction-e80c8000a431 The key idea is true: Trello is “easy and friendly” largely because you cannot modify it substantially. “Jira sucks” in part because of our temptation to use tool complication to try and manage the fact that our process for work management in an org is dysfunctionally complex, and rather than adapt to a simpler work management process, we abuse our tools. You can’t do that with Trello, which is part of its appeal.
- Talk about growth of Trello users in JIRA orgs Give specific use case examples here: no names, but “blue-chip tech company that’s been around for more than 100 years” use case and “international media organization with 20,000 journalists & staff around the world” use case.
- But wait… can you combine the two together to get the best out of both tools? Of course you can. :P
- What I mean when I’m talking about the backend of cross-team collaboration here--I’m not going to into any of these in great depth, but I want to just explain why you might wanna use Unito or a similar tool if you have many teams working in different work management tools like JIRA and Trello. The obvious reason is to have
- Add recommendations for powerups that might be cool to use other than Unito List functionaliuty for what Atlassian plugin does vs. Unito plugin does.
- On either Trello or JIRA there are many options for how to integrate the two together. I’m personally a fan of Unito’s integration for obvious reasons, but I’m not really here to sell you on it; I just want to open your mind to the idea that there are many ways to connect the two platforms together, and that I think that your business and tech teams will benefit from doing exactly that.
- Any tool can take you from A to B, but what’ s the Experience that you have on the way that matters?
- Talk about examples – nesting all developer groups into BB global users, regional based, cross office collaboration, all project managers into Bulk Change permissions