How RWE Supply & Trading supported an Atlassian toolset rollout from 25 to 2,500 users. Author: Hope Jack, originally presented at the London Atlassian User Group, 14 May 2013 http://www.meetup.com/UK-Atlassian-Community/
Boost PC performance: How more available memory can improve productivity
From 25 - 2500 users: Experiences from an Atlassian rollout
1. RWE Group Business Services PAGE 1
From 25 – 2,500 users:
Experiences from an Atlassian rollout
Hope Jack
17/05/13
2. RWE Group Business Services PAGE 217/05/13
How to grow Confluence & Jira
1. Philosophy
2. Who we are
3. Know your audience
4. Talking another language “Utilis”
5. Challenges
6. Stats 2009 – 2013
7. Lessons Learned
3. RWE Group Business Services PAGE 317/05/13
Philosophy
During my days as a Sky TV customer service rep I learnt a very important
lesson!
When there is a problem people don’t like to feel isolated that they are the
only one with the same problem. So what I used to do was always say “Oh I
have had that problem already today” Immediately their attitude would
change. So today I use this mantra dealing with my users.
4. RWE Group Business Services PAGE 417/05/13
Who we are
RWE Supply & Trading
Based in Essen, Germany: with Europe’s largest and most sophisticated energy trading floor
Hub for all tradable commodities, in both their physical and/or derivative forms, including power,
gas, coal, freight, oil, weather, emissions certificates and renewable energies
5. RWE Group Business Services PAGE 517/05/13
“Know Your Audience”
Adoption of Confluence by business users needs a different approach
from the “early adopters in the IT department
6. RWE Group Business Services PAGE 617/05/13
Talking another language “Utilis”
12. RWE Group Business Services PAGE 1217/05/13
Use Cases
> Every IT project
> Gas Operations (24/7)
> IT Change Processes
> Back Office – Recurring checks
> Compliance – New Counterparty
> HPQC Bridge – Slovakian Test Centre
13. RWE Group Business Services PAGE 13
THANK YOU VERY MUCH FOR
YOUR ATTENTION.
17/05/13
Hinweis der Redaktion
Something about building trust, you don’t have long when you start the rollout, just one mistake at the start and users won’t trust you
Code Monkeys - typically a developer – Can do it all myself, why do you rules? Give me admin access (Front Office) Process Heads (Project Managers / Business Analysts) – know enough to be dangerous Tinkerers – Spread-sheet Bods – easiest - Risk/Back Office Newbies – don’t have much IT experience, massively grateful Kids - pick up, play with it, throw it away (traders, architects)
Making confluence the go to place for information Know the business Interface to other systems – don’t make it them or us (confluence vs sharepoint) Branding – DE users much more comfortable with company colours Providing templates for common function – meetings Be professional at all times – building trust Service availability & good performance - users aren’t forgiving Training – offer online & 1-2-1 sessions Pick local mentors – give them a platinum service & they can help their local teams Eat your own dog food – use the tools to support your team & users
The challenge of a trading environment is the constant pull between standardization & quickly fulfilling business need – Systems in use Singapore – New York time & changes High standards – upgrades have to be tested, tested & tested. Fine line between Yes & No Changing IT systems – Do you have the correct set up for a large amount of users Crazy Questions Boundaries Are you ready? (Do you have a team ready for a large uptake users)
First jump in growth is spreading by word of mouth in IT, the 2 nd growth period is when we roll out to the rest of the business Plan for growth, workload can be highly variable
Mistakes – upgrades & communication = calendars upgrade – users get very personal about content Remember using Jira & Confluence isn’t a users day job, it’s yours. Security – user creation Rate of growth, can you cope Document, document, document Spiralling costs Introducing Standardisation Early On Custom fields over 400 performance starts to be effected Workflows – No 2 teams work the same Know your stuff!