Case study: Agile practices and IBM System z development
sjpeich 270000KJQC Comments (3) Visits (5288)
Is it a constant struggle to keep strategic goals, objectives, projects connected and aligned? Traditional software development methods don’t help. Programmers can work separately for days or even weeks on the same code without realizing how many conflicts (and perhaps bugs) they are generating. Because they are producing robust code with each iteration, agile teams find that they are slowed down by the long resolution and debugging sessions that occur at the end of long integration cycles. For these reasons, agile teams often choose to use continuous integration.
Join us on September 12, 2012 at 11 AM EDT / 4 PM BST / 3 PM UTC for a complimentary webcast where we'll discuss one IBM customer experience with mapping continuous integration concepts that are used in distributed development to the IBM® System z® domain – the successes and the remaining challenges. You’ll learn how the IBM Continuous Integration Solution for System z enables distributed and mainframe teams to build and test an end-to-end, cross-platform application continuously and at low-cost. We’ll also discuss how it can help manage change and address persistent bottlenecks during testing.
Register now by visiting http
Stay after the webcast for a live question-and-answer session.
UPDATE: This webcast is available for replay. Go to the registration page to access the PDF, webcast recording and mp3 audio.