Agile Development: Learning Management System

This document discusses the agile development approach for creating a learning management system. It covers the objectives, constraints, risks, and opportunities involved in the project. The document also includes an implementation roadmap and features that need to be developed.

Running head: AGILE DEVELOPMENT
Agile Development: Learning Management System
Name of the Student
Name of the University
Author’s Note

1
AGILE DEVELOPMENT
Table of Contents
Section A – Proposal.......................................................................................................................3
Business Case..............................................................................................................................3
a. Sensible Approach for the development of the system by BluChip....................................3
b. Objectives of the project......................................................................................................4
c. Potential constraints, high level risk and issues and opportunities......................................6
d. Roles and responsibility of project community...................................................................9
Create an implementation Roadmap Excel............................................................................11
a. Implementation Roadmap including features that are needed to be implemented............11
b. Roadmap defining Minimum Viable Product for first release..........................................11
c. Features that are needed to be developed over the horizon...............................................12
Creation of Product Backlog.................................................................................................12
a. Planning for breaking down features for MVP and Roadmap...........................................12
b. Example of backlog...........................................................................................................15
c. Calculation of velocity of the Team...................................................................................16
Section B – Adapting to Changes..................................................................................................16
a. Process of adding two additional features without changing go-live date.........................16
b. Description of using feedback from internal users for inclusion of right feature..............17
c. Reprioritization of product backlog for maximizing delivery of value.............................18
d. Accommodation of changes in release plan for testing features with internal users.........18

2
AGILE DEVELOPMENT
e. Communicating changes with stakeholders.......................................................................18
References......................................................................................................................................21

3
AGILE DEVELOPMENT
Section A – Proposal
Business Case
a. Sensible Approach for the development of the system by BluChip
The eLearning market is expected to grow at a rate of 7.2% each year and this sheer
growth can throw new opportunity and challenges in the education sector (Noe et al. 2017). The
learning management system is needed to focus on the capability of the learner rather than the
syllabus that is followed by the traditional learning system. The scrum method can be used by
the project manager for development of the LMS primarily. It can help in improving the
productivity of the team and delivering the software in each 2-4 weeks. The implementation of
agile scrum methodology includes team formation with the help of diversity, frequent feedback
from clients, participating users and communicative teamwork. Kanban methodology can also be
adopted for helping the team work together and it can be combined with scrum for forming
scrumban methodology (Joo, Kim and Kim 2016). This methodology helps in development of
the learning management system with the features of both scrum and Kanban methodology. The
agile scrumban methodology is important for analyzing system requirement and help in
designing an efficient human centered design. The system analyst can implement design thing
approaches such that the effectiveness of the system analysis improves. An iterative approach is
needed to be applied for solving problems since feedback from different people are taken for the
development of the critical component (Walker et al. 2016). New ideas can be applied and
creativity can be improved for development of a successful solution quickly.
Extreme software development methodology (XP) is applied for the improving the
quality of software and increasing the responsiveness for any changes that are needed to be made
in the software product. The extreme programming advocates frequent release of the software in

4
AGILE DEVELOPMENT
shorter development life cycle for improving productivity and adoption of the changes in the
final software build. It helps in inducing checkpoints in the software development process and
reviewing the code extensively, testing the codes and to avoid programming the feature until
they are needed in the software (Almarashdeh 2016). A flat structure in management and
maintaining simplicity in the code is applied for managing the changes effectively. The adoption
of agile methodology helps in integrating the learning management system with the real time
data for overlaying the information with static content and offering a dynamic package of
learning for the user.
For the development of the learning management system with the top end functionality
the core resources of the business is needed to be identified and the agile software development
is needed to be applied. The adoption of agile process can help the organization to harness the
changes for customer’s competitive advantage and deliver the working software referencing the
short timescale.
b. Objectives of the project
The development of the learning management system with the application of agile approach
helps in developing the information system in iterative cycles. For starting the development
process a research is needed to be made on the requirement and purpose of the project. The
following are the main objectives identified for the development of the information system.
 To provide top end functionality to the users and provide support of multiple platform
