The internet and web-based services provide proven and scalable solutions for the challenges of distribution and collaboration. New technology-driven ways of working, such as those leveraging Web 2.0 concepts, are familiar and have transformed users’ expectations.
So why not implement these same approaches when developing and delivering business software solutions? Successful application lifecycle management (ALM) environments must address this complexity by connecting all members and components of a project and then providing each individual with a role-based view. By coupling these two concepts—global access to a common project environment and an individualized context in which to work—teams have the potential to change the ways that they develop and deliver their products.
The IBM Rational Jazz Strategy for Collaborative Application Lifecycle Management Liz Barnett EZ Insight, Inc. July 2008 Untitled Document 2 of 7 The IBM Rational Jazz Strategy for Collaboration Application Lifecycle Management Software and systems are essential to nearly every business. Global organizations require software solutions that span geographic boundaries, cultures, and business units and that comply with corporate governance mandates. Such global businesses must collaborate effectively and leverage existing investments, or lose out to competitors. Fortunately, the global technology infrastructure specifically the use of the Internet and Web-based services provides proven and scalable solutions for the challenges of distribution and collaboration. New technology-driven ways of working, such as those leveraging Web 2.0 concepts, are familiar and have transformed users expectations. For example, worldwide procurement via eBay or Amazon is an everyday occurrence. The power and value of collaboration among those building software is also well understood. So why not implement these same approaches when developing and delivering business software solutions? Project teams are essentially a microcosm of the global business world: team members and the assets they produce are geographically distributed, and unique skills and resources can reside at any location. Successful application lifecycle management (ALM) environments must address this complexity by connecting all members and components of a project and then providing each individual with a role-based view. By coupling these two concepts global access to a common project environment and an individualized context in which to work teams have the potential to change the ways that they develop and deliver their products. People produce high quality software. Tools and processes are enablers. With the Jazz project, IBM Rational is providing integrated tools and processes that help people working on distributed teams more effective in producing software solutions. It calls this type of environment Collaborative ALM, and defines it as a new paradigm for transforming the software lifecycle so that it is more collaborative, transparent, and productive. 1 The Jazz project is Rational s vehicle for achieving collaborative ALM. 1 Source: John Wiegand, IBM Software Group, Rational, Distinguished Engineer and Rational Chief Architect. Untitled Document 3 of 7 The Jazz Project encapsulates three distinct but related initiatives that will enable collaborative ALM: 1. Rational s vision of an open integration architecture that can achieve truly collaborative, productive, and transparent software delivery in a global environment. 2. Jazz technology, a set of core services that enable ALM tools to add value and interact with each other. 3. A community in which Rational developers, customers, and business partners can collaborate on developing Jazz services and associated tools. Just as Eclipse provides rich integration and productivity for individuals, Jazz will do so for teams. Key Benefits of the Jazz Project Successful collaborative ALM requires innovation in collaboration, process, and transparency. These concepts that underlie three of the key benefits of the Jazz project: 1. Collaboration in Context. Diverse and geographically distributed teams work towards a single set of goals, as defined by a project. However, each participant on a project has his own role, his own responsibilities, and therefore his own context for working. Collaboration in context refers to a team member s ability to work with others on shared deliverables in the most productive way for the individual task at hand. In the Jazz environment, team members are aware of who else is on the team, what each team member is working on, and the relationship of others work to their own. But the Jazz technology goes a step further and treats all interactions as valued project assets, storing them as associations with the specific artifact (e.g., defect, test case) that was the source of the interaction. This approach to collaboration is unique to the Jazz offering and is perhaps its greatest differentiator. In a global environment, teams need to be able to draw upon resources regardless of their location. The greater the information available to a team member, the lesser the need for real-time interactions, reporting, and other forms of overhead. Individual productivity improves, as does the quality of team collaboration. Untitled Document 4 of 7 2. Just Enough Process. No single development or deployment process is appropriate for any organization. Companies require a portfolio of processes to support the myriad projects that they run. The Jazz architecture supports the ability to define and implement a range of processes, from lightweight approaches used by small iterative teams to highly-structured, rule-driven processes necessary for corporate or regulatory compliance. 3. Global Transparency. Transparency is a fundamental component of any collaborative ALM solution and a requirement to satisfy governance initiatives. Global teams must have the same degree of visibility at all locations. Effective transparency has two distinct aspects: the availability of accurate information and the achievement of passive governance. Jazz addresses both of these requirements with a tool-based environment that unobtrusively generates and communicates accurate project metrics based on the organization s unique guidelines. On distributed teams, developers, managers, customers, and other project participants all require real-time knowledge of a project s status, issues, and risks. Jazz accomplishes this by providing automated user-defined processes, generated project metrics, and global access to dashboards at the individual, team, and portfolio levels. In addition to these benefits, Jazz offers a future infrastructure for the many Rational ALM tools in use at large organizations. Jazz is designed so that shared services and data can be accessed via standard open interfaces and Web protocols. Initially, Jazz-based products provide bi-directional connectors for integration with existing tools. Rational Jazz Products The Jazz Foundation implements the underlying architecture for a new generation of Rational tools. The foundation includes the Jazz Team Server technology, the core infrastructure for deploying and integrating tools. It includes support for in-context collaboration, real-time project health, event notification, process enactment and enforcement, global search and query, security, role-based access, automated traceability, and a distributed repository for all development assets. Rational Team Concert (RTC). RTC is the first family of collaborative ALM tools delivered using the Jazz Team Server. The goal with RTC was to think first about how people worked together on a distributed software development team, and then to design a tool to support those work styles and roles. Initially, RTC targets small- and medium-sized distributed teams, particularly those using Agile Untitled Document 5 of 7 processes for development or team management, however RTC can be used with any development process. RTC is generally available as of June 2008. Rational Quality Manager (RQM). RQM, currently available in beta, is a new Web-based test management portal built to the Jazz architecture. Focused on addressing the needs of business analysts and QA professionals, RQM employs a test plan-centric view of testing assets. It provides the ability to use different perspectives for accessing and viewing testing assets, based on the user s role. For example, managers can review timelines and status reports for testing cycles, while business analysts can concentrate on test coverage for business requirements. In addition, test planning assets can be related to specific testing executables stored in Rational functional and load testing tools. General availability of this new product is expected in the second half of 2008. Rational Requirements Composer (RRC). In the area of requirements definition and management, Rational is offering new visual tools and is providing integration among requirements, SCM, testing, and other ALM tools. RRC provides graphical modeling, storyboarding, and sketching tools for eliciting and defining requirements, and uses a wiki-like platform for enhanced collaboration among stakeholders and development teams. RRC can generate the textual requirements assets that are stored in Rational RequisitePro. Users can also relate this rich requirements content through RequisitePro to other lifecycle assets, including test cases created in RQM, and thus be able to determine test coverage and traceability for requirements. RRC was also announced in open beta in June 2008, with general availability expected in the second half of 2008. Early Customer Experiences With RTC Among the many features in RTC, beta teams highlighted several stand-outs: Quick start-up. Training for the core work item management capabilities is minimal. Some teams worked with Rational Jumpstart support staff to conduct a brief three hour training class; others just figured it out without formal training. RTC s pre-defined role definitions and workflows made it easy to add new team members, without administrative overhead. (Rational call this day one productivity. ) Seamless integration with the Eclipse IDE. One customer noted that in the past, teams had to use three tools and switch from the Eclipse IDE to manage code in CVS and issues in Jira. With RTC, teams work from a single client environment and have access to all their development and collaboration tools developers no longer need to leave the Eclipse IDE to access other ALM functions. Further, teams had little difficulty learning to use the new tool, since it leveraged the Eclipse interface. Untitled Document 6 of 7 Little need for reporting overhead. By providing customers with a Web browser interface to the work item system and team dashboards, teams don t need to spend time creating additional status reports. Also, providing 24x7 direct access to team progress led to goodwill and far fewer surprises for customers. Simpler installation and management. Beta teams noted that maintaining project assets in the Jazz repository cuts management overhead and is far simpler than maintaining separate SCM and defect tracking environments. Achieving Strategic Benefits With the Jazz project, Rational has developed breakthrough technology and is poised to set the standard for collaborative ALM. Those companies that adopt Jazz-based tools will truly be able to transform their software development organizations. Most notably, teams will be able to: Deploy global teams of developers, managers, business users, and customers to produce leading-edge software; Improve team productivity and quality through collaboration and seamless tool integration; Provide real-time visibility into accurate project metrics for all project participants, regardless of their location; Employ Agile and iterative development and management practices to address ever-changing business requirements and to shorten delivery cycles; Achieve compliance with corporate governance and regulatory requirements without impeding team productivity; Leverage development assets created and processes used by existing Rational ALM tools; and Interact with Rational developers, other customers, business partners, academics, and anyone using Jazz.net to enhance the Jazz environment and participate in creating industry standards. Jazz offers a great opportunity to initiate Agile projects and provide distributed teams with a productive collaborative environment. Small- and medium-sized teams can get started with the new Jazz-based tools immediately. Given the current business climate of deliver more with less much sooner, organizations have no choice but to rethink the ways that they deliver software solutions. The Jazz project will help teams achieve that goal. Untitled Document 7 of 7 About the Author Liz Barnett is the Principal Analyst at EZ Insight, Inc., an analyst and consulting firm focused on global software development issues and technologies, founded in 2005. In 2006, she also launched the Agile Journal, an online publication providing in-depth analyses and case studies for Agile developers and managers, and was Editor in Chief for its first two years. Previously, Liz spent 10 years as a Vice President and Research Analyst at Forrester Research, joining Forrester as a result of its acquisition of Giga Information Group. Liz has held management positions at Accenture, PepsiCo, Atelier Research, and New Science Associates (subsequently acquired by Gartner Inc.). Liz earned her B.S. in operations research and industrial engineering at Cornell University. This report is the result of research underwritten by IBM and developed by EZ Insight, Inc. The analyses and findings are derived from EZ Insight s independent views. 2008 EZ Insight, Inc. All rights reserved.