Remain Taps JIRA to Heighten Change Management Collaboration

December 2, 2015 Dan Burger

Controlling the chaos of collaboration from an application development perspective has proved to be a valuable asset for many IBM midrange customers. Better code, with the bugs worked out before it goes into production, saves time and money compared to debugging and redesigning after the fact. The value goes beyond writing code because collaboration applies to many business oriented teams and numerous end users who are effected sometimes for the better and other times for the worse.

Project tracking comes in many flavors, so Remain Software is integrating its application lifecycle management tool, TD/OMS, with multiple popular options. Its latest integration efforts involve JIRA, a proprietary workflow application developed by Atlassian that manages the communication and task flow among team members.

The integration of Remain’s TD/OMS and JIRA combines JIRA’s agile management functions with the software development workflow and application lifecycle management functionality of TD/OMS. The goal is creating higher quality code and more stable applications than either of those tools could accomplish on their own.

To collaborate or not to collaborate is the question. The power of collaboration is tied to a well-managed workflow and is an unquestioned certainty in modern software development, says Marco Kok, managing director at Remain Software.

“This is the reason why we decided to integrate our application lifecycle management tool with collaboration solutions, such as JIRA. We let the customer choose the best option for their IT department and the most suitable software for their specific way of working and projects,” Kok says in a press release announcing the integration.

More is better when it comes to options, even though Remain has software with many of the same capabilities as JIRA. Remain calls its JIRA-like tool Gravity and it is designed to integrate with TD/OMS, a product used in IBM i development environments around the world. TD/OMS is also designed to integrate with IBM Rational Team Concert, which provides yet another option for communication and collaboration with multiple-platform development environments as well as extensive project management scope.

Any of these integration options allows a person to manage the task-related source code within the TD/OMS repository while benefiting from the strength of the IBM i in combination with Java and/or RPG best practices and users’ established workflows. IBM i developers and users can retain their methodologies for developing software and also retain the favorite collaboration processes outside of development.

In addition to project-tracking, JIRA also includes a service desk element for IT and other service teams including non-technical business teams such as marketing, finance and human resources.

“Every team needs some way to organize tasks, activities, projects, deliverables and deadlines,” said Atlassian’s President Jay Simons in an article published by CIO magazine. “JIRA started as a way for tech teams to manage collaboration around products and the things that needed to get done. Over time it has been pulled in other directions by many parts of the business.”

Improved collaboration and communication due to Remain’s IBM i-focused integration work is expected to increase software engineering productivity through streamlined processes that speed the delivery of applications and lower costs.

TD/OMS tasks or requests can be added to the JIRA workflow from within the TD/OMS UI. TD/OMS users who are not heavily involved in JIRA, but require overview of TD/OMS-related JIRA issues, should benefit from the integration.

TD/OMS is an IBM i Application Lifecycle Management (ALM) solution supporting change, development, modernization, and multi-platform deployment processes. It provides control over the software life cycle process and provides a real time overview of software components and configuration. For companies with compliance and auditing requirements, it’s a tool for managing and monitoring app development component movements.

The Eclipse-based Remain Software ALM tool is also integrated with IBM’s Rational Developer for i (RDi), including the latest release RDi 9.5. The integration allows access of TD/OMS functions within the RDi interface. Those functions include task management, check-out, edit, source compare, compilation and problem resolution.

TD/OMS is also integrated with solutions, such as Fresche Legacy‘s X-Analysis code analysis tool, Linoma Software‘s RPG Toolbox for modernization projects, and BCD‘s WebSmart PHP, a Web application development environment.

The integration with WebSmart PHP is a recent development. It provides a graphical overview of all PHP component relations, which can be displayed within TD/OMS or other PHP editors, including Zend Studio.

New RDi Ready For IBM i Developers

Fresche Legacy Advances App Dev Integration Plan

Remain Software ALM Tool Gets CA Plex Interface

Software Change Management Designed For Small IBM i Shops

Remain Software Improves ALM Workflow, Readies Multi-Platform Capabilities

Tags:

Sponsored By
UNITED COMPUTER GROUP, INC.

UCG VAULT400 BaaS Clients have it ALL!

You can't say your data protection is complete until you have a disaster recovery plan that is itself complete and tested.

        • Secure cloud backup and disaster recovery
        • Hardware DR
        • Cyber security training
        • 19 data centers across the U.S. and Canada
        • 24 x 7 x 365 monitoring
        • Supports all platforms and databases
        • The latest in IBM Power Systems
        • An excellent client experience each and every time

HOW MUCH CONFIDENCE DO YOU HAVE IN YOUR CURRENT DATA BACKUP,
DR AND CYBER SECURITY PROGRAMS?

Consider these best practices when evaluating data backup, DR, and cyber security options:

1. RELIABILITY. Up to 71% of restores from tape contain failures. Best Practice: Use disk-to-disk technology for backups. With disk-to-disk technology, your backup data resides on disk drives, proven to be far more reliable than tapes. When your backup completes, you know the data is secure and accessible on the disk drive. With tapes you never really know if your data is usable until you try to restore it, at which point it's too late.

2. BREADTH OF OFFERING. Choice in product and service offerings meet your business' needs. Best Practice: Don't settle for less than what you need. Vendor offerings vary widely. Some are designed primarily for consumers and others for enterprise data centers. Choose a solution that scales (see scalability below), and offers the features you need to provide the level of service you expect. De-duplication and delta-block technologies will improve performance, reduce your data footprint and save you money. Find out if their de-duplication offering is at the file level or the block level. Make sure the solution can back up servers, PCs, and laptops as well your applications.