and devices.
 To use high quality content and that is customizable according to the client needs
 To enable VR/AR and AI assistant and top end functionality and different creative ideas
for making the LMS system unique and attractive

5
AGILE DEVELOPMENT
 To test the system with internal staff before go-live for finding the errors and improve the
usability of the system.
 To manage the changes in the project during the development process and meet the
requirement of the users
 To integrate the different functions of the departments and look at the cost opportunity
for maximizing profit and reducing the expenses of the organization.
For the demonstration of the success of the project to the executive team some leading indicators
are needed to be used:
Effectiveness of communication – It is needed to be made sure that the employees
understands the communication messages and have active involvement in the development of the
learning management system.
Relationship and satisfaction of customer – the customers should be involved in the
development process and the developed module should be shared with them for testing (Silva et
al. 2015). Focus is needed to be given on satisfaction of the customer and right customer is
needed to be selected.
Employee Satisfaction – The employees should have proper understanding about the
project such that they can contribute to successfully develop the system.
Image of the brand – recognition and brand image is a leading indicator for the success and
market research is needed to be made for determining that the brand image is rising or falling.
Trust – People should believe in the management and barriers are needed to be eliminated
for faster development. Management program is needed to be introduced for increasing the trust
of the customer and employees.

6
AGILE DEVELOPMENT
Distraction – Measures are needed to be applied for the administrative task, management
and quality improvement. It is needed to be analyze the time the employee spends on the task
they are assigned and the leader show try to eliminate the waste.
Project Management – The organization should deliver the project objectives on time
such that efficiency and effectiveness is improved.
c. Potential constraints, high level risk and issues and opportunities
There are different constraint acting in the development process and they are needed to be
identified prior of starting the development such that the final project has no error. The following
are the constraint that are identified such as:
Budgetary constraint – insufficient funds and uncertainty about the approved budget can
cause a barrier for the project. The development team should have a vision and sign agreements
for the completion of their task and needs to wait for getting the funds (Judge and Murray 2017).
A planning is needed to be made for the identification of the problem and ensure that necessary
budget is available and it is used wisely.
Manpower Constraint – the lack of funds can be managed by getting loans but the
unavailability of properly trained technical staffs can cause failure of the project. An estimation
is needed to be made for analyzing the team size and man power needed for the completion of
the project (Sharp and Lang 2018). Training is needed to be given to the employees and
incentive scheme is needed to be provided for engaging them actively in the project.
Usability and Support – The employees aware of the learning management system
should be able to use it. A requirement assessment is needed to be performed and usage statistics,
interviews and online survey is needed to be performed with the faculty, students and other type

7
AGILE DEVELOPMENT
of users. The constraint is that the faculty might not be trained and feel that the more features are
needed to be implemented. They might not get enough time for learn to use the LMS for
maximizing the effectiveness. Thus it can be concluded that the faculty may not use the LMS
system effectively due to lack of training and support.
There are different risk associated with the development of the learning management system for
Bluechips and they are discussed below:
 Platform compatibility issues with BluChip’s LMS and unable to support multiple
platforms/devices.
 Testing failure with client content customization.
 User experience issues and expenses incurred for augmented reality and virtual reality
 One year’s content provided by Learning4U becomes irrelevant and does meet
requirements for BluChip
There are different issues associated with the risk identified above and they are discussed below:
 The compatibility issues of the platform can cause the system inaccessible from
any device or browser. The LMS system is needed to be designed such that it can
also be opened with devices having slow internet connection and smaller screen.
The LMS system should be responsive such that it can automatically adjust the
screen layout for the accommodation of user device and context.
 The test failure and content customization can cause error in the source code and
incompatibility with the other module. This may take more than the expected time
causing addition of more cost in the project.

