Preview

Improvement in offshore change management model under the umbrella of Agile

Better Essays
Open Document
Open Document
1223 Words
Grammar
Grammar
Plagiarism
Plagiarism
Writing
Writing
Score
Score
Improvement in offshore change management model under the umbrella of Agile
COMSATS Institute of Information Technology Lahore Campus

Synopsis for the degree of M.S./M.Phil. Ph.D.

PART-1 (to be completed by the student)

Members of Supervisory Committee

1.

2.

3.

4.

Title of Research Proposal

Improvement in offshore change management model under the umbrella of Agile

Summary of the Research Proposal

Requirements get changed during the course of software development process. It looks very difficult to stop the software requirements, from changing. Different software development approaches tackle changing requirement in different ways. Unlike Waterfall or document driven approaches of software development, agile methodologies welcome change during the course of software development but at the same time manage the changes in a systematic manner [1, 10]. This thesis will focus on the requirement change management and the various aspects of change management in agile. Moreover this thesis will also discuss the offshore development model with respect to Agile requirement change management. An important condition for Agile approach is to have continuous collaboration and relationship with the customer [2] so that requirements could be elicited as well as verified regularly. But in offshore environment, this approach can not be applied due to presence of the client on geographically distant location. Therefore this thesis will also highlight some of the elicitation techniques, tools and methodologies that can be applied in offshore development model while working with Agile. The problem stated in the “statement of problem” will be further refined and elaborated by extensive literature review and the proposed solution will be further evaluated with more validation.

Introduction

Requirement change management is one of the important project management issues in software development. Requirements do change during development process. Managing



References: [2] Kent Beck, Mike Beedle, Arie van Bennekum, Alistair Cockburn, Ward Cunningham, Martin Fowler. (2001). Manifesto for Agile Software Development. http://agilemanifesto.org/ (02 March 2010)

