Home ALM Journal - Vol 5 - Num 12 - December 2016
Bob Aiello,
Back

Recent articles by Bob Aiello

We are pleased to announce that our new on Agile Application Lifecycle Management - Using DevOps to Drive Process Improvement will be available June 2016 New website coming! Pre Order our new book using Discount Code Agile35 Integrate Agile ALM and DevOps to Build Better Software and Systems at Lower Cost Agile Application Lifecycle Management (ALM) is a comprehensive development lifecycle that encompasses essential Agile principles and guides all activities needed to deliver successful software or other customized IT products and services. Flexible and robust, Agile ALM offers “just enough process” to get the job done efficiently and utilizes the DevOps focus on communication and collaboration to enhance interactions among all participants. Agile Application Lifecycle Management offers practical advice and strategies for implementing Agile ALM in your complex environment. Leading experts Bob Aiello and Leslie Sachs show how to fully leverage Agile benefits without sacrificing structure, traceability, or repeatability. You’ll find realistic guidance for managing source code, builds, environments, change control, releases, and more. The authors help you support Agile in organizations that maintain traditional practices, conventional ALM systems, or siloed, non-Agile teams. They also show how to scale Agile ALM across large or distributed teams and to environments ranging from cloud to mainframe. Coverage includes Understanding key concepts underlying modern application and system lifecycles Creating your best processes for developing your most complex software and systems Automating build engineering, continuous integration, and continuous delivery/deployment Enforcing Agile ALM controls without compromising productivity Creating effective IT operations that align with Agile ALM processes Gaining more value from testing and retrospectives Making ALM work in the cloud, and across the enterprise Preparing for the future of Agile ALM Today, you need maximum control, quality, and productivity, and this guide will help you achieve these capabilities by combining the best practices found in Agile ALM, Configuration Management (CM), and DevOps.  
Micro Focus Completes Acquisition of Serena Software, Inc. Application Lifecycle Management Acquisition Boosts Micro Focus’s DevOps Capability ROCKVILLE, Md., May 2, 2016 /PRNewswire/ -- Micro Focus (LSE: MCRO.L) today announced the completion of its acquisition of Serena Software, a leading provider of Application Lifecycle Management (ALM) software, under the terms of the definitive agreement disclosed on March 22, 2016. "Our customers continue to look at DevOps as a way to deploy critical applications and services quickly and with greater reliability to meet business demands," said Stephen Murdoch, CEO, Micro Focus. "The Serena acquisition extends our ability to help customers meet these challenges so they can drive greater innovation faster with lower risk." According to industry analyst firm Gartner, "DevOps implementations utilize technology, especially automation tools, that can leverage an increasingly programmable and dynamic infrastructure from a life cycle perspective."1  The experience and expertise which the Serena business brings will enable Micro Focus to help its customers develop and release applications and services faster, with greater speed and accuracy. Serena adds capabilities in software application development; software configuration and change management; and business process management to Micro Focus's portfolio of ALM solutions spanning mainframe environments, distributed systems and cloud. The combination of Micro Focus and Serena allows companies to better: Design and build business applications and services with greater accuracy, reliability and predictability; Continuously deploy existing core business applications on a wider variety of platforms to meet changing business needs; and Improve the speed and efficiency of new business services through automated release and deployment solutions. About Serena Software Serena is among the largest Application Lifecycle Management vendors with more than 2,500 enterprise customers. Serena helps the highly regulated large enterprise move fast without breaking things – increasing velocity of the software development lifecycle while enhancing security, compliance, and performance. More information is available at www.serena.com. About Micro Focus Micro Focus (LSE: MCRO.L) is a global enterprise software company helping customers innovate faster with lower risk. Our software helps customers build, operate and secure IT systems that bring together existing business logic and applications with emerging technologies to meet increasingly complex business demands. For more information, visit: www.microfocus.com. 1I&O Must Combine ITIL and DevOps to Deliver Business Value for Bimodal IT," by George Spafford and Ian Head, March 18, 2016.

Popular articles by Bob Aiello


Random articles by Bob Aiello

IBM Rational Team Concert (RTC) is an excellent Application Lifecycle Management (ALM) solution that includes support for robust version control and workflow automation. Implementing RTC can be as simple as downloading and unzipping a zipfile or as complex as implementing WebSphere clusters and DB2 HADR. I first had the pleasure of implementing RTC 2.1 back in 2010. We selected a fairly robust topology with WebSphere as the application server and DB2 as the backend database. RTC was fairly new at that point and it was not trivial to install, configure and implement this technology. We added a bit of complexity by separating out the HTTP Webserver and creating a reverse proxy on the front end and then implementing DB2 HA DR on the backend. The result was a robust platform that could serve both onshore and offshore developers' needs and was able to scale quite effectively. My next RTC related assignment was to help a smaller team implement RTC 3.0 using the quite formidable community edition and for this purpose we actually just used the tomcat container and the Derby database which met the team's requirements and was quite acceptable. More recently, I had an opportunity to work with RTC 4.0.2 found some of the new features both challenging and exciting. Implementing RTC with Tomcat will work just fine for many teams and is certainly a lot simpler than tackling WebSphere, although the complexity may well be worth the effort because of the excelle scalability, performance and reliability. RTC 4.0.2 works well with WebSphere 8.0.0.3 and you may want to take the extra effort to separate out the HTTP webserver onto its own machine. This requires that you generate a reverse proxy plugin - which is essentially an XML file which is then propagated (actually copied) from the application server to the webserver. The plugin allows the webserver to forward requests to WAR file responsible for the tasks that need to be completed. For RTC this may be the JTS (JazzTeamServer) or CCM (Change and Configuration Management) component. If you are implementing the Quality Management (QM) and/or Requirements Management (RM) component then the plugin also helps to direct the work to the correct server where the WAR file has been deployed. You can start by deploying all of the components on one application server and add additional servers as your usage (and performance) requirements begin to increase (presumably due to your tremendous success implementing RTC. There's a lot more to implementing RTC which I will write about in future articles and I would also like to hear about your experiences implementing this new  IBM technology. more details coming...
The Chicago Board Options Exchange (CBOE) had its second outage in a week while trying to prepare its systems for expanded trading hours. The previous glitch occured on April 25th and caused the exchange to be down for half the day, with additonal  problems the next day. The CBOE described the cause of the glitch as an "internal systems issue and not the result of any outside influence". Published reports indicated that the cause of the outage was related to preparations for expanding trading hours. CBOE executives were quoted as saying that they had no plans to abandon the longer trading day and will hire an outside consultant to help. Many observers have noted that system glitches threaten the confidence in the financial systems infrastructure. But is this really the right focus? Commentary: This is only my opinion, but I believe that what seems like an endless list of high profile systems outages points to a more serious issue and that is our lack of commitment to developing and implementing software and systems in a professional way. Software systems are often mission critical with little or no room for mistakes. When companies fail to manage risk and establish proper IT controls then disaster happen such as what occured recently at Knight Capital. We need to stop making excuses and ensure that corporations develop and implement systems using industry best practices such as DevOps. Financial systems should be secure and developed with a secure trusted base. In order to be successful, corporations need to start with the basics including source code management along with automated application build, package and deployment. We can do this. Companies that do the right thing will also enjoy improved productivity and quality! That's my opinion. Drop me a line and share your views! Bob Aiello

Copyright © 2017 CM Best Practices. All Rights Reserved.
Joomla! is Free Software released under the GNU/GPL License.
 

Product News

Live Online Training

Jobs