8
AGILE DEVELOPMENT
 The environment context of the user is needed to be detected and different
schemas are needed to be used for increasing accuracy of the sensor modality.
The aspects that could affect the UX such as use, responsiveness, social comfort
and accuracy is needed to be improved.
 The content would be provided by Learning4U for 1 year and for successfully
running the LMS fresh content is needed to be added every year and a special
team is needed to be created for addition of content and engaging faculty to
improving the system.
The following are the opportunities identified for the development of the learning
management system:
Lower cost and complexity – Transiting to a learning management system was a
deliberate, expensive and time consuming but the modern LMS system is more accessible and
less cost extortionate. Thus this is an opportunity for increase in market growth of LMS system.
Rise of mobility – The society has embraced the mobile device in every aspect of life and
the mobile connectivity opened doors for a new level of learning. The society is moving far from
the classic method of learning and with the LMS system the support for real time learning can be
provided to the users.
Customer learning experiences – The learning experience of the students can be mapped
with their specific interest, behavior, needs according to time. A series of events can be created
for the promotion of continuous learning and online activity, supporting resources and needed to
be available on demand. The analysis of learning interaction by tracking the user activity can be

9
AGILE DEVELOPMENT
used as a feedback for linking learning activity with the outcomes for the business and make
continuous improvement for the LMS.
d. Roles and responsibility of project community
The roles and responsibility of the project community who are needed to be involved and
the time they would be engaged in the project is discussed below:
Contractor – The contractor is responsible for hiring employees and resources for
starting the development of the learning management system. The
Faculty – The faculty plays a role in arranging teaching session and testing the system
for creating real life environment. They are needed to be trained such that they can use the AR
and AI for managing the teaching environment.
User – The student plays a role of testing the usability of the information system
according to their needs and ask for changes that are needed to be made for increasing the
usability of the LMS.
Developer – The developer analyzes the requirement of the system and develops the
information system modules.
System Analyst – A testing is done on the developed modules and they are integrated
with each other to check the functionality of the system (Battou, Baz and Mammass 2017). The
VR/AR and AI functionality is tested for sent for testing tem for identification of changes.
Tester – The codes are tested with different users for finding the improvement and
changes that are needed to be made in the current codes such that the functionality and features
are properly implemented.

10
AGILE DEVELOPMENT
Project manager – responsible for completing the planned project and plays a leading
role in project planning, execution, controlling, monitoring and closing the project. The day to
day activity management, reviewing and prioritization is also done such that the project stays
under budget and time (Elbanna and Sarker 2015). Status and executive reporting is also the
responsibility of the project manager. Project management software is used by the project
manager for planning and scheduling the task and execute or control the aspects of the project.
Steering Committee – The management representatives and different stakeholders helps
to provide guidance on different strategy that can be applied for the development of the
information system. A leadership is provided and helps in resolving different issues that are
disputed by the project manager and takes decision on the change request for key elements for
example budget and deliverables (Annosi et al. 2016).
Role Worked hours Rate/Day Total Rate
Contractor 6 months £400/day £11,200
Faculty 6 months £200/day £5,600
User 6 months NA
Developer 6 months £1070 £29,960
System Analyst 6 months £1070 £29,960
Tester 6 months £1070 £29,960
Project Manager 6 months £1070 £29,960
Steering Committee 6 months NA