3. SECURITY. 60% of organizations using tapes don't encrypt their backups. Best Practice: End-to-end encryption with no "back door." Using encryption with tape makes backups run slowly and often takes too long to fit within a backup window. As a result, most people simply turn encryption off, creating a security risk. Even with the physical safety of disk-to-disk backup, encryption is essential. Look for 256-bit AES. Find a solution that encrypts your data during transmission and storage. Make certain there isn't a "back door" that would let someone else view your data.

4. CYBER SECURITY. More than 80% of U.S. companies have been successfully hacked, according to a recent Duke University/CFO Magazine Global Business Outlook Survey. Best Practice: Regular cyber security training and phishing tests for all employees using company email are essential to your organization. Your end-users are the weak link in your network security. Today, your employees are frequently exposed to advanced phishing attacks. Trend Micro reported that 91% of successful data breaches started with a spear-phishing attack. Be sure your vendor of choice includes cyber security training as part of their backup and DR package.

5. Accessibility. Companies waste thousands of hours waiting on tapes. Best Practice: Ensure that you can get your data back with minimal delay. You should have direct access to your backups, with no time spent on physical transport (no trucks, no warehouses). Your restores should take minutes, not hours or days. Set yourself up to work with your data, not wait for it. Make sure your solution provider can meet your Return-to-Operations (RTO) and Recovery Point Objectives (RPO) which determine how quickly you can recover your data and maintain business continuity. Inquire about onsite and offsite replication that provide both improved performance and a solid disaster recovery strategy.

6. Scalability. Some backup systems can't scale readily. Best Practice: Invest in a data protection architecture that can grow with your business. You should be able to back up your data no matter how large it grows. Starting small? Look for an option that handles your backups automatically. Then, as you grow, gives you tools to manage complex environments. Look for "changes-only" and compression technologies to speed backups and save space. And insist on bandwidth throttling to balance traffic and ensure network availability for your other business applications. Make sure that their solution offerings rely on common technology to scale easily as your business--and data--grow.

7. Cost-effectiveness. Companies lose an average of $84,000 for every hour of lost activity. Best Practice: Calculate the true total cost of tape-based back up. When you do the math, the dollars make sense: Go with disk-to-disk. Unlike tape, there are close to zero handling costs-no rush deliveries, loading, accessing, locating, or repeated steps. And there's one benefit you can't factor directly: Reputation. Reliability and security can make an incalculable difference with just one avoided breach or failure.

8. Compliance. Most companies have problems satisfying privacy, security, and data retention regulations. Best Practice: Choose a data protection partner who has deep know-how about compliance, and the technology to ensure it.

9. Disaster Recovery. Most companies lack a comprehensive, tested plan for disasters. Best Practice: Find a vendor that delivers a complete DR solution. You can't say your data protection is complete until you have a disaster recovery plan that is itself complete and tested. Your backup vendor should have both the product mix and professional services team to help you prepare for a worst-case scenario. Make sure they can help configure your backups so you rebound quickly. Best bet: A vendor who can train you to deal with disasters confidently, based on your company's actual configuration.

10. Ease-of-Use. Some companies don't--or can't--manage their backups from one place. Best Practice: Get control and reporting you can use anywhere, with ease. Managing your backup environment should be simple, and the software you use should eliminate any guesswork that could lead to lost data. You should know at all times if your data is protected across your entire network-including remote offices-by simply looking at a dashboard. The software should be simple to configure using wizards, yet powerful enough to meet your specific needs with customizable views, job propagation, and roles-based security.

11. Operating System and Platform Support. Most backup vendors support a limited range of OS, server types, and applications. Best Practice: Look for broad and deep technology that supports your complete environment. Your backup solution should accommodate your environment, not vice versa. Demand a single solution to protect your laptops, desktops, and servers regardless of the platform and applications they're running. Beyond the broad claims, check the fine print, and the level of protection offered for applications such as Exchange. For example, can they restore individual mail messages or contacts, and can they support Exchange running on a Microsoft Cluster?

12. Customer Support. Backup vendors' product support varies widely. Best Practice: Find a vendor whose support is passionate, maybe even slightly obsessed. Customer support should be one of your vendor's main selling points. You shouldn't have to wonder if they'll be there to help when you need them most. Do they offer phone support or email only, and who exactly are you talking to when you call that 800 number? Find a vendor that will treat your data as if it were their own.

13. Reputation. Does your backup vendor have a quality reputation and the financial resources to stay in business for the long haul? Best Practice: Find a vendor with strong financial backing and customer references. There are a lot of vendors that have come and gone. When you consider a service provider, look for one that has strong financial backing, a solid business plan and the ability to be in business as long as your data needs to be stored. Ask for customer references and case studies as their customers are the best validation you can get.

DOWNLOAD A PDF OF THIS ARTICLE:
BEST PRACTICES FOR BACKUP AND RECOVERY

Connect with us on our social networks!

You can find us on Google+, LinkedIn, Twitter, Facebook, and YouTube.

For more information or to schedule a demonstration on UCG's products and services,
please visit us at ucgrp.com/Talk2Us or call 800.211.8798.

Browse our Resource Libraries for important information and downloads!
UCG VAULT400 BaaS Resource Library
UCG S2K Enterprise Management Software (EMS) Resource Library

ucgrp.com • vault400.com

Technology customized to your business, today and in the future.