logging in or signing up agile method rosr978 Download Post to : URL : Related Presentations : Share Add to Flag Embed Email Send to Blogs and Networks Add to Channel Uploaded from authorPOINT lite Insert YouTube videos in PowerPont slides with aS Desktop Copy embed code: (To copy code, click on the text box) Embed: URL: Thumbnail: WordPress Embed Customize Embed The presentation is successfully added In Your Favorites. Views: 1192 Category: Entertainment License: All Rights Reserved Like it (1) Dislike it (0) Added: September 17, 2010 This Presentation is Public Favorites: 0 Presentation Description agile method Comments Posting comment... By: armanom (7 month(s) ago) Agile methods are sometimes characterized as being at the opposite end of the spectrum from plan-driven or disciplined methods; agile teams may, however, employ highly disciplined formal methods. A more accurate distinction is that methods exist on a continuum from adaptive to predictive. Agile methods lie on the adaptive side of this continuum. Adaptive methods focus on adapting quickly to changing realities. When the needs of a project change, an adaptive team changes as well. An adaptive team will have difficulty describing exactly what will happen in the future. The further away a date is, the more vague an adaptive method will be about what will happen on that date. An adaptive team cannot report exactly what tasks are being done next week, but only which features are planned for next month. When asked about a release six months from now, an adaptive team may only be able to report the mission statement for the release, or a statement of expected value vs. cost. Predictive methods, in contrast, focus on planning the future in detail. A predictive team can report exactly what features and tasks are planned for the entire length of the development process. Predictive teams have difficulty changing direction. The plan is typically optimized for the original destination and changing direction can require completed work to be started over. Predictive teams will often institute a change control board to ensure that only the most valuable changes are considered. Saving..... Post Reply Close Saving..... Edit Comment Close By: Janakiraman (12 month(s) ago) Hi friend, i need to download this presentation for ma reference... Saving..... Post Reply Close Saving..... Edit Comment Close Premium member Presentation Transcript Agile Methodology – An Overview Krishna Kumar T KAVP EngineeringGCI : Agile Methodology – An Overview Krishna Kumar T KAVP EngineeringGCI Agenda : Agenda Agile Methodology – An Introduction Why Agile? Agile Methodology & Offshore Development Critical Success Factors Agile Implementation: The GCI Offshoring experience The Future of Agile and Offshore Development Agile Methodology – An Introduction : Agile Methodology – An Introduction Gartner defines Agility as "the ability of an organization to sense environmental change and respond efficiently and effectively to that change." Sensing the need for change also includes the proactive initiation of change. Rapidity of business change is driving a need for agility to respond more effectively to change.Organizations needed to make development process changes should strongly consider using Agile rapid applications development methodologies as part of moving to service-oriented development of applications. Any enterprise that aspires to respond in real time must have the ability to be agile when needed. Agile is successful because it: Stresses customer satisfaction Emphasizes team work (simple, yet effective way to enable groupware style development) Allows agile programmers communicate with their customers and fellow programmers quite regularly and empowers them to confidently respond to changing customer requirements, even late in the life cycle Why Agile? : Why Agile? Traditionally, software development has been process-centric. Agile methodologies change the face of software development by giving it a human touch (people over processes). Customers value ROI and time-to-market. Agile methodologies help in increasing ROI as well as reduce time-to-market. (incremental working software) Customers see quality, productivity and turn-around time as a risk when it comes to off-shore software development. Agile methodologies build trust and confidence as the customer is part of the team and the techniques used reduce the offshore risks. (customer collaboration and embracing change) Agile Methodology & Offshore Development : Agile Methodology & Offshore Development Critical Success Factors Use Continuous Integration to Avoid Integration Headaches Have Each Site Send Ambassadors to the Other Sites Use Contact Visits to build trust Don't Underestimate the Culture Change Use wikis to contain common information Use Test Scripts to Help Understand the Requirements Use Regular Builds to Get Feedback on Functionality Source: Martin Fowler Agile Methodology & Offshore Development : Critical Success Factors Use Regular Short Status Meetings Use Short Iterations Use an Iteration Planning Meeting that's Tailored for Remote Sites When Moving a Code Base, Bug Fixing Makes a Good Start Separate teams by functionality not activity Expect to need more documents. Get multiple communication modes working early Source: Martin Fowler Agile Methodology & Offshore Development Agile Implementation: The GCI Offshoring experience : Client : A leading supplier of media and technology solutions to connect real estate professionals to customers Salient Features The Core / Remote Team Model Phased Requirements Project Transitioning Multiple Technical Approach Agile Source Control Agile Testing Daily & Weekly Meetings Change Request Management Agile Implementation: The GCI Offshoring experience Agile Implementation: The GCI Offshoring experience : Agile Implementation: The GCI Offshoring experience Below is a mapping of the Agile requirements to the salient features of GCI’s Agile implementation Agile Implementation: The GCI Offshoring experience : Agile Implementation: The GCI Offshoring experience The Future of Agile & Offshore Development : The Future of Agile & Offshore Development What we will see is growing qualitative feedback on the benefits of agility and offshore development - these qualitative assessments will determine if either, or both, will survive – Martin Fowler Enterprises must learn how to measure agility in general, and they must make investments to improve their agility - Gartner opportunities@gcisolutions.inQ & A : opportunities@gcisolutions.inQ & A About GCI End-to-end IT services and solutions provider to Global 2000 firms; A $200 Million Global IT Services firm Headquartered in Morristown, NJ 3000+ Professionals globally with over 2000 in the U.S. alone 20+ offices Globally 6 Global Delivery Centers Ranked among the fastest growing technology firms in the U.S, by Deloitte & Touche, and Inc. 500, for 5 years in a row You do not have the permission to view this presentation. In order to view it, please contact the author of the presentation.
agile method rosr978 Download Post to : URL : Related Presentations : Share Add to Flag Embed Email Send to Blogs and Networks Add to Channel Uploaded from authorPOINT lite Insert YouTube videos in PowerPont slides with aS Desktop Copy embed code: (To copy code, click on the text box) Embed: URL: Thumbnail: WordPress Embed Customize Embed The presentation is successfully added In Your Favorites. Views: 1192 Category: Entertainment License: All Rights Reserved Like it (1) Dislike it (0) Added: September 17, 2010 This Presentation is Public Favorites: 0 Presentation Description agile method Comments Posting comment... By: armanom (7 month(s) ago) Agile methods are sometimes characterized as being at the opposite end of the spectrum from plan-driven or disciplined methods; agile teams may, however, employ highly disciplined formal methods. A more accurate distinction is that methods exist on a continuum from adaptive to predictive. Agile methods lie on the adaptive side of this continuum. Adaptive methods focus on adapting quickly to changing realities. When the needs of a project change, an adaptive team changes as well. An adaptive team will have difficulty describing exactly what will happen in the future. The further away a date is, the more vague an adaptive method will be about what will happen on that date. An adaptive team cannot report exactly what tasks are being done next week, but only which features are planned for next month. When asked about a release six months from now, an adaptive team may only be able to report the mission statement for the release, or a statement of expected value vs. cost. Predictive methods, in contrast, focus on planning the future in detail. A predictive team can report exactly what features and tasks are planned for the entire length of the development process. Predictive teams have difficulty changing direction. The plan is typically optimized for the original destination and changing direction can require completed work to be started over. Predictive teams will often institute a change control board to ensure that only the most valuable changes are considered. Saving..... Post Reply Close Saving..... Edit Comment Close By: Janakiraman (12 month(s) ago) Hi friend, i need to download this presentation for ma reference... Saving..... Post Reply Close Saving..... Edit Comment Close Premium member Presentation Transcript Agile Methodology – An Overview Krishna Kumar T KAVP EngineeringGCI : Agile Methodology – An Overview Krishna Kumar T KAVP EngineeringGCI Agenda : Agenda Agile Methodology – An Introduction Why Agile? Agile Methodology & Offshore Development Critical Success Factors Agile Implementation: The GCI Offshoring experience The Future of Agile and Offshore Development Agile Methodology – An Introduction : Agile Methodology – An Introduction Gartner defines Agility as "the ability of an organization to sense environmental change and respond efficiently and effectively to that change." Sensing the need for change also includes the proactive initiation of change. Rapidity of business change is driving a need for agility to respond more effectively to change.Organizations needed to make development process changes should strongly consider using Agile rapid applications development methodologies as part of moving to service-oriented development of applications. Any enterprise that aspires to respond in real time must have the ability to be agile when needed. Agile is successful because it: Stresses customer satisfaction Emphasizes team work (simple, yet effective way to enable groupware style development) Allows agile programmers communicate with their customers and fellow programmers quite regularly and empowers them to confidently respond to changing customer requirements, even late in the life cycle Why Agile? : Why Agile? Traditionally, software development has been process-centric. Agile methodologies change the face of software development by giving it a human touch (people over processes). Customers value ROI and time-to-market. Agile methodologies help in increasing ROI as well as reduce time-to-market. (incremental working software) Customers see quality, productivity and turn-around time as a risk when it comes to off-shore software development. Agile methodologies build trust and confidence as the customer is part of the team and the techniques used reduce the offshore risks. (customer collaboration and embracing change) Agile Methodology & Offshore Development : Agile Methodology & Offshore Development Critical Success Factors Use Continuous Integration to Avoid Integration Headaches Have Each Site Send Ambassadors to the Other Sites Use Contact Visits to build trust Don't Underestimate the Culture Change Use wikis to contain common information Use Test Scripts to Help Understand the Requirements Use Regular Builds to Get Feedback on Functionality Source: Martin Fowler Agile Methodology & Offshore Development : Critical Success Factors Use Regular Short Status Meetings Use Short Iterations Use an Iteration Planning Meeting that's Tailored for Remote Sites When Moving a Code Base, Bug Fixing Makes a Good Start Separate teams by functionality not activity Expect to need more documents. Get multiple communication modes working early Source: Martin Fowler Agile Methodology & Offshore Development Agile Implementation: The GCI Offshoring experience : Client : A leading supplier of media and technology solutions to connect real estate professionals to customers Salient Features The Core / Remote Team Model Phased Requirements Project Transitioning Multiple Technical Approach Agile Source Control Agile Testing Daily & Weekly Meetings Change Request Management Agile Implementation: The GCI Offshoring experience Agile Implementation: The GCI Offshoring experience : Agile Implementation: The GCI Offshoring experience Below is a mapping of the Agile requirements to the salient features of GCI’s Agile implementation Agile Implementation: The GCI Offshoring experience : Agile Implementation: The GCI Offshoring experience The Future of Agile & Offshore Development : The Future of Agile & Offshore Development What we will see is growing qualitative feedback on the benefits of agility and offshore development - these qualitative assessments will determine if either, or both, will survive – Martin Fowler Enterprises must learn how to measure agility in general, and they must make investments to improve their agility - Gartner opportunities@gcisolutions.inQ & A : opportunities@gcisolutions.inQ & A About GCI End-to-end IT services and solutions provider to Global 2000 firms; A $200 Million Global IT Services firm Headquartered in Morristown, NJ 3000+ Professionals globally with over 2000 in the U.S. alone 20+ offices Globally 6 Global Delivery Centers Ranked among the fastest growing technology firms in the U.S, by Deloitte & Touche, and Inc. 500, for 5 years in a row