11
AGILE DEVELOPMENT
Create an implementation Roadmap Excel
a. Implementation Roadmap including features that are needed to be implemented
BluChip's Implementation Roadmap RELEASES
KEY SHORTTERM MEDIUM
TERM LONG TERM
2019 - Q3 2019 - Q4 2020 - Q1 2020 - Q2 2020 - Q3 2020 - Q4
Teams or roles
implementing features JUL AUG SEPT OCT NOV DEC JAN FEB MAR APR MAY JUN JUL AUG SEPT OCT NOV DEC
SHORTTERM
MEDIUM TERM
LONG TERM
FUTURE - OVER HORIZON
FEATURES
FUTURE - OVER
HORIZON
FEATURES
Actual ProductDevelopment
Scoping
Internal Test rollout
Market Analysis
Game based learning
Maintainance
Budgeting
Building Teams
Existing Competitions
Platform analysis
Hardware requriement
Software requirement
Working on UserExperience
Generating Content
Engagementof faculty
Developmentof modules
Integration of modules
Implementation of features
External TestRollout
Updates
Improvements
Support
Addition of new featrures
Feedbacks
Onboarding of users
Online training libraries
2020 SPRING
FULL FIRST
VERSION RELEASE
31/ 03/ 20
FALL2019 (MVP)
FIRSTRELEASE
31/12/19
Video Integration
Social learning
eLearning simulation using VR
AI and providing relevant suggestion
Reevaluaton
Complete Guide
Progress Tracking
Quiz and infographics
Implementing VR/ AR& AI assistansts
b. Roadmap defining Minimum Viable Product for first release
For the first release the roadmap for Minimum Viable Product is created and it is based in
short term, medium term and long term features that are needed to be included in the product. An
estimation is made for the short tem and it includes budgeting, building teams, market analysis,
existing competitions, platform analysis, hardware and software requirement analysis.
The medium term release is needed to include the actual product development, working
on user experience, generation of content, Implementation of VR/AR and AI assistance,
Development of modules, integration of modules and working on engaging the faculty and
implementation of features.

12
AGILE DEVELOPMENT
The customer preference and needs are needed to be maintained for the short term and
medium term goals for the MVP release.
The features that are included in the short term and the long term helps Bluechips to
create a project plan and estimate the resources that are needed for releasing the MVP. The
sustainability of the product can be maintained and over the horizon features and long term
features that can be implemented for increasing the popularity of the application can be identified
for the development of learning management system.
c. Features that are needed to be developed over the horizon
The main objective for the development of the learning maangement system is to
improve the response time and allow the student to access the learning material from remote
location. The resources can be shared with maximum student and thus engaging them is learning
activities program for improve their knowledge and skills. The use of AR/VR feature with the
LMS would attract the students and allow them to learn things using the virtrual environment
and thus improving their knowlede. The students can find the feature useful because it would
help thme to visualize the content and increase their concentration in the study. The
implementation of AI would help to generate automated response message and suggest similar
kind of study materials that can help an user to improve his/ her learning skill.
Creation of Product Backlog
a. Planning for breaking down features for MVP and Roadmap
For breaking down the features of MVP a planning is needed to be made with
assumptions such that the project helps in meeting the goals of the client. Brainstorming and
questionnaires are needed to be used for analysis of the scope and objective of project. The
market analysis is made for the identification of the competitor and implementation of unique

13
AGILE DEVELOPMENT
feature to make the product distinguishable from the existing products in the market. The
platform is currently demanded is needed to be analyzed for the identification of hardware and
software that is needed for the development of the software.
A build measure learning process is used for planning and allows releasing the product
for its continuous improvement and validating the assumptions made. It is used for learning the
requirement from the user and developing future iteration such that the information system can
better server the user requests (Denning 2016). The following steps are performed for planning
breakdown features for MVP and Roadmap:
Step#1: Identification and understanding the business and market needs
The long term and success criteria for the development of the information system is
needed to be identified for defining the success of the product. Once the plan has been made for
the development of LMS the long term business goals are needed to be set (Younas et al. 2018).
The definition of the product success is also needed to be defined such as the LMS system
should have 1000,000 active user each month and would reach $1 million for each month’s
transaction.
Step#2: Mapping the user journeys
The users should have good experience with the first iteration of the information system
and this would help to look at the product from the user perspective. The user flow is also needed
to be defined by addressing the action of the user for completing goals and ensuring that any
option is not missed (Soni and Kohli 2017). The design of the interface is needed to be
convenient to use and for each of the user an ending is needed to be defined for meeting the
goals of the user.

