Approach and Methodology pdf

Running head: APPROACH TO METHODOLOGY
Week Five: Approach to Methodology
Name of the Student:
Name of the University:
Author note:

1APPROACH TO METHODOLOGY
Table of Contents
Tangible and intangible benefits..........................................................................................2
Recommendation.................................................................................................................2
Procedures for development and implementation teams.....................................................2
Schedule for post-implementation audit..............................................................................3
References............................................................................................................................5

2APPROACH TO METHODOLOGY
Scrum method for this software development project
Tangible and intangible benefits
Scrum method is considered as an agile method for managing a project. Generally, agile
software development with Scrum is prescribed as methodology. However, scrum is an iterative
as well as incremental agile software development framework that is able to manage
development of the project.
There are several benefits of scrum methodology that can be divided as tangible and
intangible methodology. Stakeholder management can be achieved effectively for multiple
scopes for stakeholder as well as team involvement before every sprint. Through involving, the
client in each of the steps of the project is achieved (Mahalakshmi & Sundararajan, 2015).
Delivering software frequently trust with the ability for delivering high quality software. On the
other hand, transparency is one of the major benefits for using scrum method.
Recommendation
In order to use scrum methodology in more effective way,
 It is required to focus on people over the procedures and mind-set over the skill set.
 Integrating the method of testing with the process of lifecycle
 Establishing self-organizing teams and redefine success for the agile projects can be
helpful to improve the process.
Procedures for development and implementation teams

3APPROACH TO METHODOLOGY
In order to develop and implement the plan for team, it is required to focus on scrum,
crystal methodologies, dynamic software development method, feature driven development and
lean software development as well as extreme programming. In addition, early as well as
predictable delivery can be achieved with the help of particular method (Acosta, Espinosa &
Espinosa, 2015). Predictable costs and schedule is estimated by using scrum method. It also
allows for making change in the project. It also concentrates on the business value by allowing
client determining the priority of the features (Venugopal, Mathai & Abraham, 2015). It is also
important to focus on the users that can be achieved by the method.
Schedule for post-implementation audit
Task
Mode Task Name Duration Start Finish Predecessors
Auto
Scheduled
Project Agile Method
Implementation 36 days Thu 26-04-
18
Thu 14-06-
18
Auto
Scheduled Pre-requisite Features 9 days Thu 26-04-
18 Tue 08-05-18
Auto
Scheduled Financial Structure 4 days Thu 26-04-
18 Tue 01-05-18
Auto
Scheduled Security Structure 5 days Wed 02-05-
18 Tue 08-05-18 3
Auto
Scheduled
Post-implementation
Basic 6 days Wed 09-05-
18
Wed 16-05-
18
Auto
Scheduled General Ledger 4 days Wed 09-05-
18
Mon 14-05-
18 4
Auto
Scheduled
Procure to Pay
Features 6 days Wed 09-05-
18
Wed 16-05-
18 4
Auto
Scheduled Order to Cash 2 days Wed 09-05-
18
Thu 10-05-
18 4
Auto
Scheduled
Post-implementation
Advanced Features 6 days Fri 11-05-18 Fri 18-05-18
Auto
Scheduled
Advanced - General
Ledger 4 days Fri 11-05-18 Wed 16-05-
18 8
Auto
Scheduled
Advanced- Procure
to Pay Features 6 days Fri 11-05-18 Fri 18-05-18 8
Auto
Scheduled Order to Cash 4 days Fri 11-05-18 Wed 16-05-
18 8

4APPROACH TO METHODOLOGY
Auto
Scheduled
Agile Scrum
Implementation 12 days Thu 17-05-
18 Fri 01-06-18
Auto
Scheduled Training of End-User 6 days Thu 17-05-
18
Thu 24-05-
18 12
Auto
Scheduled Data Migration 6 days Fri 25-05-18 Fri 01-06-18 14
Auto
Scheduled Infrastructure Setup 7 days Mon 04-06-
18 Tue 12-06-18 15
Auto
Scheduled Project Closure 2 days Wed 13-06-
18
Thu 14-06-
18 16

5APPROACH TO METHODOLOGY
References
Acosta, A., Espinosa, J. E., & Espinosa, J. (2015). Developing tools for building simulation
scenarios for SUMO based on the SCRUM methodology. SUMO 2015–Intermodal
Simulation for Intermodal Transport, 23.
Mahalakshmi, M., & Sundararajan, M. (2015, February). Tracking the student's performance in
Web-based education using Scrum methodology. In Computing and Communications
Technologies (ICCCT), 2015 International Conference on (pp. 379-382). IEEE.
Venugopal, R., Mathai, M. K., & Abraham, J. T. (2015). Scrum methodology in huge
projects. bharata mata journal of Multidisciplinary Studies, 82.