Customized Project Development for IS Development

The current project aims to develop an information system using Scrum methodology, which allows for continuous iteration and improvement. The project will be divided into various sprints, each with its own objectives and activities. The product owner will be responsible for prioritizing the backlog items, while the Scrum master will ensure that the team works efficiently. The project has been rejected from other PMMs such as waterfall methods or linear methodologies because they do not provide enough freedom to the team to work and make improvements continuously. Additionally, the current system development life cycle (SDLC) will focus on four key aspects: planning and organizing, acquisition and implementation, delivery and support, and monitoring.

0
Project Management
(Schlepp-adoo Event Management)
Student Name:
Student ID:
Course Name:
Course ID:
Faculty Name:
University Name:

Table of Contents
Task 1.........................................................................................................................................2
Introduction............................................................................................................................2
Project Characteristics............................................................................................................2
Identified Methodology..........................................................................................................3
PMM and Project Characteristics...........................................................................................3
Rationale behind Selecting Scrum.........................................................................................4
Rejection of other PMMs.......................................................................................................4
SDLC in current project.........................................................................................................5
Task 3.........................................................................................................................................6
Task 3a: MS Project Plan.......................................................................................................6
Task 3b: Changeover Strategy...............................................................................................7
References................................................................................................................................11

Task 1
Introduction
The current paper is concerned with the project planning and implementation for Schlepp-
adoo Event Management Company. The company has been opened by three graduates who
study in BSc. The established event management company assists in the setting up of walking
and racing events. It also provides necessary logistical assistance. The current project
management area looks into the methodology to be selected, existing project characteristics,
rationale behind selection of particular methodology and rejection of other methods and the
consideration of software development cycle.
Project Characteristics
The event management company is opened by three individuals and is currently catering to
the clients who engage in walking and racing events. The event management also assists
client in raising funds by connecting with the external clients. The company engages in
various activities to achieve the objectives for each event such as setting up client meeting,
presenting event proposals, event creation, approaching external organizations, providing
collateral merchandise, and monitoring the budget and staffs.
The company is willing to improve the efficiency of its operational activities by expansion of
its information system. The goal is to implement improved information system that can allow
the company to increase its customer base to cover corporate events such as leadership
training, team building, and others. An improved IS will be implemented that can fast track
the organizational efficiency to cater to expanded client base.
The current project will focus on implementing integrated information system mechanism
using the contemporary technology. It will allow the organizational employees to

communicate with each other on the go and share required data and information with clients
and other stakeholders as and when required. A mobile and desktop application will be
developed that will track all the progresses at one place. A server will be setup that will
integrate the data on both, mobile and top. Cloud computing will be used for data storage as it
is comparatively more secure and requires less security focus.
Identified Methodology
The methodology that has been identified for the current project is Scrum. Scrum is a part of
agile movement which focuses more on communication and collaboration than completing
the project on time. The purpose is to ensure that the project develops as per the client’s
requirement with multiple outputs. The Scrum methodology consists of three work units,
namely, product owner, scrum master, and project team (Singh, 2008). The scrum method
will have five key elements under consideration. They are project planning, release planning,
sprint, sprint planning, daily scrum, sprint review, and sprint retrospective. The beneficial
aspect of Scrum is that it allows appreciable level of freedom to the team members working
on the project. The scrum master will only act as the facilitator and will ensure that the team
members face minimal challenge in completing the project activities. The product owner will
discuss on the overall project goals and objectives.
PMM and Project Characteristics
The project is smaller in size and is expected that it will take not more than four to five
months to be implemented. This whole duration will have multiple sprints of varying degree
that will be focused on development of various modules. The project is likely to require
several iterations during the overall development. The company owners who are willing to
implement the system have no prior experience of the implementation of the IS of this type.
This will require that the company stays in constant touch with the project development team.

Moreover, the owners should be kept in loop on the development of various modules with
explanation on how each module is going to aid on overall Information System.
Rationale behind Selecting Scrum
The current project is a customized information system development for the company. The
information system development for an organization is not a single phase development and
requires constant collaboration with the client to ensure that implemented system is catering
to all the required needs. Implementing off-the shelf information system poses challenge in a
manner that it comes with various modules that might be useless for this company and there
is high possibility that it lacks certain modules that are required. Therefore, customized
project development is necessary. Moreover, this development is new for the company and
there is likeliness of multiple instances of improvements. Considering the expectation of
iterations, Scrum methodology has been considered suitable for the project development
(Iqbal and Javed. 2014). This will allow as much iteration as possible to ensure that the
project meets all the required specifications of the client. Product owner will be one of the
three business owner and the Scrum master and project team will be outsourced from external
IT company who has experience in IS development.
Rejection of other PMMs
The other project methods have been rejected because they do not provide enough freedom to
the team to work and make improvements on continuous basis. Moreover, as there is the
possibility of continued improvements in the requirements, therefore Scrum was considered
better option. Moreover, other methods such as waterfall methods or other linear
methodologies require that the requirements are crystal clear from the beginning of the
project as it is considered final (Jain and Joshi, 2016). This creates issues for clients who are
not sure which level of development will work well for them.