14
AGILE DEVELOPMENT
Step#3: Creation of a plain and gain map
The pains actions and gains are needed to be tabulated for determining the potential value
of the developed application. E.g. If the user face problem for getting information about a course,
they should take the action of clicking on course details and view the availability of the course
and subjects available in the course.
Step#4: Taking decisions on the features needed to be build
The features that are needed to be included is needed to be identified and an opportunity
statement is needed to be created for the integration of the features (Abrahamsson et al. 2017).
The features are also needed to be broken down into product roadmap and a prioritization matrix
is needed to be developed for addressing the opportunity.

15
AGILE DEVELOPMENT
b. Example of backlog
BluChip's Product Backlog
Task Name Sprint# Assigned To Acceptance
Criteria
DoD Definition of
Done Start Finish Epics Story Points Spikes Priority Status
Projec t Initiation Sprint 1 22/07/19 06/08/19 User story
00 24 Functional High In Progress
Kickoff M eetings Analysis Team,
Project M anager
Inc lusion of
stakeholders
Performa nc e
requirement 22/07/19 23/07/19 user story
01 8 Functional M edium C omplete
C reation of projec t brief Project M anager Inc lusion of all
requirement C oding guidelines 24/07/19 25/07/19 user story
02 16 Functional M edium C omplete
Edits submitted on draft C lient , Projec t
Supervisor
Inc lusion of all
requirement
Performa nc e
requirement 26/07/19 29/07/19 user story
03 0 Functional M edium C omplete
Projec t Pla nning Sprint 2 30/07/19 01/08/19 user story
04 24 Functional High In Progress
C ost estimation Ac count M anager Under Budget C omplianc e
requirement 02/08/19 06/08/19 user story
05 16 Functional M edium In Progress
Time estimation Project M anager Less than 6 months C omplianc e
requirement 07/08/19 03/09/19 user story
06 8 Functional High In Progress
Analysis of the benefits of LM S Analysis Team,
Project M anager Positive RO I Sec urity verification 07/08/19 13/08/19 user story
07 0 Functional M edium In Progress
Design Sprint 3 14/08/19 15/08/19 user story
08 50 Tec hnical High In Progress
Data base design Development
Team Proper func tionality C ode review 16/08/19 19/08/19 user story
09 18 Tec hnical High In Progress
Interfac e design Development
Team
Simple and
attractive C oding guidelines 20/08/19 21/08/19 user story
10 15 Tec hnical High In Progress
C reation of design specific ation Development
Team
Inc lusion of all
technic al items C ode coverage 22/08/19 23/08/19 user story
11 17 Functional High In Progress
Development Sprint 4 26/08/19 30/08/19 user story
12 33 Tec hnical High In Progress
Developing system modules Development
Team
Proper working of
features (AR/AI) C ode review 02/09/19 03/09/19 user story
13 12 Tec hnical High In Progress
Integration of system mod ules Development
Team
Proper working of
features (AR/AI) C oding guidelines 04/09/19 25/10/19 user story
14 11 Tec hnical High In Progress
Perform initial test Development
Team
M eets clients
expectation Sec urity verification 04/09/19 10/09/19 user story
15 10 Tec hnical High In Progress
testing Sprint 5 11/09/19 13/09/19 user story
16 35 Tec hnical High In Progress
Performing system test Testing team M eets clients
expectation C ode review 11/09/19 13/09/19 user story
17 12 Tec hnical M edium In Progress
Doc ument issues found Testing team Error rectified C oding guidelines 16/09/19 20/09/19 user story
18 11 Functional M edium In Progress
C orrect issues found Development
Team Error rectified C ode coverage 23/09/19 24/09/19 user story
19 12 Tec hnical High In Progress
G o Live Sprint 6 25/09/19 15/10/19 user story
20 30 Tec hnical M edium In Progress
Hosting the system
Development
Team, Testing
Team
Ac cessable from
remote loc ation C ode review 16/10/19 25/10/19 user story
21 10 Tec hnical M edium In Progress
C hange management Project M anager C hange without
failure in deadline Sec urity verification 28/10/19 01/11/19 user story
22 10 Functional M edium In Progress
Through Testing Testing team No errors or bugs C ode review 28/10/19 30/10/19 user story
23 10 Tec hnical High In Progress
Projec t C losure Sprint 7 31/10/19 01/11/19 user story
24 33 Functional M edium In Progress
Projec t documentation Project Supervisor
All servic e and
featrures
documented
C omplianc e
requirement 04/11/19 12/11/19 user story
25 11 Functional M edium In Progress
Stakeholder sign off HR M anager,
Project M anager Project c ompleted C omplianc e
requirement 04/11/19 06/11/19 user story
26 11 Functional M edium In Progress
Projec t manager sign off Project M anager,
HR M anager Project c ompleted C omplianc e
requirement 07/11/19 08/11/19 user story
27 11 Functional M edium In Progress

