Atlassian 1 For Everyone. Possible solutions 2 AtlassianCollabNetHPIBMInflectra Micro...
-
Upload
lynette-harper -
Category
Documents
-
view
214 -
download
0
Transcript of Atlassian 1 For Everyone. Possible solutions 2 AtlassianCollabNetHPIBMInflectra Micro...
1
AtlassianFor Everyone
2
Possible solutions
Atlassian CollabNet HP IBM Inflectra
Micro Focus Microsoft Parasoft Polarion Software PTC-MKS
Rally Software Rocket Software TechExcel
Serena Software ThoughtWorks
VersionOne
3
Possible solutionsRequirement Atlassian Microsoft TechExcel VersionOne IBM HP CollabNet Inflectra Micro Focus Parasoft
Polarion Software PTC-MKS Rally Software
Rocket Software
Serena Software ThoughtWorks
Requirements managementProject managementQuality managementDefect managementBuild managementRelease managementLab managementChange managementTask management
Modeling or acquire a software that integrated with
ITSM or possibility to acquire an ITSM that integrated withReportingHubMarketplace
Integrated with Office or Google app Word
Fully integrated with Software development TFS
4
Why Atlassian ?• Lowest cost (important for sponsor)
• Very customizable (future needs)
• Big Marketplace (solutions out of box)
• Nice UI (user acceptance)
• Standard processes (manager)
• All teams are connected (transparency)
• Source Access (modifications)
• Open (external integration with others systems)
• Supports many application/database servers
• SOAP, XML-RPC, Java API Interfaces• Plugin sub-system
5
Lower costProduct User tier Maintenance Price
JIRA 50 users 12 months 2200$
JIRA Portfolio 50 users 12 months 1650$
Jira Misc Workflow Extensions 50 users 12 months 240$
Confluence 50 users 12 months 2200$
Team Calendar 50 users 12 months 800$
JIRA Service Desk 2.0 15 agents 12 months 4500$
JIRA Agile 50 users 12 months 1100$
Crowd 50 users 12 months 10$
Scroll translations 50 users 12 months 660$
FishEye 50 users 12 months 2200$
Tempo Timesheets for JIRA 50 users 12 months 1100$
Email this issue for JIRA
50 users 12 months 250$
Visual studio 2013 Premium Free with msdn subscription
0$
Eclipse Free (open source)
0$
Atlassian IDE connector Free 0$
Total 16910$
Issue tracker
Manage projects / Manager
Automatic linksDocumentations/Everyone
Technical team / EveryoneSupport team
Developer/Analyst/Everyone
Manage login with LDAP
Source control
Timesheet
French/English documentations/knowledge base
Send issue for everyone, not just Jira users
For developer
For developer
Embedded tasks in Eclipse and Visual Studio
*$US without taxes
6
Begin with best practices !
Licence JIRA (online course) Confluence (online course) JIRA Agile (online course)
26-50 users free free Free
1 course with an expert to answer to the questions. (1 seminar)
2400$ 1000$ 500$
Total 3900$
*$US without taxes
7
What we gain ?
• Legacy • Centralized platform
8
What we gain ?
• Legacy • Atlassian - Centralized platform
Costs 6700$CAD with
taxes/year
working in silos
It’s not what we need
Costs ~27 000$CAD with taxes - one time
Renew software maintenance
Costs ~10951.69$CAD
(incl. taxes)/two years
9
What we gain ?
BRING TRANSPARENCY
• Breaking down “organisational/teams” silos
• Bring together all departments or teams who impact the customer experience. It should enroll the key players
• Ensure everyone understands the inter-dependencies between departments and the effect on the customers experience
• We have a platform where we can optimize and automate processes
• Reporting and dashboards across all content
• Set Priority/Ranking of projects
• Find precise items and tangentially related ones
• New functionalities for the customer (historic, portal)
• and so much more!
• Atlassian - Centralized platform
Costs ~27 000$CAD with taxes - one time
Renew software maintenance
Costs ~10951.69$CAD
(incl. taxes)/two years
10
What we gain ?
BRING TRANSPARENCY
• Cohesiveness within Software Delivery (shipping system / website / AS400 / Progress)
• Traceability: Requirements/Needs -> Issues -> Code
• Search of artifacts or concepts across project
• Encapsulate knowledge of a given domain• Concepts, and how they relate to one another
• People and their roles
• Functions
• Process
• ROI• How much revenue did that feature generate ?
• How much did that bug cost us ?
• Atlassian - Centralized platform
Costs ~27 000$CAD with taxes - one time
Renew software maintenance
Costs ~10951.69$CAD
(incl. taxes)/two years
11
Limits
• When we need to upgrade the licence, we need to upgrade all environments
Example :If we need 50 licences in order to have 100 licencesWe will paid
Product User tier Maintenance Price
JIRA 50 users 12 months 2200$
JIRA Portfolio 50 users 12 months 1650$
Jira Misc Workflow Extensions 50 users 12 months 240$
Confluence 50 users 12 months 2200$
Team Calendar 50 users 12 months 800$
JIRA Service Desk 2.0 15 agents 12 months 4500$
JIRA Agile 50 users 12 months 1100$
Crowd 50 users 12 months 10$
Scroll translations 50 users 12 months 660$
FishEye 50 users 12 months 2200$
Tempo Timesheets for JIRA 50 users 12 months 1100$
Email this issue for JIRA
50 users 12 months 250$
Total 10210$
*$US without taxes
12
Limits
• Jira Help Desk 2.0 is new and Atlassian has some features to develop• The customer notification are
partially in English because for now we can’ t customize the email template.• The customer portal is only in
English
We decide to go without these features and after integrate them
13
Schedule
ID Task Dependencies
T1 Order hardware
T2 Configuration of hardware T1
T3 Installation of Atlassian products/databases T2
T4 Configuration of basic administration T3
T5 Implementation for team T4
T6 Test drive and customisation T5
T7 3 Meetings with a demo and discussions about possible concerns and expectations
T8 data entry/import (BugNET, Octopus)
T9 Identify the key resource for each team in order to have constantly an expert of the software that is using. A maximum of 3 meetings of 2hrs can be used. Depend of team
For phase 1 For each team the same phase
14
Schedule
T5 Implementation for team T4
T6 Test drive and customisation T5
T7 3 Meetings with a demo and discussions about possible concerns and expectations
T8 data entry/import (BugNET, Octopus)
T9 Identify the key resource for each team in order to have constantly an expert of the software that is using. A maximum of 3 meetings of 2hrs can be used. Depend of team
For each team the same phase
For phase 2, we begin the implementation with support and technical team.
Because if the test-drive is successful, the company is able to save the cost of
Octopus per year. Phase 3, we continue to integrate another team: the web
development. We choose this team first because they used already an Issue
Management “BugNet”. Phase 4, we integrate the solution for App
desktop/mobile team.
We keep 2 weeks between phases in order to manage the custom needs and/or
issues during the tests. Besides, when a team is testing the solution, we can
prepare the implementation for other teams. Phase 5, we will do an
implementation for Progress team.
15
ImpactCulture
The goals of Information Management cannot be achieved by software alone. More important is a company's Work Culture that encourages workers to share information so that they are happy to "put information out there" for others to consume rather than hoarding it in their private stores.
Many people are familiar with wikis through Wikipedia. However, reading a wiki page is not the same as writing a wiki page. Facing a blank wiki page is quite disconcerting for new wiki users and they are often unsure of how to write a useful page.
Changing the way people work requires a change in the work culture itself. The work practices then become automatic.
16
ImpactStandardization of process
By implementing bottom-up development processes that maximize flow and improve team autonomy. The result is a customer-driven development culture that delivers products that customers want and a set of corporate values that resonates with internal and external customers.
17
Project Review Strategy
● Each week, we will check the number of connected people and how many time.
○ For Support team: Create reports with a custom SLA in order to monitoring the
performance.
○ For Development team: Knows how many bugs/features has been closed and how
many issue has been assignee, for who.
● Each week, we will ask to key resources if they had many questions about how use the
software. It’s an indicator in order to know if there is the progress learning or not.
Ensure interoperability:
Create a procedure for recovery plan, if the server is down because there is a
hardware/software problem, we need to know how many team and which resource(s) is/are
needed. Moreover, we need to train the resource to recovery the system in order to ensure
that every user can work after a period specified.
Each 2 months, we will do a maintenance of the systems and we will update the software if it’s needed.
18
Performance Measurement Strategy
1. Be Measurable : “Just fix it!” vs Create new bug handling
process
2. Be attainable : looking for someone vs Put all tasks in JIRA
3. Be relevant : Make many reports vs Define KPIs
19
Future
Why not open Atlassian for others department ?