SDLC in current project
The current system development will work in accordance to system development life cycle
that focuses on four key aspects, namely, planning and organizing, acquisition and
implementation, delivery and support, and monitoring (Mahalakshmi and Sundararajan,
2013). All the sprints will follow these four stages wherein the objectives and activities for
each sprint will be planned, and then activities will be implemented. Further, developed
module will be delivered and then feedback will be taken for further sprints.

6
Task 3
Task 3a: MS Project Plan
The current section shows the plan of the entire project. The project is divided into various sprints that will be completed throughout the project.
Each of the sprint is completed by meeting with the client where in the feedback on the product/module developed is received. As it has been
stated that a Scrum project should have four to nine team members, this project will have seven members working on the project and the two will
scrum master and product owner. The image below shows all the details of the project plan.

9
Task 3b: Changeover Strategy
As per the changeover strategies are concerned, they are direct, phased, parallel, and pilot
changeover. The method selected for the current project phased changeover. Phased
changeover method is almost a combination of direct and parallel changeover (Lilly, 2015).
In the phased changeover, project is implemented in phased manner throughout the
organization. This method is useful if the company owners are not willing to interrupt the
functioning of all the departments at once and also they want to understand the effectiveness
of the project being implemented. The phased implementation allows the organization to
understand the effectiveness of the project in one department and then gradually roll out to
another. Appreciable aspect is that it includes the benefits of both, parallel and direct
changeover.
Parallel changeover states that the project should be implemented side by side of the existing
system. The parallel implementation ensures that the existing working of the organization is
not disturbed till the entire project is implemented and then gradually the organization is
shifted from old to new. This method alone is not appreciable as it is costly because company
has to bear cost of new as well as old system at the same time (Ukaoha et al, 2015). Another
method is direct method which is least appreciated changeover method in the project
community. The reason is that it calls for sudden disruption of the entire organization’s
operation. Therefore, if the implementation is at very small scale that is at departmental scale,
then this method would be a good fit as disrupting functioning of one department is not going
to bring down the whole organization. Therefore, phased changeover has been selected which
is the combination of parallel and direct changeover methods.
The fourth changeover method is pilot changeover. In this method, the system that is
developed is first tested at another location and setup that is similar to that of the actual

organization. After the successful result, the project is then implemented within the
organization. This method is an appreciable approach as it allows the organization to
understand any loopholes in the new system prior to making it live in actual condition.
However, this method is costly and can be afforded by organizations that have deep pocket.
In addition, this method is suitable for mission critical systems where the organization cannot
take any risk in any manner. The current organization does not stand on both the conditions
and, therefore, this method is not accepted.
Prior to going live, it is important that the organization considers all the pros and cons of the
system being implemented. If the organization fails to appropriately understand the challenge
being posed by the new system, then it is likely that the benefits might get overpowered by
the issues. Undermining associated risks with the new system is likely to put the entire
organisation at risk. Therefore, prior to implementation, systems must be evaluated properly.
In addition to this, it should be ensured that the internal and external stakeholders are aware
of the new system as they will be interacting with the new system in new ways. The lack of
awareness might create chaotic situation which will halt the progress for few days instead of
fast tracking it. In such cases, the organization can provide appropriate training to the internal
stakeholders and provide briefings to the external stakeholders. This will ensure that
everyone is on the same page when the system is made live. The current changeover strategy
will ensure that the employees are provided appropriate training so that they work
appreciably well in the days to come.

References
Iqbal, U. and Javed, A., 2014. Review-Scrum (R-Scrum) Introduction Of Model Driven
Architecture (MDA) In Agile Methodology. International Journal of Technology
Enhancements and Emerging Engineering Research, 3(11), pp.296-302.
Jain, S. and Joshi, H., 2016, September. Impact of early testing on cost, reliability and release
time. In Reliability, Infocom Technologies and Optimization (Trends and Future Directions)
(ICRITO), 2016 5th International Conference on (pp. 318-322). IEEE.
Lilly, M.T., 2015. Manufacturing: Engineering, Management and Marketing. Partridge
Africa.
Mahalakshmi, M. and Sundararajan, M., 2013. Traditional SDLC Vs Scrum Methodology–A
Comparative Study. International Journal of Emerging Technology and Advanced
Engineering, 3(6), pp.192-196.
Singh, M., 2008, August. U-SCRUM: An agile methodology for promoting usability.
In Agile, 2008. AGILE'08. Conference (pp. 555-560). IEEE.
Ukaoha, K.C., Chiemeke, S.C., Egbokhare, F.A. and Daodu, S.S., 2015. Success and failure
factors in portal development: a case study of the University of Benin. Journal of Emerging
Trends in Engineering and Applied Sciences, 6(3), pp.223-226.