16
AGILE DEVELOPMENT
c. Calculation of velocity of the Team
Sprint SP
Sprint 1 24
Sprint 2 24
Sprint 3 50
Sprint 4 33
Sprint 5 35
Sprint 6 30
Sprint 7 33
Average of last
7 Sprint 32.71428571
Rounf Off (33)
Sprint Velocity
Section B – Adapting to Changes
a. Process of adding two additional features without changing go-live date
The agile change management process can be adopted for addition of two additional
features without changing the go live date. The SCRUM is used for the management of
requirement and it treats the requirement the prioritized stack also known as product backlog.
The Disciplined Agile Development is used for recognizing the items that are needed to be
implemented and also finding the non-required works (Serrador and Pinto 2015). With the

17
AGILE DEVELOPMENT
application of the approach the development team creates a stack of priority and estimated task
that are needed to be addressed.
The extreme programmer would need a stack of user stories that are written on index card
and DAD is used as defect tracker for the management of stacks. The priority of non-required
work items are negotiated by the team and addresses for becoming a slack time in the schedule.
Another process is to freeze the requirement for current iteration for providing a stability
level for the development team. Thus on addition of two new process is considered as another
requirement (Ahimbisibwe, Daellenbach and Cavana 2017). The DAD and XP has the support
for change requirement for the iteration and this would also need to move some requirement to
next iteration such that room is created for the new requirement integrated with the current
iteration.
b. Description of using feedback from internal users for inclusion of right feature
It is important to take feedback from customer for making improvement and
understanding the fundamental needs of the user.
Customer feedback survey is needed to be conducted that may appear on the beta version
of the LMS for gathering information about the usability of the system. The user preference is
examined for getting recommendation about the implementation of AI in the learning
management system.
Email and customer contact forms can used for reaching the customer and maximizing
the effectiveness of the channel and improve the customer experience (Ahimbisibwe, Cavana
and Daellenbach 2015). The proportion of internal users that have voted for inclusion of VR/AR

18
AGILE DEVELOPMENT
in the current system is evaluated for the inclusion of the feature in LMS and increase the
efficiency of the system.
Exploratory customer interview can be conducted for directly reaching the customer and
understanding their needs. Feedback forms can be used for increasing the usability and it should
be kept in mind that the feedback form are simple and does not asks for complex data and details
of payment from the user (Bonner et al. 2016).
c. Reprioritization of product backlog for maximizing delivery of value
The product backlog can be prioritized with the application of MoSCoW methodology
such that a common understanding of the project can be shared with the stakeholders. This
methodology is derived from the first letter of each of the category of prioritization.
Mo (Must have) the critical requirements and should be applied to the learning
management system on the basis of priority (Vijayasarathy and Butler 2015). If one of the
requirement is not taken then also it is considered that the release product is unfulfilled.
S (Should Have) the requirement that are important but not critical for releasing and this
requirements should not be sensitive to time.
Co (Could Have) the desirable but not the mandatory requirement needed for the release
and they should be of low cost improvement for product (Brhel et al. 2015)
W (Won’t Have) the least critical components are considered that may be not
corresponded with the product strategy. This can be ignored and implemented for the future
release.

