Wir leben JIRA! JIRA als Ersatz für SAP & Co - Atlassian User Group München, 25.09.2014 Elian Kool, Head of Technology at Netcentric
←
→
Page content transcription
If your browser does not render page correctly, please read the page content below
Wir leben JIRA! JIRA als Ersatz für SAP & Co. Atlassian User Group München, 25.09.2014 Elian Kool, Head of Technology at Netcentric
AGENDA 1
2
How we started
Our tools
3 Next steps and conclusion
1 HOW WE STARTED
Netcentric: Who are we?
Netcentric is a Founded in 2012 Working with many
leading service with 17 employees, clients in highly
provider for the we have grown to regulated environ-
Adobe Marketing 100+ within ments where we
Cloud, serving 24 months across have to pass
many multi-national Europe vendor assess-
brands and ments and meet
corporations standard usually
fulfilled by large
companies
4
Besides in our offices in Zurich, Munich, Barcelona and London, we often work with clients on-site – which requires us to be able to perform all tasks independent of any location or availability of a person. 5
How we started
July 2012
We were using JIRA/Confluence already HEAVILY FOR REQUIREMENTS
MANAGEMENT, Bug tracking and general task tracking
All our (rather techie driven) employees were USING IT ON A DAILY BASIS
We were using TEMPO TIMESHEETS FOR TIMETRACKING throughout
everything from the very beginning – incl. vacations, etc.
Multiple PLUGINS SUCH AS GLIFFY & BALSAMIQ are supporting us
in our daily work
We used the rather new ATLASSIAN ONDEMAND offering to jump-start our
Atlassian stack
How we started
July 2013
JIRA has been well established as the central tool – the most common answer
to a question has become “IT’S IN JIRA/WIKI!”
Due to our demands for custom plugins and a central user management, we
moved away from on Demand to an ON-PREMISE INSTALLATION
Replacing HP Quality Center with Zephyr for JIRA for TEST MANAGEMENT
After MANY HEADACHES WITH CROWD (which is badly maintained), we had
to develop our own LDAP connector
JIRA as all purpose system We‘re using JIRA on a daily basis for many things HR management solution incl. asset management Recruiting platform with more than 1000 candidates in 2 years Opportunity Management solution And many more (internal tasks, R&D, etc.) Besides this, of course what everyone does: Full project lifecycle management with all our customers
Lot‘s of activity...
2 OUR TOOLS
What is a JIRA Issue?
Workflow Fields Permission
§ Describes the § Name/Type § Who may see what?
neccessary steps § Placement on screens § Who may do what?
§ Holds the status § Required/optional
A piece of
Information
CONCLUSION
You can build almost everything with JIRA ☺Recruiting workflow
Recruiting: Our conclusion
Using JIRA for our recruiting has been a DECISION
WE NEVER REGRETTED – works smooth and easy
Recruiting
What works What could be improved
§ Can be SOLVED EASILY using JIRA, § FLEXIBLE PERMISSIONS are not possible: Either
no special plugins required you have access to everything or only to specific
§ COMMUNICATION based on comments § INVOLVEMENT OF RECRUITING AGENCIES
works very well is technically feasible (POC done) but
practically limited by the willingness of
§ Very HIGH ACCEPTANCE from the
recruiting agencies & permissions
beginning (managed more than
1000 leads within 2 years)OMT Workflow
OMT: Our conclusion
Our sales is focused on a few large accounts, so OMT basically
replaces a central Excel sheet. Basic calculations can easily be made,
but it‘s for sure not a full salesforce replacement
OMT
What works What could be improved
§ Can be SOLVED EASILY using JIRA, § Customer – Contract – Tasks, in this case a further
no special plugins required sub-task level would come very handy
§ Using the OMT tickets directly for
time booking on small projects
§ CALCULATING BASIC KPIS
(e.g. order value/probability)HR: Accepting company policies SIMPLE CAPABILITY to enforce employees to accept corporate policies Process has been ACCEPTED IN A VENDOR ASSESSMENT we had to do with a bank!
HR: Asset Management SIMPLE CAPABILITY to track laptops, phones, licenses, etc. Has PROVEN ITSELF MANY TIMES (e.g. s/n for stolen or broken devices)
HR: Our conclusion
The HR system allows us to manage everything connected with an
employee from contract signature on – incl. ensuring he/she gets the
proper Laptop!
HR
What works What could be improved
§ CREATE AND MANAGE EMPLOYEES § INHERITED PERMISSIONS are not possible
(e.g. with automated subtask creation) (means it’s difficult to build hierarchies…)
§ BASIC PERMISSION MODEL
(assignee = manager)
§ Many ASSIGNED SUBTASKS such as
Computers, Phones, Reviews,
Passport copies, Holidays, sick
time, etc.3 NEXT STEPS & CONCLUSION
Our Next steps
1
Find a solution
2
Review inven-
3
Improve con-
4
(Finally)
5
Develop own
for the permis- tory solution: trolling and improve the reports or find a
sioning model: Current subtask planning with incoming advanced
JIRA’s security concept vs. Tempo Books – e-mail handling reporting suite
schemes are too buying a plugin we’re waiting for (JMEH or for proper
simple for com- this since a Service Desk?) project reporting
plex structures year!
FutureConclusion: JIRA as all purpose system
Is it working?
We NEVER REGRETTED the decision to use JIRA AS OUR ALL PURPOSE SYSTEM
We’re KEEPING SENSITIVE DATA OUT (e.g. salaries) of JIRA due to the limited
options with permissions
JIRA itself doesn’t do the trick – YOU NEED MANY, MANY PLUGINS… this cumulates
to a 100k USD investment and will get quite expensive once youu need 500+ users
The ACCEPTANCE among our employees is VERY HIGH
INTEGRATION WITH CONFLUENCE is quite important and it is crucial to define
what is stored where (JIRA, Confluence, Alfresco)Q A 29
You can also read
