Rational Team Concert (RTC) is at the core of IBM’s DevOps solution and the logical starting point for teams looking to get started with SAFe. Through a choice of topologies that include either a single RTC Project Area for small teams or multiple RTC Project Areas for added flexibility and scalability, RTC can be configured today to provide SAFe support that addresses the needs of small and mid-range IT shops as well as large, regulated IT organizations. The choice of topology depends on the characteristics of the organization. To learn... [More]
About two years ago, we started the Learning Circles initiative to provide simple and structured educational material on some IBM Rational products. There are now 11 published Learning Circles that you can leverage for your own enablement, or for self-paced training in your organization.
To align the material with latest product releases, the CLM and the RTC Learning Circles have been recently updated. They now include specific material on CLM 5.0 (and even 5.0.2 for RTC).
Earlier this year, we also worked with Scaled Agile... [More]
RTC 5.0.2 - Newest improvements for Agile Teams
December 2, 2014
11:00 AM - 12:00 PM (Eastern Time)
JL Marechaux (IBM)
Rolf Nelson (IBM)
Link to PRESENTATION
Link to RECORDING
If you care about Rational Team Concert for agile development, DO NOT not miss this webinar! We will... [More]
This week, we have released Rational Team Concert 5.0.1 with new features to improve support for agile teams who are using Scrum and Kanban. Among other things, this new RTC version provides enhancements for planning, reporting, usability, traceability, and performance.
It also includes a “hidden” capability, the “ Quick Planner Technical Preview ”. Those who are familiar with the cloud offering IBM DevOps Services may already know the Quick Planner. A similar capability is now available... [More]
In a recent post, see here , I summarized four of the key DevOps principles, namely:
Automate as much of the deployment pipeline as feasible
Develop and test against a production-like system
Continuously validate operational quality characteristics
Programs and projects adopting continuous delivery practices must create software in such a way that the software can be released to production at any time.
Establish a “Single Source of Truth”
In a recent post, DevOps in Practice – Best Practices for Adopting Continuous Delivery , I summarized seven practices for helping teams establish a automate continuous delivery process.
Establish a single source of truth
Automate painful tasks
Manage inter- and intra- application dependencies
Make “what is where” visible
Make certifications and approvals visible
During the Innovate conference earlier this month in Orlando, we delivered a 3-hour workshop on how to use Rational Team Concert with Scrum in agile projects. If you have not been able to travel to Florida, you can access the workshop material and do it on your own. To complete the hands-on exercise, you will access to an RTC environment.
Workbooks and instructions are provided here: http://bit.ly/Innovate1063
(File 1_AgileALM_Tutorial_SetupGuide.pdf describes how to set up and configure an RTC environment for the workshop)
Session 2: Backlog management and release planning
Agil e AL M Vi rtua l St udy Grou p Se rie s for information on registration and details on the different sessions
During the second session on this series, we review the key element of a Rational Team Concert (RTC) project based on the Scrum-Agile ALM process template.
IBM Rational Solution for Agile ALM with Scrum .
Explore elements in an Agile ALM project
Share a product vision
Session 1: Understand and reuse the technical solution assets
(See the Agil e AL M Vi rtua l St udy Grou p Se rie s for information on registration and details on the different sessions)
During the first session on this series, we want to describe what the IBM Rational Solution for Agile ALM with Scrum is, and what are the technical assets it contains. We also want people to understand how to find, install, and use those assets quickly. So we will cover the following topics:
As promised in Part 1 , I have continued my effort to document the differences between the RTC Scrum template and the Agile ALM Scrum template.
The summ ary- of-d iffe renc es docu ment , Lin k-to -Sum mar y , h as been updated with links to detailed information on the revised Defect and Story workflows . (See the first bullet under Work Item Types and Attributes .) The states and actions for these two work item types caused some confusion in the user community. T he Agile ALM Scrum... [More]
All activities of the Agile ALM Virtual Study Group are now completed.
More information on each session (files, recording, workbooks) is available from:.
Virtual Study Group Part 1: htt p:// bit. ly/A alm_ S 1
Virtual Study Group Part 2: htt p:// bit. ly/A alm_ S 2
Virtual Study Group Part 3: htt p:// bit. ly/A alm_ S 3
The IBM Rati onal Sol utio n fo r Ag ile ALM with Scr u m... [More]
At or around Innovate 2013, IBM released a new Agile ALM Scrum process template for RTC. The Agile ALM Scrum template is based on the Scrum template, with modifications promising better support for Agile Planning with Scrum .
After reviewing the new template, I became interested in morphing a Scrum-based project to the Agile ALM Scrum definitions. My first step was to create a summary of the differences between the two templates. (Thank you to the template authors for their help in finding and understanding these... [More]
In this blog post , I would like to share some practical experiences gained over past couple of years in Implementing Agile in our team. I intend to write this as a multi part series with each one walking through a different adoption phase for a set of practices we felt were important to implement at particular point in time. I would also like to share on what worked well for us and some pitfalls to avoid . Part 1 : The beginnings
Part 2 : Agile Planning And Tracking