19
AGILE DEVELOPMENT
d. Accommodation of changes in release plan for testing features with internal users
In the release plan the changes are needed to be accommodated with the involvement of
the internal users and testing all the functionality of the LMS that are specified in the SLA. A
quality test is performed in the system for ensuring that the expected capability of the LMS has
been fulfilled and all the features works as expected by the client. The last minute changes that
are needed to be made in the system can be accommodated by skipping some of the test such that
the deadline for launching the system is not missed. The bugs in the system can be fixed in the
maintenance phase by the means of update and patches. It is needed to be made sure that the
final project meets the necessary quality standards and the usability needs such that it does not
crashes or become irresponsive during accessed from different device and platforms (Crowston
et al. 2016). The modification that are made in the modules is needed to be tested during its
integration with the system by allocating more number of resources for developing the learning
management system. The quality management team should be involved such that they can check
the revision that has been made and allow the project for final release.
e. Communicating changes with stakeholders.
Appropriate communication channels that can be used for communicating with the
stakeholders for successfully portraying the change BlueChip has implemented within their
system are given below:
Formal meetings – With the face to face meetings the aims and objectives of BlueChip
system can be clearly stated to the development team and they have an idea about the content
that is needed to be included in the learning management system. It would also help to
understand the importance of availability of the application in multiple platform and need of
customization for future clients.

20
AGILE DEVELOPMENT
Conference calls – It helps in including the stakeholders not able to attend face to face
meeting to share their opinion and views regarding the features needed to be involved for the
development of the learning management system. The views for inclusion of VR/AR and Ai
assistance is shared by the stakeholders with the help of conference calls and meetings.
Newsletters/ Posters and Email – It is used for making some necessary changes in the
project and sharing feedback regarding the developed modules that are sent for usability testing
to the internal users (Al-Zewairi et al. 2017). It is important to get valuable feedback such that
the strength of the message is improved and it should be made sure that feedback and impact is
received quickly.
Voice mail – It can be used as a reference and save it for listening multiple time if any of
the requirement is not clear and make the development process more compelling.
Hallway conversation – It can be used for generating new innovative ideas and discussing
it with the development team for its implementation in the LMS and increase the efficiency of
the project.
Sporting events – It can be used for gathering inputs and feedbacks from the development
team and the internal users. This approach can be applied for brainstorming new ideas and
strategy for BlueChip that can be applied in the development process for successfully deploy the
LMS in real life environment (Larson and Chang 2016).

21
AGILE DEVELOPMENT
References
Abrahamsson, P., Salo, O., Ronkainen, J. and Warsta, J., 2017. Agile software development
methods: Review and analysis. arXiv preprint arXiv:1709.08439.
Ahimbisibwe, A., Cavana, R.Y. and Daellenbach, U., 2015. A contingency fit model of critical
success factors for software development projects: A comparison of agile and traditional plan-
based methodologies. Journal of Enterprise Information Management, 28(1), pp.7-33.
Ahimbisibwe, A., Daellenbach, U. and Cavana, R.Y., 2017. Empirical comparison of traditional
plan-based and agile methodologies: Critical success factors for outsourced software
development projects from vendors’ perspective. Journal of Enterprise Information
Management, 30(3), pp.400-453.
Almarashdeh, I., 2016. Sharing instructors experience of learning management system: A
technology perspective of user satisfaction in distance learning course. Computers in Human
Behavior, 63, pp.249-255.
Al-Zewairi, M., Biltawi, M., Etaiwi, W. and Shaout, A., 2017. Agile software development
methodologies: survey of surveys. Journal of Computer and Communications, 5(05), pp.74-97.
Annosi, M.C., Magnusson, M., Martini, A. and Appio, F.P., 2016. Social conduct, learning and
innovation: an abductive study of the dark side of agile software development. Creativity and
Innovation Management, 25(4), pp.515-535.
Battou, A., Baz, O. and Mammass, D., 2017. Toward a Framework for Designing Adaptive
Educational Hypermedia System Based on Agile Learning Design Approach. In Europe and