You May Also Find These Documents Helpful

  • Good Essays

    Bsbpmg510A Kbq

    • 635 Words
    • 3 Pages

    Change Management: To ensure the post projects ongoing success the change in the business due to the project must…

    • 635 Words
    • 3 Pages
    Good Essays
  • Best Essays

    The Software Development Life Cycle (SDLC) gives very definable goals regardless of the methodology used; the development process will have a planning and a testing phase whether it is Waterfall or Agile. At Smith Consulting (SC), projects begin with a project planning phase when SC selects team leaders and assigns jobs to team members based on their particular strengths. Then SC locks project requirements into an open-ended Agile process…

    • 3816 Words
    • 16 Pages
    Best Essays
  • Good Essays

    Bsa 385 Week 2

    • 791 Words
    • 4 Pages

    Developing software is far from an exact science and without a structured system to guide the process a project is likely to fail. Defining and adhering to a Software Development Life Cycle (SDLC) early in the project will help to guide the development of a new information system. In addition to having the structure for the development team to work within a defined and agree upon SDLC will help to set the proper expectations for deliverables with the stakeholders and customer(s). Smith Consulting has been given the task of creating a Frequent Shopper program for Kudler Fine Foods. As a result Smith Consulting needs to decide on which SDLC will work best for this project. In addition to selecting a SDLC to use Smith Consulting will need to determine how testing will be conducted. The purpose of this paper is to compare and contrast Waterfall and Scrum SDLC's, including how testing will be performed for each, such that Smith Consulting will be able to make an informed decision on which methodology to use when creating the Frequent Shopper Program for Kudler Fine Foods.…

    • 791 Words
    • 4 Pages
    Good Essays
  • Best Essays

    The Scrum approach has been developed gaming for managing the systems development process. It is an empirical approach applying the ideas of industrial process control theory to gaming development resulting in an approach that reintroduces the ideas of flexibility, adaptability and productivity (Schwaber & Beedle 2002). It does not define any specific software development techniques for the implementation phase. Scrum concentrates on how the team members should function in order to produce the system flexibly in a constantly changing environment.…

    • 3180 Words
    • 13 Pages
    Best Essays
  • Good Essays

    Software development is the full-cycle process of developing a software product. The software development cycle, assuming the software project management follows the waterfall model, includes: requirement gathering, system analysis, designing, coding, testing, and implementation. A software development team must commit to creating and maintaining (i.e. bug fixes) the source code to remain relevant and progressive against competition.…

    • 665 Words
    • 3 Pages
    Good Essays
  • Good Essays

    Martinig & Associates, (1995-2009), Measuring Integrated Progress on Agile Software Development Projects, Retrieved February 25, 2013, from http://www.methodsandtools.com/archive/archive.php?id=61…

    • 684 Words
    • 3 Pages
    Good Essays
  • Powerful Essays

    “Change control aims to ensure that all changes are assessed and approved by management before their implementation. Its goals are minimal disruption to services, reduction in back-out activities and economic utilization of resources involved in implementing change” (Wikipedia, 2008). Change control is the formal process to allow the customer and developer to communicate what is needed to modify or correct problems in an application. This process will convey the specific needs and both the customer and the developers have documentation to show what deliverables will come from the change request. The change process is documenting the request, analyzing technical and business impacts and risks, gaining approval from stakeholders, scheduling and managing the change workflow, and reviewing the change tasks. The change management process in and of itself must also be tuned for operational efficiency assessing the types of changes that are being requested across the organization, the speed with which changes are made, or the number of changes that must be reversed. The software change request require expenditures and may generate revenues over a span of time. A software change can be considered the result of an investment decision in which expenses are dispersed in the belief that greater benefits will be obtained in the future by changing or improving the software. Similarly, the choice…

    • 2098 Words
    • 9 Pages
    Powerful Essays
  • Satisfactory Essays

    “The classic waterfall model views the optimal process for software development as a linear or sequential series of phases that take developers from initial high-level requirements through system testing and product shipment.” 2 Microsoft isn’t the only one either. “Due to the success of the Waterfall model, many software development firms and industrial manufacturers have adopted it as their prime development framework and SDLC to plan, build, and maintain their products.” ¬3 Though it is one of the first software project development methods, the waterfall method remains one of the…

    • 321 Words
    • 2 Pages
    Satisfactory Essays
  • Satisfactory Essays

    Individual Project Budget

    • 627 Words
    • 2 Pages

    For this Project we have in front of us we are going to be expecting some changes, as the nature of the project itself, changes will occur. If a change were to be encountered during the project we have and if those said changes are out of the blue and or unexpected then we will analyze the changes fully and ensure proper documentation and reporting of the changes. Once we examine the said changes that we observed we will send the reports that we have created to the management that oversees the areas that the changes happened and study and review the changes based on specific guidelines we have set. These guidelines include:…

    • 627 Words
    • 2 Pages
    Satisfactory Essays
  • Satisfactory Essays

    Braude, E. J., & Bernstein, M. E. (2011). Software Engineering, Modern Approaches (2nd ed.). :…

    • 516 Words
    • 3 Pages
    Satisfactory Essays
  • Best Essays

    Nerur S., Mahapatra R and Mangalaraj G. (2005). Challenges of Migrating to Agile Methodologies. Communications of the ACM. Vol. 48, No. 5, May, pp. 73-78.…

    • 3598 Words
    • 15 Pages
    Best Essays
  • Good Essays

    However, the rapid change in customer demands and fiercer market competition forced it to make a choice whether or not to adopt agile methods instead of traditional plan-driven development method. The iterative nature of agile method makes it an excellent alternative when it comes to managing software projects. But since the new method differed from the traditional way in almost every respect, Jharna Software had to take a flexible and feasible approach for change management to execute the agile method. There was no denying for the necessary and urgency of the change management in term of customer orientation business model. The case that a rival company Ampersand was closed after lost a main client confirmed this point.…

    • 596 Words
    • 3 Pages
    Good Essays
  • Powerful Essays

    The requirements engineering program at Siemens Corporate Research has been involved with process improvement, training and project execution across many of the Siemens operating companies. We have been able to observe and assist with process improvement in mainly global software development efforts. Other researchers have reported extensively on various aspects of distributed requirements engineering, but issues specific to organizational structure have not been well categorized. Our experience has been that organizational and other management issues can overshadow technical problems caused by globalization. This paper describes some of the different organizational structures we have encountered, the problems introduced into requirements engineering processes by these structures, and techniques that were effective in mitigating some of the negative effects of global software development. projects in the large, and specifically distributed requirements engineering efforts. The requirements engineering (RE) competency center at Siemens Corporate Research in Princeton has had the unique opportunity to participate in large, global projects with different organizational structures. Each structure brought different challenges, benefits and issues. In the following sections, I will describe some of the structures we encountered, problems caused by the organizational structures, and, finally, I will suggest techniques for mitigating the problems encountered.…

    • 2822 Words
    • 12 Pages
    Powerful Essays
  • Good Essays

    Agile UCD Case Study

    • 1012 Words
    • 5 Pages

    The management should introduce adoption of Agile UCD methodologies by bringing to light its business advantages like delivery of economic, usable, quality software with an accelerated time-to-market. Understanding the process advantages by reduction in risks of bottlenecks, negligible rework requirements, reduced documentation and smooth integration process, increased productivity and simplicity would promote the adoption of Agile UCD much rapidly.…

    • 1012 Words
    • 5 Pages
    Good Essays
  • Powerful Essays

    Agile Manifesto Case Study

    • 2096 Words
    • 9 Pages

    The Agile Manifesto emphasizes the importance of the customer in the development process. Again we refer to the fact that the Agile Manifesto Satisfying the client via immediate and uninterrupted delivery of software is our highest priority (M1). Also it states that Welcome varying requirements, even at maturity level of development (M2). 1Besides this also in the values of the Agile Manifesto the importance of this aspect can be seen, as these both mention the importance of customer collaboration and responding to change. A5 Collective ownership of work A5 involves that all the work is done is the product of whole team not of a single one. No one team participant owns, or is dependable for a particular code segment and whole work can be reformed by the team, without any permission. This feature also linked with the team having a shared vision and responsibility of the system to be built. The whole team is working together, aiming for a single goal and is collectively responsible that this goal is reached. This aspect is found in a indirect manner in the researched methodologies. Chao et al. [70] states numerous agile methods…

    • 2096 Words
    • 9 Pages
    Powerful Essays