Pratyush Nutalapati

Agile by concept is co-locating all the three legs of the IT organization the business, IT and QA. However with more and more organizations doing offshoring to optimize cost and getting the best talent across the globe it has become a challenging transition from traditional enterprise development processes into an Agile methodology along with geographically split teams with various time zones. Traditional approaches to offshore development are based on plan-driven methodologies and doing agile is definitely challenging. Because agile development works best with close communication and an open culture, agilists working offshore feel the pain much more than those using plan-driven approaches. Locations We have implemented Agile Offshoring for both development and QA teams spread across Reston(VA), Kansas(KS), Bangalore (India) and Gurgaon (India) for a major communication client. Methodology We follow SCRUM Agile process with two week sprints and a production release atleast after two sp

Agile by definition is an iterative and incremental approach to software development which is performed in a highly collaborative manner by self-organizing teams within an effective governance framework with enough ceremony that produces high quality software in a cost effective and timely manner which meets the changing needs of its stakeholders. Agile methodologies share much of the same philosophy, practices and characteristics. But from the way each of them is implemented they have their own recipe of practices and terminology. Agile basically promotes iterative development, teamwork, collaboration and process adaptability throughout the life-cycle. Iterations are short time boxes that last from one to four weeks. The goal is to ensure the application is ready to be deployed at the end of the iteration however it might not always be true in most organizations. The production readiness happens at the end of last iteration for the planned release in most of the scenarios especially i

Installing Plugin between iPlanet and Webshpere 6.x server If you are doing a plain vanilla installation with Webserver listening on port 80 than regular steps will help. However if we are installing in any other port we need to do some manual changes for the plugin to work correctly. Below are the list of files that you would have to change the port name manually: - Plugin-cfg.xml This is the file that connects between the webserver and appserver that we mentioned during the plugin installation. We need to make the following changes virtualhostgroup name="default_host" virtualhost name="*:9080" virtualhost name="*:80" virtualhost name="*:9443" virtualhostgroup Modify the line in red from 80 to the port your webserver is listening. Also don’t forget to add this line to provide access to your application root in the : - Virtualhosts.xml This is located in your profiles directory as below: C:\Program Files\IBM\SDP70\runtimes\base_v6\profiles\AppSrv