22
AGILE DEVELOPMENT
MENA Cooperation Advances in Information and Communication Technologies (pp. 113-123).
Springer, Cham.
Bonner, N.A., Kulangara, N., Nerur, S. and Teng, J.T., 2016. An empirical investigation of the
perceived benefits of agile methodologies using an innovation-theoretical model. Journal of
Database Management (JDM), 27(3), pp.38-63.
Brhel, M., Meth, H., Maedche, A. and Werder, K., 2015. Exploring principles of user-centered
agile software development: A literature review. Information and software technology, 61,
pp.163-181.
Crowston, K., Chudoba, K., Watson-Manheim, M.B. and Rahmati, P., 2016, May. Inter-team
coordination in large-scale agile development: A test of organizational discontinuity theory.
In Proceedings of the Scientific Workshop Proceedings of XP2016 (p. 2). ACM.
Denning, S., 2016. How to make the whole organization “Agile”. Strategy & Leadership, 44(4),
pp.10-17.
Elbanna, A. and Sarker, S., 2015. The risks of agile software development: Learning from
Adopters. IEEE Software, 33(5), pp.72-79.
Joo, Y.J., Kim, N. and Kim, N.H., 2016. Factors predicting online university students’ use of a
mobile learning management system (m-LMS). Educational Technology Research and
Development, 64(4), pp.611-630.
Judge, D.S. and Murray, B., 2017. Student and faculty transition to a new online learning
management system. Teaching and Learning in Nursing, 12(4), pp.277-280.

23
AGILE DEVELOPMENT
Larson, D. and Chang, V., 2016. A review and future direction of agile, business intelligence,
analytics and data science. International Journal of Information Management, 36(5), pp.700-
710.
Noe, R.A., Hollenbeck, J.R., Gerhart, B. and Wright, P.M., 2017. Human resource management:
Gaining a competitive advantage. New York, NY: McGraw-Hill Education.
Papadopoulos, G., 2015. Moving from traditional to agile software development methodologies
also on large, distributed projects. Procedia-Social and Behavioral Sciences, 175, pp.455-463.
Serrador, P. and Pinto, J.K., 2015. Does Agile work?—A quantitative analysis of agile project
success. International Journal of Project Management, 33(5), pp.1040-1051.
Sharp, J.H. and Lang, G., 2018. Agile in teaching and learning: Conceptual framework and
research agenda. Journal of Information Systems Education, 29(2).
Silva, F.S., Soares, F.S.F., Peres, A.L., de Azevedo, I.M., Vasconcelos, A.P.L., Kamei, F.K. and
de Lemos Meira, S.R., 2015. Using CMMI together with agile software development: A
systematic review. Information and Software Technology, 58, pp.20-43.
Soni, D. and Kohli, P.J., 2017. Cost estimation model for web applications using agile software
development methodology. Pertanika Journal Of Science & Technology, 25(3), pp.931-938.
Vijayasarathy, L.R. and Butler, C.W., 2015. Choice of software development methodologies: Do
organizational, project, and team characteristics matter?. IEEE software, 33(5), pp.86-94.
Walker, D.S., Lindner, J.R., Murphrey, T.P. and Dooley, K., 2016. Learning management system
usage. Quarterly Review of Distance Education, 17(2), pp.41-50.

24
AGILE DEVELOPMENT
Younas, M., Jawawi, D.N., Ghani, I., Fries, T. and Kazmi, R., 2018. Agile development in the
cloud computing environment: A systematic review. Information and Software Technology, 103,
pp.142-158.