Agile Project Management for Som Bot Application Development

This report provides an overview of the agile project management approach used in the development of the Som Bot application, a voice and text-based application designed to answer gaming questions. It highlights the use of agile methodologies, DevOps practices, and continuous integration to ensure rapid software releases and adaptability to changing user requirements. The report details the Agile Extension Strategy horizon, emphasizing incremental updates and the integration of testing throughout the software development process. It also covers the application of the Agile SDLC model, PMBOK knowledge areas, and the APM framework to manage and monitor the application's performance and security. The study contrasts agile with traditional project management approaches, underscoring the flexibility and collaborative nature of agile in delivering customer-centric solutions.

Running head: PROJECT MANAGEMENT
Project Management
Name of the Student:
Name of the University:

1PROJECT MANAGEMENT
6. Delivery and review
Som Bot application is worked as voice commands or the text chat messages on the
phone, which is provided of answers to the gaming questions. Documentation as well as testing
is two project management activities which are provided on the software development teams.
This application is used of agile project management as well as product development
methodology which promotes interaction among IT departments as well as business users.
Among the IT departments, they are focused to build along with deliver of software which meets
with changing requirements of users (Abrahamsson et al., 2017). There is a building of two-way
DevOps software pipeline among the users and the customers. Creation of DevOps culture is
used for collaboration among the team members those are involved into software delivery. In this
practice, the team is produced of application in short cycles ensure that the software is released
anytime.
6.1 Strategy
In development of Sam Bot application, there is use of Agile Extension Strategy horizon
to the software project (Turk, France, & Rumpe, 2014). This extension is provided of guidance
for the agile business by effective business analysis as well as applies of horizons to the program
governance as well as project management.
• The recommended change
There are software changes by allowing of incremental updates towards the application in
production. The agile development is recognized that testing is not a phase from coding,
but it is considered as integral part of software development process (Brhel et al., 2015).
The features are evolved to change the requirements of customers.

2PROJECT MANAGEMENT
• Recommendations for specific initiatives at a strategic level of detail
Agile testing tool is used for cross functional agile development teams to plan along with
execute of the testing activities (Alliance, 2015). Using agile framework, it is about
collaboration and learning from others to deliver of value.
• Provide a model supporting one initiative recommendation
Agile SDLC model is used to support the recommendations which are combination of
iterative as well as incremental process models that is focused on adaptability as well as
satisfaction of customers by rapid delivery of the working software products. This
particular model is used to break the product into smaller incremental builds. It is
provided into iterations (Ahmed et al., 2016). This model is a practice which promotes
continuous iteration of development as well as testing into the software development
lifecycle of project.
7. Project management
In this particular study, the best project management approach is agile methodology,
which is based on iterative development. This development is implied of solutions which are
evolved throughout collaboration among the cross functional teams.
7.1 PMBOK: a discussion
Agile methods is used which consists of six stages. In the first stage, the project team
defines as well as plans main features. Requirement analysis stage is conducted where meetings
with the managers are done to identify the business goals, requirements (Turk, France, & Rumpe,
2014). Design phase provides picture how the product will look, implementation phase where
coding, development as well as testing of application features is done, testing ensures that the

3PROJECT MANAGEMENT
product solves the requirements of customer, deployment phase delivers the product to the
clients after testing. The PMBOK knowledge areas which are used in this software development
project are integration management, scope management, schedule, cost, quality, resource,
communications, risks, procurement and stakeholder management knowledge areas.
There are some basic differences among agile as well as traditional project management
approaches where the agile is focused on adapt of changes into core plan. The other approaches
are required of managers to control of the project changes. Agile is about the customers where
the software puts adherence to the plans (Brhel et al., 2015). The traditional approach has little or
no scope to make changes to the product. Agile methodology is adaptable and offered of
flexibility. Into traditional, the ownership is belonged to the project manager. Agile is where the
team members are shared of ownership of project.
7.2 APM Framework
APM framework is a programming model which provides guidance to the application
component provider of the Sam Bot. It is focused on create of components to access towards
company’s enterprise information system and also establish as well as managing of connections
among the system. This framework develops of components which provide of security to the
enterprise application as well as providing of secured transactions. APM is monitoring as well as
management of performance along with availability of the software applications (Saadat &
Sharif, 2017). It detects the application performance issues for maintaining of expected level of
services.

4PROJECT MANAGEMENT
References
Abrahamsson, P., Salo, O., Ronkainen, J., & Warsta, J. (2017). Agile software development
methods: Review and analysis. arXiv preprint arXiv:1709.08439.
Ahmed, T. M., Bezemer, C. P., Chen, T. H., Hassan, A. E., & Shang, W. (2016, May). Studying
the effectiveness of application performance management (APM) tools for detecting
performance regressions for web applications: An experience report. In Proceedings of
the 13th International Conference on Mining Software Repositories (pp. 1-12). ACM.
Alliance, A. (2015). What is agile software development. web: http://www. agilealliance. org.
Brhel, M., Meth, H., Maedche, A., & Werder, K. (2015). Exploring principles of user-centered
agile software development: A literature review. Information and Software
Technology, 61, 163-181.
Saadat, N., & Sharif, M. M. M. (2017, September). Application framework for forest
surveillance and data acquisition using unmanned aerial vehicle system. In Engineering
Technology and Technopreneurship (ICE2T), 2017 International Conference on (pp. 1-
6). IEEE.
Turk, D., France, R., & Rumpe, B. (2014). Limitations of agile software processes. arXiv
preprint arXiv:1409.6600.