|System z on Facebook
Straight from Innovate2014 - Day 3 Highlights
Pratin Ashtekar 2700046SAG email@example.com | | Tags:  enterprise_modernization devops innovate system_z_software innovate2014 appdev mainframe | 1,856 Visits
By Craig C. Branham,
Technical Enablement Specialist- Enterprise Modernization.
Greetings again from Orlando, where it's early afternoon at IBM Innovate 2014, Day 3.
I spent yesterday at the Solution Expo (where the catering made it Build-Your-Own-Wrap night). In the Demo Center, I watched as RDz Architect, Bill Alexander, for another night expertly led demonstrations of Rational Developer for System z. The DevOps Zone-Enterprise Systems peds feature live demonstrations, along with loops of demonstration videos (similar to this series on RDz from Rational User Technologies).
Also at the Expo, after my third wrap, IBM DevOps Technical Sales Lead, Sanjeev Sharma made a formal appearance to sign copies of his excellent chapbook, DevOps for Dummies (a free ebook version is available). Sharma is uniquely engaging and entertaining, an essential DevOps speaker at the conference. As I gushed such sentiments about his IBM Sales Academy presentations, Sharma inscribed my book, "Live long and deploy!" and referred me to his own DevOps video series. Well said.
After a repentant oatmeal and coffee, this morning I attended my highlight session of the day, Rosalind Radcliffe's "Collaborative Development Panel: Best Practices in Implementing a Rational Team Concert Solution," featuring experts from client organizations and partners sharing lessons learned from their own successful enterprise RTC rollouts and migrations. Consistent with themes I described in yesterday's post, along with the need to integrate global, cross-organizational teams, a big reason that clients are adopting RDz and RTC is to leverage skills across their mainframe and distributed development teams.
The panel agreed that the biggest success factor for implementing an RTC solution successfully is training. Some of the experts reported success by providing formal curricula of classroom courses, while others succeeded using more informal training, such as one program that was similar to pair programming ("each one teach one"). In general there was agreement that learning needs to be continuous throughout the rollout effort; it requires formal planning, leadership support, and accountability among developers.